Analytics
Auto attendant: answer every call and route it in seconds
Reviewed by Sujan ThapaliyaLast updated
What is a auto attendant?
How it works
Auto attendant in four steps
No implementation project. Most teams are dialling the same day they sign up.
- 1
Write the menu around call volume
Three to five options on one level, ordered by how many callers want each — not by the organisation chart. The option most people need goes first. - 2
Record or generate the greeting
Upload a recording or generate one from text. Keep it under twelve seconds to the first option; every second before a caller can choose costs you some of them. - 3
Set the routing behind each option
A queue, a hunt group, an individual, an AI receptionist, or a mailbox — with a different destination for out of hours and for holidays. - 4
Give every branch a fallback
What happens when nobody answers, when the caller presses nothing, and when they press zero. A menu without a fallback is where calls disappear.
Capabilities
What you get
Keypress and speech input
Schedules and holidays
Multi-level menus, used sparingly
Zero-out to a person
Per-number menus
Reporting on the menu itself
How do you write a menu callers do not hate?
Complaints about phone menus are almost never about automation. They are about depth, ordering and dead ends, and each one is measurable before a caller tells you.
| What to measure | Healthy | What a bad number means |
|---|---|---|
| Time to the first option | Under 12 seconds | The greeting is doing work the routing should do |
| Menu depth | One level, two at most | Each extra level loses callers who were choosing correctly |
| Zero-out rate | Under 15% | Callers cannot find themselves in your options |
| Drop-off inside the menu | Under 5% | People are hanging up rather than choosing |
Where an auto attendant stops being the right answer
A menu is a routing tool. Once callers are waiting behind it, you need a call queue rather than a longer greeting. Once they are asking for things the menu cannot express, you need either an IVR that transacts or an AI receptionist that simply asks what they want and acts on the answer.
The failure worth naming: a menu built to protect a team from calls. It shows up as a rising zero-out rate and falling first-contact resolution, and no amount of re-recording the greeting fixes it.
Fit
Who a auto attendant is right for
If none of these describe you, a different mode probably fits better; the comparison pages lay out the trade-offs honestly.
- Businesses where one number reaches several teams
- Practices and offices that need reception cover without a receptionist
- Any line currently answered by whoever happens to be free
- Teams running campaign numbers that need their own greeting
Frequently asked questions
What is the difference between an auto attendant and an IVR?
How many options should the menu have?
Can I write my own auto attendant script?
What happens outside business hours?
Sources
- Combating Spoofed Robocalls with Caller ID Authentication — Federal Communications CommissionThe STIR/SHAKEN framework, the attestation levels carriers sign calls with, and the mandate requiring providers to authenticate caller ID.
- 47 U.S.C. § 227 — Restrictions on the use of telephone equipment — Cornell Legal Information InstituteThe Telephone Consumer Protection Act itself — the consent requirements, calling-hours limits, and private right of action.
Try auto attendant without a contract
No seat licences, no minimum commitment. Add a number, top up a wallet, and start. Release the number whenever you like; your remaining balance stays yours.
- No subscription
- Owned numbers with Attestation A
- Compliance built in