Reece capability guide
Know the Microsoft 365 boundary before promising a booking.
Evaluate appointment-request handoff while direct Microsoft 365 calendar setup remains unavailable. Reece handles the bounded call work; your team keeps the decisions and commitments that require a person.
Start free 7-day trial Hear Reece answer live
7 days free · 60 minutes · No credit card required
Current Reece product assurances
- Keep your business number: Use your provider's forwarding instructions for all calls or missed calls only.
- Cover configured calls 24/7: Answers configured business calls 24/7, including after-hours and overflow calls.
- Review call results: The web dashboard keeps call recordings, transcripts, AI summaries, caller details, and outcomes together.
- Test without a card: 7 days and 60 call minutes are included.
The short answer for Microsoft 365 Calendar AI receptionist
Evaluate appointment-request handoff while direct Microsoft 365 calendar setup remains unavailable. Reece fits when the call can use reviewed business facts, a bounded action, and a named employee for exceptions. Customer-configurable Microsoft 365 calendar connection and direct booking are not currently exposed in production. Treat Reece as the request-capture layer, not as a Microsoft Graph, Exchange, or Outlook booking client. A tenant user or delegate must review the request and create or confirm the event.
- Requested service and preferred timing
- Caller details and approved intake
- Staff owner for scheduling follow-up
- Requested versus staff-confirmed status
What to inspect for Microsoft 365 Calendar AI receptionist
Use the current-surface boundary and staff-confirmation checklist to write the inputs, allowed decisions, attempted action, stop condition, fallback, and owner in one place. After a Microsoft 365 Calendar AI receptionist test call, compare that plan with the recording, transcript, summary, caller details, and outcome. Configuration shows what might happen; the call record shows what did happen. For a Microsoft 365 handoff, name the tenant owner, shared or delegated calendar, Outlook timezone, meeting-location policy, and employee who confirms the request. A Teams meeting link is not implied by a Reece call outcome.
Run the Microsoft 365 Calendar AI receptionist failure path
For Microsoft 365 Calendar AI receptionist, test requested service and preferred timing, a corrected answer, an interruption, an unsupported question, an unavailable destination, and a stale fact. The caller should hear a truthful boundary, the record should match the audio, and an employee should own the remaining work. Include an expired delegate permission, a request for a shared calendar the recipient cannot edit, and a time expressed in another timezone. Keep the outcome at requested until Outlook or Exchange evidence exists.
Microsoft 365 Calendar AI receptionist: who it fits and who still needs a staffed path
Microsoft 365 Calendar AI receptionist is a strong Reece fit when approved facts stay current and the business can name an owner for every open state. Keep sensitive, adversarial, high-stakes, regulated, or constantly changing work with a qualified person.
Keep the Microsoft 365 Calendar AI receptionist boundary visible
Customer-configurable Microsoft 365 calendar connection and direct booking are not currently exposed in production. Do not turn a requested appointment into a booking, a configured destination into a connected transfer, or a small test into a claim about accuracy, revenue, savings, or capacity.
Guardrail: Customer-configurable Microsoft 365 calendar connection and direct booking are not currently exposed in production.
Release Microsoft 365 Calendar AI receptionist in a bounded test
Start the Microsoft 365 Calendar AI receptionist current-surface boundary and staff-confirmation checklist with one schedule, call type, or forwarding condition. Keep the previous route available, document the expected result for each test, and roll back when facts, records, destinations, or fallbacks are misleading. Expand only after the receiving team says the records are actionable. The acceptance record should distinguish the Reece call ID, the human-created Outlook event, and any separately generated Teams meeting details; each has a different owner and timestamp.
How Reece handles the call
- Forward the calls you choose. Keep the number customers already know, then use your phone provider's instructions to forward all calls or missed calls only to Reece.
- Reece answers with approved knowledge. Reece answers the configured call and uses business knowledge the owner has reviewed before it becomes active.
- The caller explains what they need. Reece answers approved FAQs and gathers the caller, request, and intake details needed for a clear next step.
- A supported handoff happens. Eligible Scale and Growth setups can use configured direct or warm transfers. Otherwise, Reece records details or an appointment request for staff follow-up.
- Your team reviews the result. The recording, transcript, summary, caller details, and outcome stay together in the responsive web dashboard.
Your team stays in control. Reece handles approved call intake and configured routing. Your team still owns diagnosis, safety decisions, pricing, dispatch, appointment confirmation, and any follow-up that needs a person.
| Decision | Evidence to inspect | Owner |
|---|---|---|
| Requested service and preferred timing | Recording, transcript, summary, caller details, and outcome | Business-approved call flow |
| Caller details and approved intake | Configured rule, attempted action, fallback, and staff follow-up | Business-approved call flow |
| Staff owner for scheduling follow-up | Recording, transcript, summary, caller details, and outcome | Business-approved call flow |
| Requested versus staff-confirmed status | Configured rule, attempted action, fallback, and staff follow-up | Named human owner |
Know the handoff before you forward a call
Can I keep my current number?
Plans include 1, 3, or 10 Reece phone numbers. Businesses can keep an existing number and forward selected calls to Reece.
Can Reece take missed calls only?
Yes. Choose missed-call forwarding when staff should have the first chance to answer, or forward all calls when Reece should answer first. Your provider controls forwarding behavior.
What if the caller needs a person?
Scale and Growth support owner-configured direct and warm transfers. Reece does not include a staffed human fallback, so the team must define the follow-up path for calls that are not transferred.
Does an appointment request mean booked?
Reece can capture appointment requests, preferred times, caller details, and approved intake answers for staff follow-up. The current production UI does not offer customer-configurable calendar connections or direct provider-backed booking, so Reece does not report an appointment as confirmed.
Setup is guided, but completion time varies with business rules, transfer routing, testing, and carrier forwarding. Call results are available in the web dashboard. Email call notifications are available on all plans, subject to your notification preferences. SMS notifications are Coming Soon.
Privacy and sensitive calls. Review the current Privacy Policy and Terms before forwarding calls that may include sensitive information. Reece does not claim HIPAA compliance; medical, legal, emergency, financial, and other consequential calls may require a qualified person. Privacy Policy · Terms
Questions, answered
What should I verify for Microsoft 365 Calendar AI receptionist?
Verify the configured inputs, the attempted action, the resulting call record, the failure path, and the named human owner. Customer-configurable Microsoft 365 calendar connection and direct booking are not currently exposed in production.