How to Configure Call Queues, Auto Attendants, and Direct Routing in Microsoft Teams

Modern enterprise communications require migrating away from rigid legacy PBX hardware to agile, cloud-managed telephony platforms. Microsoft Teams Phone delivers enterprise-grade voice architecture capable of replacing traditional telecommunications systems. Central to this infrastructure are Auto Attendants (which provide automated interactive voice response menus) and Call Queues (which distribute incoming customer inquiries across designated agent groups). Integrating these services with Microsoft Calling Plans, Operator Connect, or custom Direct Routing Session Border Controllers (SBCs) guarantees high-availability call handling, flexible holiday routing, and granular agent governance.

Microsoft Teams Telephony Architecture: Connectivity Models

Deploying Teams Phone requires selecting an appropriate Public Switched Telephone Network (PSTN) transport architecture based on infrastructure scale, geographical carrier contracts, and regulatory constraints. The table below delineates the three primary PSTN options:

PSTN Connectivity Model	Infrastructure Responsibility	Best Suited For	Key Advantages & Trade-offs
Microsoft Calling Plans	100% cloud-hosted and managed directly by Microsoft.	Small to mid-sized businesses seeking rapid turn-up without local telecoms hardware.	Zero hardware overhead; billed directly through Microsoft 365 licensing, but carrier selection is locked.
Operator Connect	Managed by certified third-party telecommunications carriers.	Enterprises wanting to retain existing carrier relationships with managed PSTN peering.	Carrier handles all SBC infrastructure; configuration resides cleanly inside Teams Admin Centre.
Direct Routing	Customer-managed or partner-hosted Session Border Controllers (SBCs).	Global enterprises requiring analogue PBX integration, complex survivable branch appliances, or local SIP trunks.	Maximum control and interoperability with third-party PBX systems; requires dedicated SBC hardware and TLS certificates.

Establishing Resource Accounts and Telephone Number Binding

Auto Attendants and Call Queues cannot be linked directly to user accounts; they require dedicated “Resource Accounts” provisioned within the Microsoft 365 directory and licensed with zero-cost Microsoft Teams Phone Resource Account licenses.

1. Provisioning a Resource Account in Teams Admin Centre

1. Navigate to the Microsoft Teams Admin Centre (admin.teams.microsoft.com).
2. In the left navigation drawer, go to Voice > Resource accounts.
3. Click Add.
4. Configure resource attributes:
   • Display Name: A human-readable identifier (e.g., Main Support IVR or Tier 2 Escalations Queue).
   • Username: An Azure AD user principal name (e.g., [email protected]).
   • Resource Account Type: Designate either Auto attendant or Call queue.
5. Click Save.

2. Licensing and Assigning a Service Number

1. Open the Microsoft 365 Admin Centre (admin.microsoft.com), locate the newly provisioned resource account under Active users, and assign a Microsoft Teams Phone Resource Account licence.
2. Return to Voice > Resource accounts in the Teams Admin Centre, select the account, and click Assign/Unassign.
3. Select your telephone number type (Calling Plan, Operator Connect, or Direct Routing), assign an external service telephone number (Toll-Free or Geographic DID), and commit the binding.

Configuring an Interactive Voice Response (IVR) Auto Attendant

The Auto Attendant welcomes callers, provides informational audio prompts, and routes incoming calls based on touch-tone DTMF keypad inputs or speech recognition.

1. Setting Language, Operator, and Time Zone

1. In Teams Admin Centre, navigate to Voice > Auto attendants and click Add.
2. Specify an Auto Attendant Name (e.g., Corporate Reception Menu), designate your primary business time zone, and choose your preferred prompt language (e.g., English (United Kingdom)).
3. Optionally designate an Operator destination so callers can press 0 at any juncture to reach a human receptionist.

2. Designing Menu Prompts and Dial-by-Name Routing

1. Under Call flow, select Play an audio file (uploading a studio .wav or .mp3 recording) or choose Type a greeting message to leverage Microsoft’s text-to-speech engine.
2. Choose routing behaviour: Set up menu options.
3. Assign keypad DTMF buttons to operational paths:
   • Press 1: Redirect to Voice app > Sales Call Queue.
   • Press 2: Redirect to Voice app > Technical Support Queue.
   • Press 3: Route to Directory search > Dial by name (allowing callers to speak or spell an employee’s surname).

3. Defining Business Hours, After-Hours, and Holiday Schedules

Telephony flows must adapt when offices close or during bank holidays:

• Business Hours: Set working days and operational shifts (e.g., Monday through Friday, 08:30 to 17:30).
• After-Hours Flow: Define distinct routing when calls arrive outside schedule boundaries (e.g., play an after-hours prompt and route callers to an emergency voicemail box).
• Holiday Schedules: In Voice > Holidays, pre-configure national bank holidays. Inside the Auto Attendant, map these holiday events to bespoke holiday greeting audio clips.

Configuring Call Queues and Agent Distribution Algorithms

Call Queues hold callers in a virtual waiting room with custom hold music while distributing incoming calls across available staff.

1. Linking Queues to Agent Teams

1. Go to Voice > Call queues and click Add.
2. Assign a name and associate the previously created Resource Account.
3. Under Call agents, choose how agents are identified:
   • Add Users: Manually search and add individual staff members.
   • Add Groups: Bind the queue to a Microsoft 365 Group, Security Group, or specific Microsoft Teams Channel (e.g., IT Operations > General), allowing channel members to manage queue calls collaboratively.
4. Enable Conference mode (strongly recommended; reduces call connection latency by pre-initialising VoIP media bridges).

2. Selecting the Routing Algorithm

Select how incoming calls cycle through the agent roster:

• Attendant Routing: Rings all available agents simultaneously; the first agent to answer claims the call.
• Serial Routing: Rings agents one by one in a specified linear order.
• Round Robin: Distributes calls sequentially across all agents to balance incoming load evenly.
• Longest Idle: Routes the incoming call to the agent who has been off the phone for the longest duration, maximizing team fairness.

3. Establishing Overflow and Timeout Policies

To avoid indefinite customer wait times, configure escalation safety valves:

• Call Queue Maximum Size: Set a threshold (e.g., 15 calls). If the queue exceeds capacity, route excess callers to voicemail or an overflow queue.
• Call Timeout: Define a maximum hold duration (e.g., 20 minutes). Once exceeded, trigger a graceful redirect to an escalation group.

Troubleshooting Telephony Routing and Media Drops

When operating cloud voice infrastructure, administrators frequently address specific audio routing anomalies:

• Agents Not Receiving Queue Calls: Verify that agents have enabled the Receive calls from this queue toggle inside their personal Microsoft Teams client under Settings > Calls > Call queues. If an agent sets their presence status to Do Not Disturb, Teams suppresses queue calls unless presence-based routing is disabled in the queue configuration.
• One-Way Audio on Direct Routing Calls: Usually caused by asymmetric Network Address Translation (NAT) or firewall port blocking. Ensure UDP ports 49152–53247 and 3478–3481 are unobstructed between the SBC and Microsoft Teams transport relays.
• Direct Routing SBC TLS Handshake Failures: Microsoft enforces strict TLS 1.2/1.3 standards. Verify that the SBC certificate is issued by a Microsoft-approved public root Certificate Authority (CA) and that the Fully Qualified Domain Name (FQDN) in the certificate Common Name matches the SIP trunk domain registered in the Teams Admin Centre.