Auto Attendant That Routes Callers, Not Runs Them in Circles
Answer every call instantly, send people to the right team on the first try, and keep a working path to a human. Build and change menus from a browser — no engineer, no downtime.
- ✓ Included in every plan
- ✓ Change menus in minutes
- ✓ 99.9% uptime SLA
An auto attendant is an automated menu that answers inbound calls and routes each caller to the right extension, department, ring group or voicemail box based on the option they choose.
It does the job a switchboard operator used to do for the routing step: greet the caller, find out what they need, and connect them — without putting anyone on hold first.
What is an auto attendant?
An auto attendant picks up an inbound call, plays a greeting, presents a short set of options, and transfers the caller based on the key they press or the phrase they say. Typical destinations are a department ring group, a specific extension, a voicemail box, or an external number such as an on-call mobile.
The practical benefit is that no call goes unanswered during busy periods, and callers stop being transferred twice before reaching the right person. The practical risk is that a badly structured menu turns a 20-second call into a two-minute maze, which is why the structure section below matters more than the feature list.
Auto attendant vs IVR vs AI receptionist
These three are often used interchangeably in sales material, but they do genuinely different amounts of work. The distinction is how much the system can decide or retrieve on its own.
| Auto attendant | IVR | AI receptionist | |
|---|---|---|---|
| Caller input | Keypad, simple voice | Keypad and voice prompts | Natural speech |
| Main job | Route the call | Route, plus collect and act on data | Understand intent and resolve or route |
| Back-end lookups | No | Yes — balances, order status, payments | Yes, plus calendar and CRM actions |
| Menu structure | Fixed tree | Fixed tree with branching logic | No fixed tree |
| Best fit | Most businesses, most of the time | Self-service transactions at volume | High inbound volume, varied requests |
Most teams asking for an "IVR" actually need a well-built auto attendant. Add true IVR when callers need to complete a transaction without an agent. Consider an AI receptionist when the range of requests is too wide to express as a menu at all.
How should you structure a menu?
Keep it to five options or fewer at any level, and put the most-requested option first. Callers decide as soon as they hear something that matches their need, so burying "sales" at option six means most of them have already pressed something else or started pressing zero.
A structure that holds up in practice:
- Greet and orient in one sentence. Name the company, then go straight to options. Long branding messages are heard as hold time.
- Order by call volume, not by org chart. Check your call reports and rank the menu to match what people actually call about.
- Announce the escape first. "Press 0 at any time to reach someone" removes most of the frustration before it starts.
- Avoid a third level. Two levels deep is the practical ceiling for keypad menus.
- Handle no input and wrong input. Repeat once, then route to a human rather than looping.
- Set different after-hours behavior. A menu offering a closed department wastes the caller's time.
When does an auto attendant frustrate callers?
When it is built around the company rather than the caller. The specific failure patterns are consistent and worth naming plainly, because every one of them is avoidable:
- No path to a person. The most damaging one. If 0 does nothing, callers hang up and call a competitor.
- Too many options. Past about five, callers stop tracking and start guessing.
- Menus that mirror the internal org chart. Callers do not know which department owns their problem.
- Dead ends. An option that leads to an unmonitored voicemail is worse than no option.
- Asking for information twice. If the menu collects an account number, the agent should see it on screen-pop rather than asking again.
If a department's voicemail is not monitored daily, do not offer it as a menu option. Route to a ring group with real coverage instead.
How do you set one up?
Build the menu in the admin console, record or generate the greeting, map each key to a destination, and set separate business-hours and after-hours routing. Changes take effect immediately, so you can adjust a menu during an unexpected volume spike rather than filing a ticket.
Auto attendant and call routing are included in every plan at $15, $25 and $40 per user per month, with a 14-day free trial — there is no separate license for menu building. It runs on the same geo-redundant platform as the rest of the system under a 99.9% uptime SLA. See the cloud phone system for the wider feature set, call center software if you need queueing and supervisor tools on top, or small business phone systems for a smaller setup.
Frequently asked questions
What is an auto attendant?
An auto attendant is an automated menu that answers inbound calls and routes them to the right extension, department or voicemail based on what the caller selects. It replaces a human operator for the routing step.
What is the difference between an auto attendant and an IVR?
An auto attendant routes calls. An IVR can also collect and act on information, such as reading an account balance or taking a payment, by connecting to a back-end system. Every IVR includes auto attendant behavior, but not every auto attendant is an IVR.
How many menu options should an auto attendant have?
Five or fewer at any level. Callers hold roughly the first few options in working memory, so longer menus cause repeats and mis-presses. Put the most-requested option first, since most callers choose before hearing the full list.
Can callers always reach a human?
They should be able to. Always map a key such as 0 to a live person or a ring group, and state it in the greeting. Menus with no escape route are the single most common cause of caller frustration and abandoned calls.
Is an auto attendant included in Salamtalk plans?
Yes. Auto attendant and call routing are included in every plan, starting at $15 per user per month with a 14-day free trial. There is no separate license for menu building.
Build a menu callers do not fight
Start a 14-day free trial, or talk to our team about mapping your call flows before you migrate.