Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
Getting started
Once you complete the planning tasks in this article, follow these steps to get your Auto attendants and Call queues set up:
- Design call flows to identify the number of resource accounts, Teams Phone Agent, Auto Attendants, Call Queues, and associated configuration items you need.
- Plan for Auto Attendant and Call Queue authorized users who can be responsible for administrative changes to Auto attendants or Call queues.
- Get a Teams Phone Resource Account license for each resource account that you plan to create. These licenses are free, so we suggest getting a few extra in case you decide to make changes to your resource accounts in the future.
- Create a resource account for each Teams Phone Agent, Auto Attendant, and Call Queue that that directly answers calls.
- Assign a Teams Phone Resource Account license to each resource account.
- If the resource account is used to transfer calls externally, assign a pay-as-you-go license or communications credits to the resource account
- Get service numbers for the Teams Phone Agent, Auto attendant, and Call Queues that you want phone callers from outside your organization to call.
- For more information about service numbers, see transferring numbers from another provider or requesting new service numbers.
- Create click-to-call configurations for the Teams Phone Agent/Auto Attendant and Call Queues that you want users on your website or in your mobile applications to call.
- Create the holidays for which you want to have separate call routing in your Auto attendants.
- Create the groups, Teams channels, or Shifts scheduling groups that you want to use to contain the call agents for the Call queues.
- If you plan to enable dial by extension, ensure that you add your users' extension number to their Microsoft Entra ID profile.
Once you complete these steps, you're ready to create your Teams Phone Agents, Auto Attendants, and Call Queues. Refer to the workflow diagram that you created to determine what should be created first.
In the example diagram, it's recommended to create the sales and support call queues before creating the Contoso main auto attendant because the auto attendant needs to direct callers to the queues.
See the following articles for information on how to create Teams Phone Agent, Auto Attendant, and Call Queues:
Important
A user's Microsoft Entra ID GUID token is stored as part of the Auto attendant or Call queue configuration when the user is configured as:
- an Auto attendant or Call queue Authorized user.
- an Auto attendant Operator.
- a Person in Organization transfer point.
- an individual member of a Call queue.
The Teams Phone Agent, Auto Attendant, and Call Queue configurations aren't synchronized with Microsoft Entra ID lifecycle events. Teams administrators need to manually update configurations to remove this personal data when a user included in the configuration leaves the organization.
This doesn't apply to call queue representative memberships that are configured via distribution lists or channels. It also doesn't apply to users who are reached through the Dial by Name or Dial by Number feature of Auto attendants.
Alternate provisioning tools
Auto Attendant and Call Queue Backup and Bulk Provisioning Tools are a set of tools that provide a way to configure Auto attendants, Call queues, and Authorized users through Excel spreadsheets and PowerShell scripts.
Previous planning articles
- Overview
- Questions and answers tools (Teams Phone agent)
- Appointments tools (Teams Phone agent)
- Agents and Queues (Teams Phone agent)
- Third party voice agents
- Holidays
- Authorized users
- Shared call history
- Call priorities for call queues
- Recording calls
- Templates and resources
- Business decisions for Teams Phone Agents, Auto Attendants, and Call Queues
- Nesting call flows
- Reporting Considerations
- Technical prerequisites and licensing requirements
- Design call flows
- Supported configurations