IVR and phone menus

IVR Menu Design: How Many Levels, Options and Prompts to Use

How to design a phone menu callers can follow: how many options and levels to use, how to order and word them, and how to test the result before going live.

Call editorial team · Published · 5 min read

A phone menu is a conversation with someone you cannot see. They cannot scroll back, skim ahead or glance at a list. They hear each option once, in order, while thinking about their own problem. Every design decision follows from that: keep it short, keep it in their words, and never make them remember more than they can.

A person sketching a phone menu flow on paper beside a desk phone
Illustrative image

This guide walks through the choices you have to make: how to learn why people call, how many options and levels to use, how to order and word them, how to handle the edges, and how to test. If you are brand new to the topic, start with What Is IVR?.

Start from why people call

Before you open any settings, list the reasons people phone you. Use real evidence: call logs, voicemail, email subjects, and what your front desk says they hear most. Group the reasons into a handful of categories and put a rough share beside each.

From call reasons to menu

  1. CollectList actual reasons for calls over a few weeks.
  2. GroupMerge similar reasons into five or fewer categories.
  3. RankOrder by how often each occurs.
  4. NameDescribe each in the caller's words.
  5. RouteDecide where each ends: person, team, information or message.

The result usually surprises people. The top reason is often something simple that could be answered by a recording or an AI agent, such as opening hours, directions or order status.

How many options, how many levels

Short-term memory is limited. Most callers handle about four or five options comfortably. Beyond that, they forget the first ones before the last are finished. Levels add another cost: each menu a caller must pass through adds time and a chance to get lost.

Flat versus layered menus

One levelTwo levels
Best forSmall businesses with a few clear reasons for callingLarger organisations with distinct departments
StrengthFast. The caller reaches a destination in one choiceHandles more topics without a long list
WeaknessRuns out of room as services growSlower; the caller must choose twice
Rule of thumbFour or five optionsFour or five options at each level, never deeper than two

Ordering and wording

Order by frequency, not by org chart

Put the most common reason first. Callers listening for their option often decide on the first plausible one, so the order matters more than people expect. Keep related options together, and place "speak to someone" in the same position at every level.

Words callers actually use

Wording checklist

  • Each option fits in about five words
  • No jargon or abbreviations
  • Option comes before the key
  • Options are mutually exclusive
  • Related options sit together
  • The "other" and "speak to someone" options are easy to find

Designing for the edges

Menus work smoothly until a caller does something unplanned. The edge cases decide how the menu feels.

Plan for these situations

  • No key pressedRepeat the choices once, then offer a person or voicemail.
  • Wrong key pressedSay the key is not an option, then repeat the choices.
  • Caller wants a personMake the route obvious and consistent, on the same key everywhere.
  • Nobody is availableOffer a callback or voicemail rather than ending the call.
  • Closed hoursGive hours and a next step.

Related guides: Letting Callers Reach a Person Quickly, Using Callbacks and Voicemail in Your IVR and Routing Calls by Business Hours, Holidays and Closures.

Language and accessibility

If a meaningful share of your callers speak another language, offer a language choice at the very start, in each language, before anything else. Allow enough time between options for callers who need longer to respond, repeat on request, and avoid relying on keypad entry alone for callers who cannot use one.

A worked example

Take a hypothetical physiotherapy practice with three therapists and one front-desk person. A month of call notes shows four main reasons: book or change an appointment, ask about opening hours and location, ask about billing or insurance, and speak to a therapist about treatment. A final group is everything else.

ReasonShare of calls (noted by staff)Where it should go
Book or change an appointmentMost callsFront desk, or an AI agent that can take a booking request
Hours and locationA fair numberA short recorded answer, with the option to continue
Billing or insuranceSomeFront desk during office hours, message otherwise
Therapist about treatmentA fewMessage for the therapist, or transfer if they are free
Something elseRareA person

A one-level menu with four options and a "speak to someone" key covers all of that. There is no need for a second level, and the common reasons come first. The practice then records the greeting, tests it with a patient who has never called, and checks the numbers after a month. If many callers choose "something else," they add or reword an option. The whole exercise takes an afternoon, and it is easy to repeat when services change.

Writing the prompts

A good prompt sounds like a helpful person talking, not a legal notice. Keep sentences short and keep the key near the end of each option, so the caller hears the label first.

For help with voice quality and whether to record or use synthetic speech, see Creating IVR Prompts: Recording vs Text-to-Speech.

Testing before you launch

  1. Call the menu from a mobile phone, not a computer.
  2. Ask someone unfamiliar with your business to call and say what they thought each option meant.
  3. Try every path to the end, including wrong keys, silence and the route to a person.
  4. Time the journey from greeting to a person and from greeting to an answer.
  5. Call outside hours and on a holiday setting.

After launch, review call data and adjust, as described in Analyzing and Improving Your IVR. A menu is never finished; callers' reasons change.

Doing it in Call

In Call, the first thing a caller meets is usually an AI agent on a phone line, which can answer questions and put the caller through to a person when asked. You choose the line's main language, which agent answers, and which people or numbers are put through, with their own hours. Queues carry their own hours, closed greeting, required skill and overflow queue. Before real callers arrive, you can use the routing simulator to see where a call would go and place a practice call to hear the experience. See Setting Up IVR and Business Hours in Call and IVR vs Voice AI Agents.

Frequently asked questions

How many options should a phone menu have?

Four or five per level is a good limit. More than that and callers forget the early ones.

How many levels are too many?

Two is usually the most callers will tolerate. If you need a third, consider merging options or handing detail to a person.

Should I put the key before or after the label?

Say what it is first, then the key: "For billing, press 1." Callers then know whether to listen for the key.

What order should options be in?

Most frequent first, with related ones grouped, and the route to a person in the same place on every level.

How do I test a menu?

Call it from a phone, ask someone new to your business to try it, test every path including mistakes, and time the journey.

Do I need a language choice?

Only if a meaningful share of callers need one. If so, offer it at the very start, spoken in each language.

Build a simple call flow for your phone line in Call

In the demo console you can try incoming calls in a simulation.

Related guides