An auto attendant is the automated voice that answers a business line and connects callers without a human receptionist: "Thanks for calling Northbeam. For sales, press 1. For support, press 2." It picks up on the first ring, every time, and routes each caller to the right person, group, or mailbox.
If that sounds like an IVR, you are not wrong, and the difference between the two terms trips up almost everyone shopping for a phone system. Here is what an auto attendant actually does, where it stops and IVR begins, and how to build one that callers do not hang up on.
What an auto attendant does
Think of it as the receptionist's first ten seconds, automated. A caller dials your published number, and instead of ringing an empty desk or dumping into someone's personal voicemail, the system answers immediately, plays a greeting you recorded, and offers a short menu of destinations. Each keypress maps to somewhere useful:
- A person. "Press 3 for billing" rings Dana directly.
- A ring group. "Press 1 for sales" rings three reps at once, and whoever picks up first takes the call.
- A submenu. "Press 2 for support," which then offers existing tickets or a new issue.
- Information. Hours, address, or directions, played as a recording so nobody has to answer that call again.
- Voicemail. Which, on a modern system, arrives as readable text rather than a message nobody dials in to hear.
The payoff for a small company is out of proportion to what it costs. A four-person business with a decent menu answers like a forty-person one, and for many teams it replaces the monthly bill of a live phone answering service entirely, a bill that starts at $250 a month once you price it out (see the full answering service cost breakdown). Nobody is playing switchboard from their cell, no caller hears "hang on, let me find someone who can help," and the sales call that came in at 4:55pm on a Friday does not die in a personal mailbox until Monday.
Auto attendant vs IVR: what is the actual difference?
In everyday sales conversations the two words are used interchangeably, and for a small business they usually describe the same feature. The technical distinction is about how deep the system goes.
| Auto attendant | IVR (Interactive Voice Response) | |
|---|---|---|
| Core job | Greet the caller and route the call | Greet, route, and interact with data |
| Caller input | Keypresses on a simple menu | Keypresses or speech, sometimes account numbers |
| Typical depth | One menu, maybe one submenu | Multi level trees, conditional branches |
| Talks to other systems | No | Yes: it can look up a balance, a ticket, or an order status |
| Who it suits | Nearly every small business | Banks, utilities, and anyone with a call center |
| What it costs | A plan feature, $29 per user on Phoner's Team plan | The same, if all you need is routing; more if it must query a database |
The practical read: an auto attendant is the routing half of IVR, and routing is the part a small business actually needs. When a vendor sells you an "IVR phone menu," what you are usually buying is an auto attendant with room to grow. You do not need the system that reads out a mortgage balance. You need the one that gets the roofing estimate to the person who does estimates.
What a good menu sounds like
Two real-shaped examples, both under fifteen seconds.
A three-person creative agency:
"Thanks for calling Northbeam. For new projects, press 1. For current clients, press 2. For billing, press 3. Or stay on the line and we'll connect you to the next available person."
A home services company:
"You've reached Corewood Roofing. If this is about a new estimate, press 1. To reschedule a visit, press 2. For anything else, press 0."
Both name the business immediately, put the most common reason for calling first, and always leave a path to a human. That last one is not a courtesy. The caller who cannot find a person is the caller who hangs up angriest, and they are often the one holding a checkbook.
How to set up an auto attendant in six steps
Step 1: List the reasons people actually call
Before touching any software, write down the three to five real reasons your phone rings. If you have call notes from the last week, read them. For each reason, decide the destination: a person, a group, or a mailbox. This ten minute exercise is the entire design job, and skipping it is why so many menus feel like a maze.
Step 2: Keep the top level to five options or fewer
Callers hold a menu in short-term memory. Past five options they stop listening and start pressing zero. If you genuinely need more paths, use one submenu, not seven top-level choices. Most small businesses need three.
Step 3: Write and record the greeting
Aim for fifteen to twenty-five seconds. Name the business, list the options in "for X, press N" order, and say what zero does. Record it in a quiet room on the second take, or use a text-to-speech voice if you would rather not perform. Consistency beats charisma, and a slightly robotic voice that says the right things beats a warm one that rambles.
Step 4: Point each option somewhere, and give every branch a fallback
Map each digit to its teammate, ring group, submenu, or mailbox. Then decide what happens when nobody answers: after about twenty seconds, roll to voicemail or to another person. No caller should ever reach silence. Silence is how you lose someone permanently.
Step 5: Set business hours and the after-hours path
Inside hours, the full menu runs. Outside them, skip the menu, play a short greeting, and take a message. Ringing empty desks at 9pm wastes the caller's time and teaches them you do not answer. If the message comes back as a text transcript, someone can read it at a stoplight and call back first thing.
Step 6: Test-call every branch
Dial your own number from a personal cell. Press every digit. Press an invalid digit. Press nothing at all and wait. Every path should end somewhere sensible. Fix the dead ends now, then publish the number everywhere. Retest after any staffing change, because the menu that points at a person who left in March is worse than no menu at all.
The mistakes that make callers hang up
| Mistake | Why it costs you | The fix |
|---|---|---|
| More than five top-level options | Callers forget the early ones and guess | Cut to the three to five real call reasons |
| No path to a human | Your most motivated callers give up | Announce that zero reaches a person, and mean it |
| A greeting over thirty seconds | Hang-ups climb steeply past half a minute | Cut the preamble; they know you have a website |
| Menus three levels deep | It stops feeling like a receptionist and starts feeling like a maze | One submenu, maximum |
| Never test-calling it | Dead branches go unnoticed for months | Test quarterly, and after anyone leaves |
Do you actually need one?
Honestly, not always. A solo founder whose every call is worth answering personally should route the line straight to their phone and let voicemail-to-text catch the overflow. That is the $15 Starter plan, and a menu would only put a wall between them and their customers.
The auto attendant earns its keep the day two people split responsibilities, because that is the day callers start reaching the wrong one. If a good share of your inbound is people who would rather not have called at all, a simple question they could have answered themselves, it is also worth putting a chatbot trained on your own site content on the website, and reserving the phone line for the conversations that deserve a voice.
Frequently asked questions
What is an auto attendant on a phone system?
An auto attendant is an automated voice menu that answers incoming calls, plays a recorded greeting, and routes each caller to the right person, team, or voicemail box based on which key they press. It replaces the routing work of a human receptionist and answers instantly, at any hour, on every call.
What is the difference between an auto attendant and an IVR?
An auto attendant greets and routes. An IVR does that too, but can also interact with data, taking spoken input or account numbers and looking up a balance or an order. For most small businesses the two are effectively the same feature, and an auto attendant is all they need.
How much does an auto attendant cost?
On a cloud phone system it is a plan feature, not a separate purchase. Phoner includes an auto attendant with a visual menu builder on the Team plan at $29 per user per month, alongside ring groups, business texting, and call recording. On old PBX hardware, the same capability used to mean a five-figure install.
Can an auto attendant transfer to a cell phone?
Yes. Each menu option can ring any device your team is signed in on, including the app on a personal iPhone or Android, so "press 1 for sales" can ring three cell phones at once. The caller never sees a personal number, and nobody has to carry a second handset.
Where to go next
Building the menu is step three of setting up a business line. If you do not have the number yet, start with how to get a business phone number, then set up the IVR phone menu that sits in front of it. For the wider picture of what a modern system includes, the cloud phone system overview covers numbers, routing, recording, and voicemail in one place. And if the greeting itself is what you are stuck on, we wrote 32 professional voicemail greeting examples you can read straight off the page, plus phone greeting scripts for the recorded menu and for whoever picks up when the caller presses zero.
LINE OPEN
Get your business number
Phoner is a business phone system with ivr phone menu built in: a local or toll-free number your whole team can answer, with an IVR menu, voicemail-to-text, and routing from $15 per user per month. No hardware, no contracts.