Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Automatic voicemail triage uses a compliant and secure Large Language Model (LLM) to help users interpret and prioritize voicemail messages through transcript analysis.
When enabled, the system can generate:
- A concise summary of the message.
- Categories and priority indicators.
- Suggested follow-up actions.
- Highlighted key terms for quick review.
Important
This feature is available only through the Microsoft Frontier Program. General availability (GA) timing hasn't been announced yet.
How voicemail triage works
Voicemail triage runs after a message is recorded and before it's delivered to Exchange.
The service analyzes the voicemail transcript and can generate these outputs:
- Summary: A concise, natural-language paragraph that starts with the caller's intent and includes key details (for example, dates, times, requested actions, or contact information).
- Category: A topic label for the voicemail. Some categories are system-defined (for example, junk and harmful content), and other categories are generated from transcript content.
- Suggested actions: Recommended follow-up tasks derived from the voicemail content. System-defined action labels include callback, set appointment, reschedule appointment, cancel appointment, and email reply, followed by other requested actions generated from the transcript.
- Importance flag (urgency): A priority signal for time-critical messages, which can mark the voicemail as important in Outlook.
Generated triage insights are stored with the voicemail in Exchange and can be used by downstream automations such as Outlook rules, agent-based workflows, and other LLM-powered processes. A compliant evaluation model is used to assess the quality of the generated triage insights and monitor triage performance.
If AI-generated content doesn't appear for a voicemail, audio or transcript clarity might be insufficient for reliable triage output.
Scope
- Shared voicemail triage applies to missed calls handled by Auto Attendants, Call Queues, and Teams Phone Agents.
- Personal voicemail triage applies to a user's personal Teams voicemail.
For shared voicemail, AI triage data will also be available in the Teams Queues app experience soon. The Queues app requires a Teams Premium license.
Admin controls
Admins can control which AI outputs are generated:
- For personal voicemail, configure user settings in the Teams admin center (Manage users > Voicemail > Personal voicemail AI triage) or by using PowerShell.
- For shared voicemail, configure settings in the AI triage of shared voicemails template used by Auto Attendants, Call Queues, and Teams Phone Agents in the Teams admin center or by using PowerShell.
Requirements
Personal voicemail triage
Personal voicemail triage requires all of the following:
- A Microsoft 365 Copilot license for the user.
- A spending policy for AI Triage for Personal Voicemail configured in the Microsoft 365 admin center.
- Voicemail AI triage enabled in Voicemail policies in the Teams admin center.
If any requirement isn't met, AI triage isn't performed and no usage-based billing charges are incurred.
Shared voicemail triage
Shared voicemail triage requires both of the following:
- A spending policy for AI Triage for Shared Voicemail configured for the applicable resource account in the Microsoft 365 admin center.
- A Voicemail AI triage template selected for the specific Auto Attendant, Call Queue, or Teams Phone Agent in the Teams admin center.
If no template is selected, AI triage isn't performed and no usage-based billing charges are incurred, even when a spending policy is configured.
Billing summary
Billing is per voicemail processed:
- Personal voicemail triage: Charged per voicemail processed. For configuration details, see Personal voicemail AI triage billing.
- Shared voicemail triage: Charged once per voicemail processed, even when the same voicemail is delivered to multiple users. For configuration details, see Shared voicemail AI triage billing.
For shared voicemail, cost is attributed to the resource account associated with the Auto Attendant, Call Queue, or Teams Phone Agent. If an Auto Attendant or Call Queue doesn't have its own resource account, billing uses the root resource account associated with the phone number.
Availability
During TAP and early GA, voicemail AI triage is available only for tenants whose tenant language is set to English.
Additional languages and organization-defined custom categories and suggested actions might be introduced based on customer demand and feedback.