How should we design Teams auto attendants and call queues?

Key facts

• Auto attendants answer and route calls; call queues hold and distribute calls to agents.
• Every auto attendant and call queue that has a phone number needs a resource account with a Teams Phone Resource Account license.
• Routing methods include attendant, serial, round robin and longest idle, with optional presence-based routing.
• Every queue needs an overflow rule and a timeout rule, or callers wait with no way out.
• Shared voicemail goes to a Microsoft 365 group, so its members and alerts must be planned.

Know which tool does what

An auto attendant is the menu: it greets callers, applies business hours and holidays, offers options or dial by name, and routes the call. A call queue is the waiting line: it plays music, distributes calls to agents and decides what happens when nobody answers.

Good designs keep these roles separate. The main number lands on an auto attendant, each menu option goes to a call queue or person, and the queue handles agents, overflow and timeout. Auto attendants can be nested, for example a main menu that hands off to a department menu, but every extra layer adds caller frustration.

Design the menus

Start with call data or reception staff's knowledge of why people call. Put the most common reasons first.

• Keep each menu to about four or five options and say the most common one first.
• Offer an operator option on every menu so callers are never stuck.
• Use dial by name or extension only if callers actually know names or extensions.
• Record greetings with a consistent voice, or use text-to-speech and update it easily.
• Plan separate after-hours and holiday greetings and routing.
• Consider language options only if a real share of callers need them.

Choose routing methods for each queue

The routing method decides which agent gets the next call. Pick it per queue based on how the team works.

Handle overflow, timeout and voicemail

Every queue needs two exit rules. Overflow applies when too many callers are waiting; timeout applies when a caller has waited too long. Each can send calls to another queue, a person, an auto attendant, external number or shared voicemail. Set values that match the service level you promise, and test both paths.

Shared voicemail is delivered to a Microsoft 365 group mailbox. Decide who belongs to the group, how they get notified, and who is responsible for returning calls. Turn on transcription if it helps the team triage messages.

Agents, permissions and resource accounts

Agents can be added individually, through a Microsoft 365 group or through a Teams channel. A channel-based queue gives agents a shared space for notes and lets them take calls from the channel. Decide whether agents can opt out of taking calls and whether conference mode should be on, which usually speeds call connection.

Each auto attendant and queue with a phone number needs a resource account with a Teams Phone Resource Account license. Use clear naming so administrators can tell them apart. Authorized users can be given rights to change greetings and holiday schedules without full Teams admin access, which keeps day-to-day changes with the business.

Test before you port

Build the flows on temporary numbers and walk every path: each menu option, after-hours, holidays, overflow, timeout, voicemail and the operator option. Have real agents take test calls. Record the final design in a simple diagram so the next change does not depend on memory.

How Accred Consulting approaches it

Accred Consulting designs call flows with the people who answer the phones. During discovery we map current menus, hunt groups and after-hours rules, then propose simpler auto attendants and call queues with clear routing, overflow and voicemail. The US-based specialists assigned to your engagement build the resource accounts, queues and greetings, test every path on temporary numbers, and set up authorized users so your staff can change holiday schedules themselves. Handover includes a call flow diagram and documentation, with optional support retainers for ongoing changes.

Track record: 475+ client projects, 2,000+ migration workstreams and 210,000+ users migrated by a US-based team. Company facts · Case studies

Related questions