Skip to content
Operations November 7, 2026 11 min read

IVR Menu Design: Options, Order and Scripts

How to design an IVR menu callers can use: start from call reasons, keep options few, put the action before the digit, always offer a person, and test it.

D
November 7, 2026

Quick answer

Design an IVR menu from the reasons people call, not your org chart. Keep each menu to about four options, because research on working memory points to roughly four chunks. Put the most common reason first, say the action before the digit, keep the tree shallow, always offer a person, use plain words, and test with real callers by tracking menu abandons, misroutes and zero-outs.

An IVR menu is a small piece of writing that every caller has to use under pressure, one time, without being able to scroll back. Most bad menus are not bad technology. They are menus written from the inside: they list departments, they use internal names, and they put the thing most callers want in the fourth position after a long preamble.

This guide is the global how-to. It covers structure, option count, ordering, wording and testing, and ends with a before-and-after script. If your callers are in the Gulf or speak several languages, read it together with our guide to IVR design for Gulf callers. For the definition, see what is IVR.

Start from call reasons, not the org chart

Before you write a prompt, find out why people call. Export a few weeks of call records or agent dispositions and count them. If you do not have good data yet, ask agents to list the five reasons they hear most, then check that against whatever records exist.

Put the result in a simple table:

Call reason (caller's words)Share of callsCan it be self-served?
Check or change an appointmentfrom your dataOften
Where is my orderfrom your dataIf you can look it up
Billing questionfrom your dataSometimes
A fault or complaintfrom your dataRarely, needs a person

The rows are illustrative; the shares must come from your own records. Two rules follow. Name each option with the caller's words ("a bill", "an appointment") and not yours ("accounts receivable", "customer relations"). And rank by share, because the order of the menu should follow the order of the demand.

How many options per menu, and why fewer is safer

There is no standard for the number of options. Be careful with any article that states one as a fact. What exists is research on how much a person can hold in mind at once. Cowan's review of the evidence concludes that "a single, central capacity limit averaging about four chunks is implicated" (Cowan, 2001, Behavioral and Brain Sciences 24(1)).

That is not a law about phone menus, and it is an average, but it explains why long menus fail. A caller listening to a menu cannot re-read it. They must hold each option, compare it with the reason they have in mind and wait to see if a better one comes. By the time option six is read, option two has faded. Our practical reading is:

  • Aim for about four options on a menu, with a way to a person as one of them or as a standing instruction.
  • If you have more than four real reasons, move the less common ones under a single "something else" option, rather than reading them all.
  • Treat the number as a judgement to test, not a rule. A menu of five that your data shows works well is fine. A menu of three that sends 30% of callers to the wrong place is not.

Order: most common reason first, and the action before the digit

Put the most common reason first. The caller who hears their reason straight away can stop listening and press.

Then say the action before the digit. Compare:

Digit firstAction first
"Press 1 for appointments.""For appointments, press 1."

With the digit first, the caller has to remember "1" while waiting to learn what it means, then decide. With the action first, the caller listens for their own reason, and the digit arrives when they are ready to act on it. It is a small change that costs nothing.

Depth versus breadth: keep the tree shallow

Every extra level has a cost: another prompt, another chance to press the wrong key, another reason to give up. A flat menu of four with one "something else" branch usually serves callers better than a tidy three-level tree.

  • Put the common reasons at the first level.
  • Allow a second level only where one option really splits into two or three different jobs.
  • Never go to a third level without a strong reason.
  • On every level, give a way back and a way to a person.

Always offer a way to a person

A menu without a way out makes people angry and wastes the effort you put into the rest of it. Say early that a person is available, and make the key work at every level, not only the first.

Some rules now require it. Spain's Ley 10/2025, Article 8.2, says that when a customer asks, the company must guarantee personalised attention from the options in the main telephone menu, and that automated systems must let the customer ask for personalised attention at any moment from the start. It defines personalised attention as given directly by a human operator who answers in real time and identifies themselves at the start, and it adds that 95% of such requests must be answered, on average, in under three minutes (BOE consolidated text, checked November 7, 2026). That law applies to the companies it covers, in Spain. Read our summary of Ley 10/2025 for who is in scope.

Even where no law applies, a human option is good practice. If you are worried about the load, reduce the reasons that need a person, not the access to one. And if the person option leads to a wait, offer a callback; see queue callback.

Writing prompts: short, plain words, no marketing in the menu

  • One idea per sentence. "Thank you for calling. Your call may be recorded for quality." is two sentences and one is unavoidable. Do not add a third.
  • No marketing in the menu. Promotions delay the caller's reason for calling. If they must be there, put them after the caller has a path, or on hold.
  • Use the caller's words. Test the labels on someone outside the company.
  • Do not say "please listen carefully, our options have changed." It is filler.
  • Do not make a known customer identify themselves twice. The IVR builder has a smart greeting that recognises the caller before the menu and a CRM lookup node, so a known caller need not be asked.
  • Record, do not assume. A voice that is clear and unhurried beats a clever script. See voice packs for how voices are managed on the platform.

Keypad conventions callers already know

Callers already know the keypad. ITU-T Recommendation E.161, "Arrangement of digits, letters and symbols on telephones", is the standard that covers how those keys are arranged (ITU-T E.161, base edition 02/01 with Amendment 1 of 06/14, both listed as in force; checked November 7, 2026). You do not need to quote it to callers, but its lesson is practical: keep to the keys on the pad.

  • Use digits for choices. Use the star and hash symbols for navigation only, and be consistent: the same key should mean "go back" or "repeat" on every menu.
  • Do not ask callers to spell with letters on the keypad unless you have no choice. It is slow and error-prone.
  • Make sure digit entry works on every route. If a keypress is lost on one carrier, the menu looks broken; see what is DTMF.
  • Accept the digit at once. Do not make callers wait for the prompt to end before a key is recognised.

Language selection for multilingual callers

If you serve callers in more than one language, ask for the language early, in each language. A single English prompt asking people to pick a language excludes the people who need it. The prompt for each language should be in that language, so an Arabic option reads العربية and plays in Arabic, followed by the same menu in that language.

The IVR builder lets the caller choose a language, then runs the rest of the flow on the matching voice pack, so a language is a branch of one flow rather than a separate flow. Dialect, voice and script issues for Gulf callers are in the Gulf IVR guide.

Self-service that removes calls

A menu gets shorter when fewer people need it. The IVR builder has nodes for the jobs that do not need a person (see the IVR builder page and the customer service solution):

  • Check a booking and manage a booking: the caller can read, move or cancel an appointment without an agent.
  • Hear queue status and request a callback: the caller can hold their place without staying on the line.
  • WhatsApp deflect: offer a WhatsApp thread instead of a hold queue.
  • CRM lookup: bring the caller's record into the flow.

The platform has 40 node types in all. Use only the ones your callers need. Where a caller wants to talk rather than press keys, read conversational IVR versus an AI voice agent. For routing the numbers into a queue, see how to set up an inbound queue.

Testing and measuring a menu

Test it before launch with people who did not write it. Give them a task ("you want to move your appointment") and watch where they hesitate. Then measure after launch.

MeasureWhat a high value suggests
Menu abandonsThe menu is too long or the first prompt is too slow.
Misroutes (transferred, then re-routed)Option labels do not match caller language.
Zero-outs (pressed for a person at once)Callers do not trust the menu, or their reason is missing.
Timeouts and invalid keysPrompts are unclear, or digit entry is failing on a route.

Change one thing at a time. The A/B split node in the IVR builder splits callers between two versions of a branch and lets you read the analytics on the split, so the wording that works better wins on evidence. A flow goes live as a published version, so you know which version produced which numbers.

An example menu script, before and after

Both scripts are illustrative.

Before (a long preamble before the first useful word):

"Welcome to Example Company, your trusted partner since the day we opened. Please listen carefully as our menu options have changed. For sales, press 1. For accounts, press 2. For technical support, press 3. For human resources, press 4. For billing enquiries, press 5. For appointments, press 6. To hear these options again, press 9."

After:

"Thank you for calling Example Company. To check or change an appointment, press 1. For a bill or payment, press 2. For a fault, press 3. For anything else, press 0 to speak to a person. You can press 0 at any time."

What changed: the most common reason (appointments, in this example) comes first; the preamble is gone; internal departments became caller reasons; there are four choices; and a person is available from the start and at any point.

Frequently Asked Questions

How many options should an IVR menu have?

No standard fixes a number. Cowan's 2001 review concludes that people can hold about four chunks in working memory, and a caller listening to a menu cannot re-read it, so fewer options are safer. Treat four as a design target rather than a rule, group the long tail under one option, and test the menu with real callers.

Is the five-option rule real?

It is a rule of thumb repeated widely, but we found no standard behind it. The research we cite points to about four chunks of working memory on average. Use the number as a starting point, then let menu abandons, misroutes and zero-outs from your own calls decide.

Should the action come before the digit?

Yes. Say what the option does first and the key second, for example: for your balance, press 1. If the digit comes first, callers must hold it in memory while they wait for the meaning. Putting the action first lets them listen for their reason and then act.

How do I let callers reach a person?

Offer it from the first menu, not only after several levels, and do not hide it behind a wrong-key loop. Some laws now require it: Spain's Ley 10/2025, Article 8.2, requires that automated systems let customers ask for personalised attention at any moment from the start. Check whether a rule applies to you.

Should an IVR be deep or wide?

Keep it shallow. Each extra level adds a prompt, a chance of a wrong key and a reason to hang up. If you need more than one level, make the second level the exception, and give a way back and a way to a person on every screen.

How do I know whether my IVR menu works?

Measure menu abandons (callers who hang up in the menu), misroutes (callers transferred and then re-routed), zero-outs (callers who press for a person at once) and timeouts. Compare them before and after any change. The DialerBee IVR builder has an A/B split node for comparing two versions of a branch.

Sources

  1. N. Cowan, "The magical number 4 in short-term memory: A reconsideration of mental storage capacity", Behavioral and Brain Sciences 24(1), 2001. Cambridge Core abstract (checked November 7, 2026).
  2. ITU-T Recommendation E.161, arrangement of digits, letters and symbols on telephones. itu.int/rec/T-REC-E.161 (checked November 7, 2026).
  3. Ley 10/2025, de 26 de diciembre, consolidated text, Boletin Oficial del Estado: Article 8.2. boe.es/eli/es/l/2025/12/26/10/con (checked November 7, 2026). The BOE marks the consolidated page as informative; the published BOE text is the authoritative version.

Related reading

Disclaimer: This article is general information, not legal advice. DialerBee does not provide legal advice or guarantee regulatory compliance. The Spanish law is summarised from the BOE consolidated text as read on November 7, 2026. Confirm current requirements with qualified counsel and the competent authority.

Ready to see DialerBee in action?

Request a 15-minute live demo, or start a 14-day free trial — no slides, no commitment. Calling starts once your own SIP trunk or PBX is connected and approved.

14-day free trial · free AI credit · no card · 11 languages · BYOC · compliance-supporting controls