IVR menu design best practices
A well designed IVR menu gets callers to the right person in seconds; a poor one makes them hang up. This guide gives you a practical method for IVR menu design: choosing the options, writing the prompts, handling errors and opening hours, and testing the menu before it goes live.
Before you write anything: start from why people call
The most common mistake is designing the phone menu around your org chart, with one key per department. Callers do not know your departments; they only know their problem. The right starting point is the real reasons people call.
Look at a few weeks of calls. Ask your agents, or use your reports and call outcomes, to find out why people get in touch. You will usually find a small set of reasons that covers most of the volume, plus a long tail of rare requests. Menu options should mirror the frequent reasons; the rare ones can go to a general option or straight to an agent.
For each reason, note who handles it and how urgent it is. Two different requests that end up in the same queue with the same agents do not need two separate keys. One fewer option is time saved for every caller.
List the reasons for calling
Write them in your customers’ words, not your internal team names.
Estimate how much each one matters
A rough estimate is enough to see which reasons deserve their own key.
Group them by destination
Merge reasons that go to the same people into a single option.
Decide the order
Put the most chosen options first, so most callers listen to less.
How to word IVR prompts: short sentences, action last
Menu prompts are heard once, so write them for the ear. Short sentences, everyday words, one idea per sentence. Avoid acronyms, team names customers have never heard of and long introductions before the options.
A useful rule is about word order: the reason first, then the key. “For technical support, press 2” works better than “Press 2 for technical support”, because the listener recognises their situation first and only then needs to remember a number. The other way round, they have to memorise every number before they know what it is for.
Keep the greeting short. Your company name and, if needed, one sentence about what callers can do; then go straight to the options. Promotions, privacy notices or company descriptions at the start of the menu make everyone wait longer, including people who call every week.
| Avoid | Better |
|---|---|
| “Welcome to Smith Ltd customer services, serving the industry since 1985…” | “Welcome to Smith Ltd.” |
| “Press 1 for the order desk” | “To check an order, press 1” |
| “For support, information, complaints, returns or anything else press 2” | “For a return or a complaint, press 2” |
| “Your call is important to us” before every choice | One greeting, then the options |
Handling errors, silence and retries: IVR fallbacks
Some callers will press the wrong key, or nothing at all. It happens to people calling from a mobile with the phone at their ear, people driving, people who did not catch the options. Good design decides in advance what happens in these cases instead of letting the call drop.
There are four things to design: how many seconds to wait for a key after the prompt ends, how many retries to allow, what to say after an invalid choice, and where to send callers who never choose. A wait that is too short cuts off people who are thinking; one that is too long leaves confused callers in silence. A few seconds, checked with real calls, is usually the right balance.
The invalid choice prompt should not just say “invalid option”. It is the moment to repeat the options briefly, because a caller who got it wrong probably does not remember them. And callers who press nothing should not be locked out: sending them to an agent or a general queue is far more useful.
- Key timeout: long enough to decide, short enough not to sound like a dead line.
- Retries: one or two extra attempts are usually enough.
- Invalid choice prompt: repeats the options, not just the error.
- No key pressed: goes to a useful destination instead of hanging up.
- Goodbye prompt: tells callers what to do next, such as calling back later or writing in.
Opening hours, holidays and out-of-hours prompts
A menu that offers “press 2 to speak to an adviser” at eleven at night wastes time and frustrates callers. Your menu should know when you are open and act accordingly: outside business hours, state the hours clearly and offer a real alternative.
The most useful alternatives are a message with your hours and website, a way to leave a number for a callback, or an automated assistant that answers common questions. For urgent matters, if your service offers it, an option that reaches the on-call person.
Do not forget public holidays, extra days off and summer closures: these are the days when a menu left in “open” mode produces the most unanswered calls. With time conditions you define your hours once and apply them to several menus; our guide to business hours and holidays shows how to organise them.
After the key press: queues, waiting and reaching an agent
The menu’s job ends when the call reaches its destination, but the caller’s experience does not. If a key leads to a queue, your design has to account for what happens next: the queue greeting, the hold music, position announcements and what happens when the wait gets long.
Avoid double greetings. If the menu has already welcomed the caller, the queue does not need to say “welcome to…” again. A short message before the transfer, such as “putting you through to technical support”, confirms the choice and reduces uncertainty.
For long waits, plan a way out: offer a callback, send the call to another queue or to an automated assistant. Our guide to call queue strategies explains how to share calls between agents, and the one on how to reduce missed calls covers the most effective overflow options.
Frequently asked questions
How many options should an IVR menu have?
As a practical guideline, three to five options per level and no more than two levels. Beyond that, callers struggle to remember the choices. If you have many requests, group them by destination or use an AI voice agent instead.
What should an IVR greeting say?
Your company name, followed straight away by the options, each with the reason before the key, such as “to check an order, press 1”. Leave out promotions and company descriptions: they make every caller wait longer.
What happens if a caller does not press any key?
It depends on how the menu is set up. A good design gives callers who press nothing a destination, such as an agent or a general queue, rather than ending the call after the retries.
Should I record IVR prompts or use text-to-speech?
A voice recorded by a person sounds more personal, but every change needs a new recording. Text-to-speech lets you change the wording in seconds and keeps the same voice across all your menus, which helps when hours and options change often.
How often should I review my IVR menu?
Whenever teams, services or hours change, and at regular intervals anyway, using your reports and asking agents which calls land in the wrong place. Remove temporary notices that no longer apply.