Microsoft Teams Phone Agent moves the familiar auto attendant into a more conversational era. Instead of forcing every caller through a rigid “press one, press two” tree, the new agent can understand an ordinary request, answer from approved knowledge, help manage an appointment, route the caller, or hand a specialized workflow to a voice agent built in Microsoft Copilot Studio.
The timing matters. Teams Phone Agent entered Frontier Public Preview on June 15, 2026, and Microsoft has already added historical reporting, spam controls, customizable AI disclosures, configurable call duration, and new automatic-recording documentation. That pace makes the product worth evaluating—but it also makes disciplined preview governance essential.
The practical takeaway: Teams Phone Agent is ready for a narrow, measured pilot on the right service line. It is not yet a reason to replace a mature contact center, remove human escalation, or let an unauthenticated caller trigger sensitive work.
What changed this summer
| Date | Microsoft update | Why it matters |
|---|---|---|
| Jun 15, 2026 | Teams Phone Agent entered Frontier Public Preview. | Eligible tenants can begin controlled evaluation of conversational service-line calls. |
| Jul 20, 2026 | Historical reporting became available in the Teams voice-applications Power BI template. | Pilots can measure call results, categories, transfers, Q&A outcomes, and appointment outcomes instead of relying only on anecdotes. |
| Aug 12, 2026 | Microsoft documented spam detection, AI-disclaimer customization, and configurable call length. | Admins have more control over nuisance calls, caller transparency, and conversations that exceed the default four-minute limit. |
| Aug 17, 2026 | Automatic recording and transcription documentation was added for Teams Phone Agent. | Quality review and coaching become more practical, although Microsoft currently limits this recording feature to the Voice Applications trial. |
This is still a preview product. Features, setup steps, licensing, limits, and support boundaries can change. Treat the release log as a pilot roadmap, not a promise that every feature is ready for a business-critical main number.
What callers can actually do
| Capability | How it works | Best first use |
|---|---|---|
| Conversational routing | The caller describes what they need; the agent maps that intent to a person, operator, call queue, voice app, resource account, voicemail, or external number. | Replacing a deep menu on a departmental line while retaining a keypad and operator fallback. |
| Questions and answers | The agent answers from a curated knowledge tool built from supported documents or specific public web pages. | Hours, location, service eligibility, required documents, or other low-risk repeat questions. |
| Appointments | The agent connects through API endpoints for authentication, availability, booking, and retrieval. Microsoft recommends Power Automate as an integration layer. | A bounded scheduling workflow with clear identity checks and a staffed exception path. |
| Specialized voice workflows | A call can hand off to a basic Copilot Studio voice agent for scenarios such as billing, order status, inventory, or another custom process. | A read-only status workflow or tightly controlled transaction with independent verification. |
Where it fits in the Teams Voice stack
Teams Phone Agent does not eliminate auto attendants or call queues. It extends the front door and then uses the existing Teams Voice building blocks behind it.
| Component | Primary job | Use it when |
|---|---|---|
| Auto attendant | Hours, holidays, directory search, and predictable key or voice-command routing. | The path is stable and a simple deterministic menu is enough. |
| Teams Phone Agent | Conversational intent, knowledge answers, appointment tools, and smarter routing. | Callers express the same need in many different ways or ask repeat questions before transfer. |
| Call queue | Hold and distribute calls to available representatives. | A person needs to complete the interaction. |
| Copilot Studio voice agent | Custom logic, data access, and specialized workflows beyond built-in Q&A and appointments. | The use case has defined business logic, an owner, a support model, and appropriate verification controls. |
A sensible call flow is often: phone number → Teams Phone Agent → approved knowledge or tool → person or queue when confidence, policy, or caller preference requires it.
The preview limits leaders should understand
It is available through Frontier, not general availability
As of this article’s publication date, Microsoft documents Teams Phone Agent as a Frontier Public Preview feature. Copilot Studio integration is separately gated: the tenant must be explicitly enabled by Microsoft support before the Teams Phone channel appears.
The newest controls are PowerShell-first
Spam templates, AI-disclaimer customization, and call-duration changes currently require Microsoft Teams PowerShell module 7.9.1-preview or later. Microsoft says these controls are coming to the Teams admin center. The default Teams Phone Agent call length is four minutes unless an administrator changes it.
Knowledge does not maintain itself
During preview, a Q&A tool can use supported files or specific public web pages. Teams Phone Agent does not crawl links from a page, authenticated and intranet pages are not supported, and web pages are not automatically rescanned. A stale source can become a confidently delivered stale answer, so every knowledge set needs a business owner and refresh cadence.
Copilot Studio’s phone channel is public by design
Microsoft’s current setup requires the Copilot Studio agent channel to use No authentication so any caller can reach it through Teams Phone Agent. That does not mean a workflow should trust a caller’s claimed identity. Billing, prescription, account, payment, or personal-data scenarios need a separate, deliberate verification design before the agent reveals information or takes action.
Current orchestration has a specific support path
Microsoft currently requires classic orchestration for the Copilot Studio voice integration. Generative orchestration is not supported and can introduce delays of five to six seconds. Only basic voice agents are supported on this channel; real-time voice agents are not.
Recording is not a blanket compliance solution
Microsoft’s first-party Teams Phone Agent recording can automatically record and transcribe inbound calls and store them in SharePoint, but the current documentation limits it to the Voice Applications trial. Recording also creates legal, privacy, retention, access, and eDiscovery decisions. Microsoft allows the default AI notification to be changed or disabled through PowerShell, but explicitly makes the organization responsible for real-time participant notice under applicable law.
A safe, useful pilot blueprint
1. Pick one line with repeatable demand
Choose a departmental number where a meaningful share of calls involve the same ten to twenty intents. Facilities, scheduling, dealership service, clinic administration, property management, member services, and internal help desks can be strong candidates. Avoid the executive main line, emergency response, or a high-value transaction queue as the first experiment.
2. Define the allowed job in one sentence
A good pilot charter sounds like: “Answer approved questions about hours and service eligibility, help callers request an appointment, and transfer everything else to the correct queue.” If the sentence includes “anything the caller needs,” the scope is too broad.
3. Build a voice-ready knowledge set
- Use short, unambiguous answers written to be heard rather than scanned.
- Remove conflicting versions, complex tables, macros, graphics, and workflow instructions.
- Define acronyms and keep each knowledge tool aligned to the number’s purpose.
- Assign an owner, effective date, review date, and emergency correction process.
- Test questions callers actually ask, including slang, partial information, and incorrect assumptions.
4. Design human escape routes first
Configure an operator and map it to a key so callers can explicitly request a person. Also define transfers for low confidence, repeated misunderstanding, authentication failure, distressed callers, accessibility needs, and any topic the agent must not handle. A successful handoff should preserve context where the platform supports it and should never send the caller into a routing loop.
5. Separate conversation from identity proof
Voice convenience is not caller authentication. Before a workflow retrieves protected information or changes a record, require an approved verification step that is independent of what the caller says. Log verification outcomes without exposing unnecessary secrets in transcripts or analytics.
6. Make transparency part of the experience
Tell callers they are interacting with an AI assistant, explain recording or transcription when applicable, and provide a clear human option. Keep the message short and natural, but do not hide the nature of the interaction to reduce abandonment.
7. Test like a caller, not only like an administrator
- Quiet room, background noise, speakerphone, cellular connection, and low volume
- Different accents, speech rates, ages, and assistive communication patterns
- Interruptions, corrections, silence, repeated requests, and out-of-scope questions
- Duplicate names, after-hours calls, holidays, queue overflow, and failed transfers
- Requests for a person at the beginning, middle, and end of the interaction
- Prompt-injection-style requests to ignore rules, reveal sources, or perform prohibited work
- Calls near the configured time limit and conversations that move between languages
Measure outcomes that reflect caller experience
| Measure | What to review | Early warning |
|---|---|---|
| Answer success | How often approved questions receive a correct, complete answer. | High containment paired with repeat calls or later human correction. |
| Transfer accuracy | Whether the caller reaches the right person, queue, or workflow on the first transfer. | Transfers bouncing back to the front door or rising internal re-transfer rates. |
| Human escape | Whether callers can reach a person quickly when requested or required. | Hang-ups after repeated requests for an operator. |
| Latency and turn quality | Response delay, interruptions, awkward pauses, and recognition errors. | Callers repeating themselves or speaking over delayed responses. |
| Business outcome | Appointments completed, avoidable calls deflected, staff time saved, and demand shifted by hour. | A technically successful interaction that creates cleanup work downstream. |
| Risk and compliance | Unauthorized disclosure, unsafe action attempts, notice delivery, recording access, and retention. | Any protected-data answer without verified identity or unclear recording ownership. |
Microsoft’s historical report can help quantify call results, Q&A outcomes, appointment outcomes, transfers, and categories. Microsoft cautions that the reports rely on diagnostic telemetry and are not supported as audit, compliance, or payroll records. Use them for operational insight, then keep formal evidence in the systems designed for it.
Who should pilot now—and who should wait
Pilot now if your organization already runs Teams Phone, has a clear service-line problem, can join Frontier, can dedicate an owner to weekly tuning, and can keep sensitive work behind independent verification and human review.
Wait or limit the scope if the number is life-safety critical, every call is a complex exception, the workflow depends on unsupported regions or orchestration, recording and consent requirements are unresolved, or the organization cannot actively monitor a changing preview.
Frequently Asked Questions
Is Teams Phone Agent a replacement for an auto attendant? It extends the auto-attendant experience with conversational intent, knowledge, appointments, and agent handoffs. Existing Teams Voice components still handle hours, routing, queues, people, and other destinations.
Is it generally available? No. Microsoft currently lists it in Frontier Public Preview. The Copilot Studio voice channel is also a gated preview and is not intended for production use.
Can it answer from our website? It can use specific public pages during preview, but it does not crawl linked pages and does not automatically rescan them. Authenticated or intranet pages are not supported for the Q&A tool.
Can it book appointments? Yes, when connected to a suitable booking system through the required API functions. Microsoft recommends using Power Automate between the agent and the booking platform.
Can it record calls? Microsoft now documents automatic recording and transcription for inbound Teams Phone Agent calls, with recordings stored in SharePoint. The feature is currently limited to the Voice Applications trial.
What is the best first use case? One low-risk number with repeat questions, a small approved knowledge set, clear transfer destinations, an operator escape route, and measurable caller outcomes.
Turn Teams Phone Agent into a controlled pilot—not a science project
Accred Consulting can design the call flow, Teams Voice architecture, knowledge boundaries, Copilot Studio integration, identity checks, testing plan, reporting, and go/no-go criteria for a useful AI voice pilot.
Plan a Teams Phone Agent Pilot