An auto attendant is the menu that answers your main number: "For sales, press 1." Done well, it saves everyone a transfer. Done badly, it is the first thing a customer remembers about your company. Most of the bad ones fail in the same four ways, and all of them are fixable in an afternoon.
Keep it shallow
Every level of menu is a chance for a caller to give up or press the wrong key. One level is usually enough. Two is the practical limit for most small and mid-sized businesses. If you find yourself designing a third level, the real problem is that too many destinations share one number, and you may be better off giving the busiest ones their own numbers.
Keep the top level to four or five options. People remember the first and last options best, so put the most common destination first. Look at your last month of calls to see what that is, rather than relying on how the org chart looks.
Word the options as the caller would say them
Callers think in their own terms, not yours. They say "I have a question about my bill", and your menu says "Accounts receivable". They say "something broke", and your menu says "Tier 1 support".
- Name the option after the problem: "For a question about an invoice, press 2."
- Say what the option is before the key. "For billing, press 2" works better than "Press 2 for billing" because the caller waits for the thing they want and then acts.
- Avoid internal names for teams and systems.
- Keep each option to a few words. Read the script aloud at a normal pace. If you run out of breath, cut it.
- Do not read out the entire menu twice. Say it once, and repeat only when asked or after a pause.
Always leave a way to a person
Some callers will not fit any option, and some will not listen to options at all. Give them a key, usually 0, that goes to a person or a general queue, and say so in the greeting: "To speak to someone, press 0 at any time." Also decide what happens when a caller presses nothing. A few seconds of silence should route to the same place. A menu that repeats itself three times and then hangs up is a trap.
Set hours and holidays before the calendar does it for you
The most common failure is a menu that tells the caller to "press 1 for sales" at 9 p.m. when sales has gone home. Build separate behavior for open and closed hours.
- Open hours: the full menu.
- After hours: a short greeting that says when you open, and options that still work, such as voicemail, an emergency contact if you have one, or a callback request.
- Holidays: a separate schedule with its own greeting, switched on for specific dates. Record it the week before and list the dates in your calendar for the year.
- Lunch and short closures: if you really close for an hour, handle it, but think about whether the phones should be answered anyway.
Test the moments when the schedule switches, such as opening time and the start of a holiday. This is where a menu goes wrong most quietly.
A worked example
Bell & Ortiz LLP has a main line, 000-001-0100, with a menu that reads like a table of contents: seven options, three of them for departments clients have never heard of. The office manager pulls a month of calls. Most of them are one of three things: a question about a bill, a question about a matter, and a request for a named attorney.
She rebuilds the menu around those. Press 1 for a question about an invoice. Press 2 for a question about a case or matter. Press 3 to find an attorney by name, using the dial-by-name directory. Press 0 for the front desk. Everything else, such as vendors and recruiters, goes to the front desk. After 6 p.m. the greeting says when the office reopens and offers voicemail by attorney. She records a holiday greeting for each public holiday the firm observes and sets the dates for the year in January.
Test it like a stranger
- Call from a mobile phone that is not on your account, at a time when you are open, and follow every option to the end.
- Call after hours and on a scheduled holiday. Confirm the right greeting plays.
- Press nothing, then press an invalid key, then press 0. Each should do something sensible.
- Ask someone who has never heard the menu to call and find a department. Do not coach them. Watch where they hesitate.
- Re-test whenever a team changes name or a phone number moves.
Common mistakes
- Recording the greeting in a noisy room, or using a different voice for each submenu.
- Announcing "your call is important to us" before the options. It delays the thing the caller wants.
- Leaving a departed employee's name in the directory and the options.
- Sending every option to a voicemail box nobody reads.
- Forgetting that the menu is also what an AI receptionist or an integrated system hears when it calls you.
A good menu is short enough to remember and honest about what each key does. Revisit it every few months with the previous quarter's call log beside you, and remove an option when you cannot find a reason it exists.