You can put an AI receptionist on Microsoft Teams Phone in two ways: turn on Microsoft's own Teams Phone Agent, which runs inside an auto attendant and is billed in Copilot Credits, or route calls from Teams to a third-party AI voice agent over Direct Routing, Operator Connect, or a transfer from your auto attendant to an external number. Your Teams users, numbers and call queues stay as they are either way. The right choice depends on what the receptionist has to do: answer FAQs and book Bookings appointments, or look up orders, take actions in your helpdesk and CRM, and hand off with context.
TL;DR
- Teams auto attendants route calls by menu. They play greetings, take keypad or spoken choices, and send callers to people, queues, voicemail or an external number. They don't answer questions.
- Teams Phone Agent is Microsoft's AI receptionist. It became generally available on 30 Sep 2026, answers questions from up to ten files or public web pages per tool, books appointments through Microsoft Bookings, and is billed in Copilot Credits.
- Licensing: at least one Teams Phone license in the tenant, plus a free Teams Phone Resource Account license per resource account. Transfers to external numbers need PSTN calling on the resource account.
- A third-party AI receptionist connects three ways: a Direct Routing SBC, an Operator Connect operator, or an auto attendant option that redirects to an external number the AI answers.
- Test transfers back into Teams first. That's where most setups break, and where callers notice.
- Cost has three parts: Microsoft licenses, carrier minutes, and the AI itself. Open charges $0.75–$0.90 per resolution, and handoffs to a human aren't billed.
What Teams Phone auto attendants and call queues do
An auto attendant is the menu callers hear when they dial your main number. In the Teams admin center you set business hours, after-hours and holiday call flows, a greeting, and menu options mapped to keys 0 to 9, * and #. Each option can redirect to a person, a call queue, another auto attendant, a resource account, a Microsoft 365 group voicemail, or an external phone number. Callers can also dial by name or extension.
A call queue holds callers and rings a group of agents, with music on hold, overflow and timeout rules.
Together they route calls well. They don't resolve anything: a caller who wants to know where their order is still waits for a person. For MENA teams there's another catch. Microsoft's language table for auto attendants lists Arabic (Egypt) and Arabic (Saudi Arabia) for text-to-speech but not for speech recognition, so Arabic-speaking callers can only use the keypad.
Teams Phone Agent: Microsoft's built-in AI receptionist
Teams Phone Agent is a type of auto attendant that answers in natural language instead of fixed menus. You create it in the same place (Voice, then Auto attendants, then Add, then Teams Phone Agent). According to Microsoft's documentation, checked 22 Nov 2026:
- Status: generally available to all customers since 30 Sep 2026. It isn't supported for use in India.
- Questions and answers: each Q&A tool takes up to ten files totalling 5 MB, or public web pages. It doesn't crawl a site, only the page you give it, and pages that need a login or sit on an intranet aren't supported. URLs refresh once a day.
- Appointments: through Microsoft Bookings.
- Routing: to people, queues, other auto attendants, external numbers, and Copilot Studio agents.
- Settings: an AI disclaimer, maximum call length, automatic recording, spam detection and historical reporting.
- Languages: the supported list includes Arabic (Egypt) and Arabic (Saudi Arabia).
- Billing: Copilot Credits through a spending policy. If no policy exists, the policy isn't funded, or the monthly limit runs out, it falls back to working as a plain auto attendant.
When it's the better fit: your receptionist mostly answers opening hours, directions and policy questions from a few documents, books appointments in Bookings, and routes callers. You stay inside Microsoft billing and the admin center.
When it falls short: the call needs data from systems outside Microsoft, such as an order in Shopify, a ticket in Zendesk or an account in Salesforce. Microsoft's route for deeper workflows is to add Copilot Studio agents, which need their own Copilot Studio licenses, and Copilot Studio's page for connecting voice agents to Teams Phone Agent is marked preview. Microsoft also doesn't publish a per-minute Copilot Credit rate for Teams Phone Agent; it offers an estimator instead.
Teams Phone licensing for an AI receptionist
| What you need | When | Notes |
|---|---|---|
| Teams Phone license | Always, at least one in the tenant | Enables auto attendants, call queues and Teams Phone Agent |
| Teams Phone Resource Account license | One per resource account | Free. Resource accounts can't sign in |
| Phone number on the resource account | To take calls from outside Teams | A Microsoft service number, an Operator Connect number or a Direct Routing number |
| PSTN calling on the resource account | To transfer callers to an external number | Microsoft numbers: funded pay-as-you-go or Communications Credits. Direct Routing: an online voice routing policy. Operator Connect: nothing extra |
| Copilot Credits and a spending policy | Teams Phone Agent only | Usage-based. Unfunded means it acts as an auto attendant |
| Copilot Studio licenses | Only if you add Copilot Studio agents | Tenant and user licenses, billed separately |
Microsoft's documentation also notes that transfers between Calling Plan, Operator Connect and Direct Routing trunks aren't supported. If your main number is on one connectivity type, plan the route to the AI and back on the same one, and test it.
3 ways to connect a third-party AI receptionist to Teams Phone
| Option | How the call reaches the AI | Good fit when | Watch for |
|---|---|---|---|
| Direct Routing | Your SBC routes chosen numbers or patterns to the AI's SIP endpoint, and a Teams voice route sends calls to the SBC | You already run Direct Routing with your own carrier | TLS is required. Microsoft supports only SBCs it has tested for Direct Routing |
| Operator Connect | Your operator points a trunk at the AI's SIP endpoint for the numbers you choose | Your carrier is an Operator Connect operator and will set the route | Depends on your operator. Ask them before you plan around it |
| Auto attendant redirect to an external number | A menu option, after-hours flow or operator setting redirects to a phone number the AI answers | You want a pilot this week, or you only want AI on one branch, such as after hours | The resource account needs PSTN calling, and each redirect is an outbound call leg |
Microsoft also documents a third-party voice agent path through Azure Communication Services, set up in PowerShell, for vendors that Microsoft lists for it. Microsoft lists a known issue: a voice agent reached this way can't yet transfer or conference to an external phone number. Ask any vendor which of these paths it uses.
For most teams the order is: start with an auto attendant redirect on one branch, measure it, then move to Direct Routing or Operator Connect for the main number once the AI is earning its place. For the broader SIP mechanics behind these options, see our guide to SIP trunking for AI voice agents.
How to set up an AI receptionist in the Teams admin center
These steps use the auto attendant redirect, then add Direct Routing for the full version.
- Get a number the AI answers. From your AI voice agent vendor, get a phone number or SIP details for the agent and set up its greeting, knowledge and actions first.
- Check the resource account. In the Teams admin center, go to Voice, then Resource accounts. Confirm the auto attendant's resource account has the free Teams Phone Resource Account license and PSTN calling for external transfers (pay-as-you-go or Communications Credits, a voice routing policy, or an Operator Connect number).
- Open the auto attendant. Go to Voice, then Auto attendants, and select the one on your main number.
- Pick the branch. In the business-hours, after-hours or holiday call flow, choose Redirect call, or edit a menu option, and set the destination to External phone number with the AI's number in E.164 format.
- Set the operator. Keep an operator destination that reaches a human, so errors and "operator" requests still land with a person.
- Run the diagnostic. Use the auto attendant diagnostic in the Microsoft 365 admin center with the resource account to catch licensing or policy problems.
- Move to Direct Routing when ready. Add the AI's SIP endpoint as a peer on your SBC over TLS, create a voice route for the numbers that should reach it, and add those numbers to the AI platform.
- Configure the way back. Set where the AI transfers callers: a Teams user, a call queue or an auto attendant. Test it from outside your network.
What to test before you go live
- Caller ID. Does the AI see the caller's real number, or your Teams number? Without the real number it can't recognise returning customers or look up their account.
- Transfers back into Teams. Transfer to a user, a call queue and an auto attendant, during business hours and after. Check that the human sees who is calling and why.
- Context on handoff. Does the person who picks up get the transcript, or does the caller repeat everything?
- Audio and latency. Call from a mobile on a weak signal. Measure the pause between the caller finishing and the AI replying.
- Keypad input. Press keys during the AI's greeting and when it asks for a number.
- Failure path. Switch off the AI route in a test window. Callers should reach a person or voicemail, not silence.
- Languages. Test each language your callers speak, with real speakers. For Arabic, our guide to testing Arabic AI voice agents across dialects has a test plan.
What an AI receptionist on Teams Phone costs
| Cost | Teams Phone Agent | Third-party AI receptionist |
|---|---|---|
| Microsoft licenses | At least one Teams Phone license, free resource account licenses | Same |
| AI usage | Copilot Credits. Microsoft publishes no per-minute rate and points to its estimator | The vendor's per-minute, per-call or per-resolution price |
| Carrier minutes | Your Calling Plan, Operator Connect or Direct Routing carrier | Same, plus the outbound leg for each auto attendant redirect |
| Extras | Bookings, Copilot Studio or Power Automate if you use them | Usually none on the Microsoft side |
We couldn't load Microsoft's Teams Phone list price page when we checked on 22 Nov 2026, so take the license price from your Microsoft agreement or reseller quote.
Where Open fits
Open's AI voice agents work as a SIP destination for Teams Phone over Direct Routing or Operator Connect, or as the external target on the auto attendant or call queue branch you choose (Open for Microsoft Teams). Your Teams users, numbers and admin center don't change, and the AI doesn't need its own Teams license because it isn't a Teams user. During the call it answers from your knowledge base and takes actions in tools such as Dynamics 365, Salesforce, ServiceNow and Zendesk. When it needs a person, it transfers back to a Teams user, auto attendant or call queue over SIP REFER with the transcript attached.
Open charges $0.75–$0.90 per resolution, depending on volume. Handoffs to a human aren't billed, Microsoft keeps billing your Teams licenses, and carrier costs are passed through at cost. The details are on the pricing page, and Open's security documentation is at trust.open.cx. If you're comparing receptionists more widely, see the best AI receptionists in 2026, and for contact center platforms, CCaaS built-in AI vs a dedicated agent.
Sources
- Microsoft Learn, "Setup - Teams Phone Agent," https://learn.microsoft.com/en-us/microsoftteams/aa-cq-setup-teams-phone-agent, checked 22 Nov 2026
- Microsoft Learn, "Setup - Teams Phone Agent - Usage-based billing" (GA date, spending policies, fallback to auto attendant), https://learn.microsoft.com/en-us/microsoftteams/aa-cq-setup-teams-phone-agent-ubb, checked 22 Nov 2026
- Microsoft Learn, "Planning - Teams Phone Agent - Usage-based billing," https://learn.microsoft.com/en-us/microsoftteams/aa-cq-plan-teams-phone-agent-ubb, checked 22 Nov 2026
- Microsoft Learn, "Setup - Teams Phone Agent Questions and Answers tools," https://learn.microsoft.com/en-us/microsoftteams/aa-cq-setup-teams-phone-agent-tools-questions-answers, checked 22 Nov 2026
- Microsoft Learn, "Reference - Voice applications prerequisites and licensing," https://learn.microsoft.com/en-us/microsoftteams/aa-cq-reference-prerequisites-licensing, checked 22 Nov 2026
- Microsoft Learn, "Setup - Auto Attendant" (call routing options, language table), https://learn.microsoft.com/en-us/microsoftteams/aa-cq-setup-auto-attendant, checked 22 Nov 2026
- Microsoft Learn, "Setup - Third-party voice agents," https://learn.microsoft.com/en-us/microsoftteams/aa-cq-setup-third-party-voice-agents, checked 22 Nov 2026
- Microsoft Learn, "Integrate voice agents with Teams Phone Agent (preview)," https://learn.microsoft.com/en-us/microsoft-copilot-studio/voice-teams-phone-agent, checked 22 Nov 2026
- Microsoft Learn, "Plan Direct Routing," https://learn.microsoft.com/en-us/microsoftteams/direct-routing-plan, checked 22 Nov 2026
- Microsoft Learn, "Plan for Operator Connect," https://learn.microsoft.com/en-us/microsoftteams/operator-connect-plan, checked 22 Nov 2026
- Open, "Microsoft Teams," https://www.open.cx/telephony/microsoft-teams, checked 22 Nov 2026