Auto Attendant Menu Design — Prompts Callers Don't Hate

Callers tolerate a phone menu exactly as long as it's obviously helping them. The design rules are few and firm: identify yourself immediately, offer at most four or five options, put the most-chosen option first, say the destination before the digit, and always staff the 0 key.

The rules

1. Identify first: "Thank you for calling [name]" — callers verify they dialed right before anything else.
2. ≤5 options. Beyond that, nobody remembers option 2 by the time you reach 6. Deep organizations need layered menus or a staffed 0, not longer lists.
3. Destination before digit: "For scheduling, press 1" — callers listen for their need, then grab the number. The reverse loses them.
4. Order by call volume, not org chart. If 60% of calls are scheduling, scheduling is option 1.
5. 0 = human, always, and route it somewhere actually answered.
6. No information ghettos: hours and address deserve a key only if they meaningfully deflect calls; otherwise they pad the prompt.

A template that works

"Thank you for calling [organization]. If this is a medical emergency, hang up and dial 911. For scheduling, press 1. For billing, press 2. For prescription refills, press 3. For all other calls, or to reach the front desk, press 0."

Fifteen seconds. The emergency line leads for clinical contexts; commercial menus drop it.

Multi-language pattern

A language gate ("For English, press 1; para español, oprima 2") should be the entire first menu — two keys, instantly — leading to parallel single-language menus. Bilingual prompts within one menu double its length for every caller.

Recording quality

One voice, one session, all variants (day/night/holiday) — see the recordings library conventions. Re-record the set when anything changes; a menu with two voices sounds broken even when it isn't.

Related articles

• Auto attendant setup
• Recordings library