What this page covers
A Teams auto attendant or call queue can redirect a call to an external phone number, and that is how an AI voice agent connects. An auto attendant's after-hours or holiday call flow, or one of its menu options, can point at the agent's number. A call queue can send overflow, timeouts or calls with no staff logged in to the same number. The prerequisite to check is licensing. External transfers need the right license or policy on the resource account, and the requirement depends on how Teams connects to the phone network.
How Does an AI Voice Agent Connect to Teams Phone?
Through the auto attendants and call queues you already manage in the Teams admin center. Both can redirect a call to an external phone number, and the agent's number is that destination.
Teams auto attendants have separate business-hours, after-hours and holiday call flows. Each flow can redirect the call or play a menu, and External phone number is one of the destinations Microsoft lists for both. If business hours are left unchanged, Teams follows the business-hours flow from 9:00 AM to 5:00 PM every day. Set the practice's real hours first, so the after-hours flow sends the right calls to the agent. Microsoft covers this in set up an auto attendant.
Call queues have exception handling for overflow, timeout and no agents. Each exception can disconnect the call or redirect it to a routing destination. The maximum number of calls in the queue defaults to 50 and can be set from 0 to 200. The call timeout can be set from 0 seconds to 45 minutes. Matching the timeout to how long your front desk lets callers wait decides when the agent takes overflow.
Teams reaches the phone network through a Calling Plan, Operator Connect, Teams Phone Mobile or Direct Routing. With Direct Routing, a session border controller managed by you or your provider sits in front of Teams. Depending on that controller, a dedicated number such as a refill line can be routed to the agent over SIP before it reaches Teams.
Get an outside read on your Teams Phone calls workflow
In 30 minutes we map your current volume, the payers and systems involved, where staff time goes, and the highest-ROI calls and follow-ups Flexbone can take off your team first, scoped to the work you actually run.
What Licensing Does an External Transfer Need in Teams?
More than the Teams Phone Resource Account license. Microsoft's licensing reference for auto attendants and call queues lists an extra requirement when they transfer calls to an external phone number. It depends on the type of number the resource account uses:
- Microsoft-provided numbers need a funded pay-as-you-go license or Communications credits on the resource account.
- Direct Routing numbers need an online voice routing policy assigned to the resource account.
- Operator Connect numbers need nothing more in Teams, though Microsoft asks customers to arrange these calls with their operator.
Microsoft also notes that since November 1, 2025, Calling Plan licenses on resource accounts no longer cover these outbound calls. If a transfer to a person in your organization works but a transfer to an outside number fails, Microsoft's troubleshooting guidance points to licensing first. On Direct Routing, Teams prefers to move a transferred call with a SIP REFER to your session border controller. The controller's REFER handling is therefore part of the test plan.
Which Calls Does the Agent Take First?
Start where Teams already separates the traffic. The after-hours and holiday call flows carry the least risk, because the alternative is voicemail. Queue overflow comes next: when the front-desk queue reaches its timeout, callers reach the agent instead of waiting longer. A menu option for appointments then hands over a call type callers already pick themselves.
The calls the agent handles on those paths are routine ones. It books and reschedules visits, and it takes refill requests to the clinical staff queue without making a clinical decision. It answers coverage questions after an eligibility check. It handles calls in English and Spanish, and urgent after-hours calls follow your on-call rules. The after-hours answering service page covers that path in detail.
What Happens When a Caller Needs a Person?
The agent transfers the caller back into Teams, to a user's phone number or a call queue's number, and briefs the staff member first. The transcript is saved with the call. A call queue only accepts calls from outside Teams if its resource account has a phone number. That can be a Microsoft service number, an Operator Connect number, a Direct Routing number or a hybrid number. If your front-desk queue has no number today, assign one before go-live so the agent has somewhere to send callers.
Microsoft recommends configuring an Operator on the auto attendant. Teams sends callers to the Operator when they make no menu selection or when a call processing error occurs. Callers who do not choose an option still reach a person.
Does This Change Our Teams Phone Setup?
One destination changes in one call flow or one queue exception. Users keep their Teams numbers, devices and calling policies, and other auto attendants and queues stay as they are. Nothing is ported, and no number moves between Calling Plan, Operator Connect and Direct Routing. The added work is the resource account licensing above, plus a queue phone number if transfers back need one.
Results go to the EHR, not into Teams. Where the connection is set up, the agent writes appointments, refill requests and call notes to eClinicalWorks, athenahealth or Tebra. It uses a vendor API or a browser automation. Until then, it sends a structured message to a staff queue. The general routing patterns are covered in how voice agents connect to phone systems.
How Does a Flexbone Deployment Work?
Every deployment starts from the work as your team does it today, not from a product demo. The steps below are the same whether the first agent answers phones, checks eligibility, or files incoming documents.
- Audit first, then automate. We listen to a sample of your calls and read the work queues, then agree with your team on which work to automate first. The audit is complimentary.
- Forward-deployed engineers map your SOPs. An engineer sits with the staff who do the work and turns your written and unwritten rules into agent logic.
- Agents act on your rules, and exceptions go to a person. Each step follows logic built from your SOPs. A case outside those rules, or one the agent is not confident about, goes to your team with the context attached.
- Every action leaves a record. A check in a web application saves a screenshot, a call saves a transcript, and results are written back where your team already looks.
- Start with one or two agents on the systems you already run. The agents work in your EHR, practice management system, phone system, and the web applications your staff use, as they are configured today, so nothing is migrated or rebuilt.
- The same team stays after go-live. We monitor results, tune the agents as payers and workflows change, and add agents as new work is found.
The engagement model is described in more detail in forward-deployed engineering for healthcare contact centers.