Shared voicemail AI triage billing

This article is for IT pros and Teams administrators who want to set up usage-based billing for shared voicemail AI triage.

Important

This feature is available only through the Microsoft Frontier Program. General availability (GA) timing hasn't been announced yet.

Planning and licensing review

Planning

Licensing

  • Shared voicemail AI triage requires usage-based billing.
  • A Microsoft 365 Copilot license isn't required for shared voicemail triage.
  • For Queues app scenarios, the Queues app has separate licensing requirements (Teams Premium).

Shared voicemail AI triage usage-based billing

Each shared voicemail is charged once per processed voicemail, regardless of how many users receive it.

If you want to enable shared voicemail AI triage for all resource accounts, use the All users option in spending policy scope. This approach is recommended when you want to enable AI triage for all shared voicemail in your organization.

If you want to limit which resource accounts have voicemail AI triage enabled, create a Microsoft 365 security group and use the Specific groups option in the spending policy scope. To apply different spending limits to different resource accounts, create separate security groups. Limit the number of people who own these security groups.

Configuring a spending policy alone doesn't enable AI triage for resource accounts. AI triage must also be enabled in the specific Call Queue, Auto Attendant, and Teams Phone Agent templates.

For "Specific groups" option create a Microsoft 365 security group

  1. In the Microsoft 365 admin center, go to Teams & groups > Active teams and groups > Security groups.
  2. Select Add a security group.
  3. Complete group setup and create the group.

and add Call Queue, Auto Attendant, and Teams Phone Agent resource accounts to the group

  1. Open the security group you created.
  2. Add owners.
  3. Add the resource accounts used by Auto Attendants, Call Queues, or Teams Phone Agents.

Create a spending policy

These steps require the AI Administrator role.

Add spending policy

  1. In the Microsoft 365 admin center, go to Copilot > Cost Management.
  2. Select the Configuration tab.
  3. Select + Add spending policy.

Agents and services

  1. Turn off Allow new Agents and services as they become available.
  2. Select only AI Triage for Shared Voicemail.
  3. Clear all other services.
  4. Select Next.

Access scope

  1. Name the policy.
  2. Select one of the following:
    • Specific groups to limit applicable Call Queue, Auto Attendant, and Teams Phone Agent resource accounts, and then select the Microsoft 365 security groups that contain these resource accounts.
    • All users to apply the policy to all resource accounts.
  3. Select Next.

Set limits and alerts

  1. Configure monthly spending limits.
  2. Optionally configure per-resource-account limits.
  3. Optionally configure policy-level and user-level alerts.
  4. Select Next.

Billing method

  1. Use the default spending policy billing method, or override it if you're a Global admin or Billing admin.
  2. Select Next.

Review and add the policy

  1. Verify scope, services, billing method, limits, and alerts.
  2. Select Create spending policy.

Activation prerequisites and charging behavior

Shared voicemail AI triage runs only when both are true:

  • A spending policy is configured for AI Triage for Shared Voicemail for the applicable resource account in Microsoft 365 admin center.
  • An "AI triage for shared voicemails" template is selected under the specific Auto Attendant, Call Queue, or Teams Phone Agent settings in 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 attribution

Shared voicemail AI triage is billed once per processed voicemail, regardless of how many users receive the voicemail.

The charge 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, the root resource account associated with the phone number is used for billing.