A phone menu without the frustration: IVR design rules

Everyone has a story about an endless phone menu: press 1, press 2, and after three levels you're back at the start. An IVR (interactive voice response, or phone menu) doesn't have to work that way. A good menu saves callers time, routes them to the right agent, and handles simple tasks without a queue. Let's go over the rules and calculate what a good menu saves and what a bad one costs.

Start with why people call, not with your org chart

Menus often mirror the org chart: sales, billing, tech support. Callers don't think in departments – they think in terms of what they need done.

• Break down a month of calls by call reason – speech analytics can do this automatically.
• Put the three or four most common reasons at the top of the menu.
• Use the caller's words: "check where my order is," not "logistics department."
• Revisit the menu when products, seasons, or marketing campaigns change why people call. Review the per-option reports once a month.

Keep the menu short and shallow

• No more than four or five options per level – by the fifth, callers forget the first.
• No more than two levels before reaching an agent or a self-service action. More options and levels mean more confusion and wrong choices.
• Action first, then the number: "To check your order, press 1."
• A short greeting, with no ads or long legal disclaimers.
• Let callers press a key without waiting for the prompt to finish – regular callers know the menu by heart.

Why two levels of 4-5 options, and no more. One menu option takes 3-4 seconds to say: "To check your order, press 1." A greeting plus two levels of five options is about 45 seconds to the goal. Three levels of six options is already about 80 seconds – and that's if the caller never makes a mistake. People can hold only a few options in their head at once: by the sixth, they forget the first, pick at random, end up in the wrong place, and the time grows even more. Every extra second in the menu means callers who hang up before they ever reach an agent.

Speech recognition where it helps

Speech recognition and AI let callers simply say what they need. For many lines, that's faster than any keypad menu.

• Ask an open question: "Briefly tell me what you're calling about."
• Route the call by meaning, not exact words: "where's my package" and "my order didn't arrive" should go to the same place.
• Ask callers to repeat only when the system isn't sure, not after every answer.
• Keep a keypad option for noisy places and for people who prefer pressing keys.
• Accept order, account, or phone numbers by voice so callers don't have to key them in.

Self-service that finishes the job

Self-service is useful only if callers can resolve the whole issue. A flow that ends with "please hold for an agent" is worse than none at all.

• Good fits: order or service request status, account balance, business hours, appointment confirmation, simple payments.
• Connect the menu to your CRM and order system through the API so it gives real answers.
• Identify callers by phone number and don't ask for what you already know.
• If there's a lot of information, send the details after the call by SMS or a messaging app.
• For conversations more complex than picking from a list, use a voice AI agent instead of a rigid tree.

Someone who calls every week doesn't need the whole menu: recognize their number and offer their last action right away, or connect them to their assigned account manager. New callers benefit from a short note on what they can handle without an agent.

What a good menu saves and what a bad one costs

Let's run the numbers for a line with 20,000 calls a month. An agent hour costs $50, and calls take up 60% of an agent's time – breaks, training, and idle time take the rest. That puts a minute of talk time at roughly $1.40.

• Self-service. If the menu fully resolves 10% of calls – for example, by giving order status – that's 2,000 calls a month that never reach an agent. At 3 minutes per call, that saves about $8,300 a month and $100,000 a year – roughly the annual cost of one agent.
• Wrong choices. If 10% of calls land in the wrong queue and the transfer takes an extra minute, that's 2,000 minutes a month – about $2,800, or $33,000 a year, just because the menu is confusing.
• Abandoned in the menu. A caller who couldn't find a way out and hung up is the same as a missed call for sales. The missed call cost calculator shows what those losses cost.

Plug your own numbers into the AI agent savings calculator: enter the share of calls the menu will resolve and the handle time for those calls, and for a keypad menu, set the AI cost per inquiry to 0.

Always leave a path to an agent

Hiding the way out to an agent doesn't reduce calls. Callers who can't find it get angry and call back. And when the path to a person is visible, callers are more willing to try self-service.

• Say in the main menu how to reach an agent.
• Transfer to an agent after two failed attempts to recognize a response.
• Pass everything the caller already entered to the agent so they don't have to ask again.
• Announce the expected wait time, and offer a callback when the queue is long.
• Put callers whose self-service attempt failed at the front of the queue.

Don't forget after-hours calls. Instead of a curt "we're closed," give your business hours and offer self-service, a callback in the morning, or a conversation with a voice AI agent that handles the request. That way, after-hours calls don't go to waste.

Common mistakes

• Loops that send callers back to the main menu with no explanation.
• Long ads before the menu.
• Different menus for the same task on different phone numbers.

Prompts people understand

Even a well-structured menu fails if the prompts are hard to understand. Words and voice matter as much as structure.

• Short sentences and everyday words, without internal product names or abbreviations.
• One voice for all prompts. For changing data, use a natural-sounding synthesized voice. If the menu changes often, text-to-speech is easier than booking a voice actor.
• Dates, amounts, and numbers sound the way people say them: "twelve hundred dollars," not "one, two, zero, zero."
• During pauses, say what's happening: "Looking up your order."
• Before launch, test the prompts on colleagues who haven't seen the menu yet.

A simple test: call your own line from a cell phone in a noisy place and try to complete the three most common tasks. If it's hard for you, it's even harder for callers. Repeat the test after every change.

Where to start

1. Break down a month of calls by reason and find the three or four most common.
2. Call your line and time how many seconds it takes to reach the goal for each of those reasons.
3. Estimate what share of calls the menu could resolve without an agent and how much that would save at your cost per agent hour.
4. After making changes, track how many callers choose each option, where they abandon the menu, and how many calls go to an agent after self-service.
5. Listen to recordings of calls that left the menu at the same step.
6. Change one branch at a time and compare results week over week.

In CONTACT.WORK, the IVR, speech recognition, AI agents, and call routing to agents are all configured on one platform. The menu pulls customer data from your CRM, and per-option reports show where self-service works and where callers give up.