How to Set Up an Auto Attendant in Microsoft Teams

What an auto attendant actually is

A Microsoft Teams auto attendant is the automated menu that answers an inbound call and routes it — "press 1 for sales, press 2 for support." In Teams it's a configuration object rather than a physical device, and it can route to people, to call queues, to other auto attendants, to voicemail, or to external numbers.

Done well, it gets callers to the right person without anyone touching a phone. Done badly, it's the reason people hang up and call your competitor. The difference is almost entirely in the design decisions, not the technical setup.

What you need before you start

Three prerequisites, and getting them wrong accounts for most of the auto attendant problems we get called about.

A resource account

Auto attendants and call queues don't attach to a person. They attach to a resource account — an account type that exists to hold a phone number and a routing configuration. Every auto attendant needs one.

Resource accounts need a license. Microsoft provides a free Virtual User license for exactly this purpose, but the allocation is finite. If you're building several attendants and several queues, count them up first. Running out mid-build is a frustrating way to discover the limit.

A phone number, if it answers external calls

An auto attendant that only handles internal transfers doesn't need a number. One that answers your main line does, and that number has to come from somewhere — Microsoft Calling Plans, a carrier via Operator Connect, or Direct Routing.

Teams Phone licensing for the people it routes to

Routing a caller to someone who can't receive PSTN calls produces a dead end. Confirm the destinations are licensed before you build the tree. See Teams Phone licensing explained.

Building it, step by step

1. Create the resource account. Teams admin center, under Voice. Give it a name you'll recognize in six months — "AA-MainLine" beats "Resource Account 3."
2. Assign the Virtual User license in the Microsoft 365 admin center. The account won't work without it.
3. Assign the phone number to the resource account, if the attendant answers an outside line.
4. Create the auto attendant under Voice, Auto attendants. Link the resource account you just made.
5. Set the operator. Where does a caller go if they press 0, or say nothing at all? Never leave this empty — an attendant with no operator is a dead end by design.
6. Set the language and time zone. The time zone drives business hours. Get it wrong and your after-hours greeting plays at lunchtime.
7. Record or generate the greeting. Text-to-speech is fine while you're testing. Record a real voice before it goes live — a synthesized greeting is the first thing a caller hears about your business.
8. Build the menu options. Map each key to a destination: a person, a call queue, another attendant, voicemail, or an external number.
9. Set business hours, then build the separate after-hours call flow. These are different trees and can behave completely differently.
10. Add holidays. Define them once and attach the greeting you want. This is the step everyone skips.
11. Set dial scope — whether callers can dial by name or extension, and which directory they can search.

The design decisions that matter more than the setup

Keep the menu to three or four options

People can hold about three or four options in working memory while listening. Past that, they stop tracking, press 0, or hang up. If your menu has seven options because your org chart has seven departments, you've designed for yourself rather than the caller.

Build the menu around the reasons people call, in order of how often they call for them. If 60% of your inbound volume is one thing, that's option 1.

Say the department before the number

"For billing, press 2" works. "Press 2 for billing" makes people wait through the number before they know whether they want it — and on a long menu they lose track. Small change, measurable effect.

Never nest more than one level

A menu inside a menu inside a menu is where callers give up. If you genuinely need depth, ask whether the first menu is doing the wrong job.

Always leave an escape

Dial-by-name, an operator on 0, or both. Every menu needs a way to reach a human without navigating correctly.

Handle holidays properly

A caller reaching a cheerful "we're open Monday to Friday" message on Thanksgiving learns something about how carefully your business is run. Define your holidays for the year in one sitting.

Testing before you trust it

Call the number yourself and walk every branch. Specifically:

• Each menu option, all the way through to a person answering
• Pressing 0
• Pressing nothing at all
• Pressing an invalid key
• Calling after hours
• Calling on a defined holiday, by temporarily setting one to today

The invalid-key and press-nothing paths are the ones most often left unconfigured, and they're the ones confused callers hit.

Then find out whether it actually works

Routing correctly and working well are different things. The question that matters is whether callers are dropping out of the menu before they reach anyone — and native Teams reporting won't tell you that. Menu abandonment is invisible in the admin center.

If a meaningful share of your callers hang up during the greeting or between options, the menu is too long, the options don't match why they're calling, or the greeting is burying the useful part. You can only fix what you can see. Our Customer Experience Oracle for Teams shows where callers drop out of the tree, along with queue waits and abandonment by time of day.

Getting it built for you

Callifi configures auto attendants as part of every Teams Phone deployment — including the recording, the holiday calendar, and the testing most people skip. See Teams Phone with Callifi, the general auto attendant design guide, or talk to us.