IVR and phone menus

10 Common IVR Mistakes and How to Fix Them in Your Phone Menu

Ten problems that make callers hang up on phone menus, from long greetings to dead ends, with a practical fix for each and a checklist for a quick self-audit.

Call editorial team · Published · 5 min read

Phone menus seldom fail because of technology. They fail because of choices made once, never revisited, and never heard by the person who made them. If you call your own number tomorrow and listen as a stranger, you will probably find at least three of the problems below.

A person frowning at a desk phone while reading a list of menu options
Illustrative image

This list is ordered roughly from the most to the least damaging. For the design principles behind the fixes, see IVR Menu Design and What Is IVR?.

The ten at a glance

Ten mistakes, one line each

  • 1. Too many optionsMore than about five choices is hard to remember.
  • 2. A long greetingCallers hear a speech before they can act.
  • 3. Internal jargonDepartment names mean nothing to outsiders.
  • 4. No way to a personCallers feel trapped.
  • 5. Dead ends and loopsThe menu repeats or ends without help.
  • 6. Stale informationOpening hours and options out of date.

Mistakes 1 to 5: the design

1. Too many options

Callers cannot hold a long list in their heads. By the sixth option they have forgotten the first. Cut the menu to the few reasons that account for most calls, and move everything else to a general option or a person. If you truly need more choices, split them across two levels, but think twice: each level adds delay.

2. A long greeting

A paragraph of welcome, legal notices and promotions before the first option teaches callers to ignore the whole thing. Say who you are in one sentence, then give the choices. Put necessary notices where they apply, not all at the front.

3. Internal jargon

"Press 2 for Tier 2 Fulfilment" means something only inside your company. Use the words customers use: "For a delivery," "To change a booking." Ask a few customers what they would call each option.

4. No way to a person

Hiding the human route makes people press random keys. Mention it early and keep it on the same key at every level. Letting Callers Reach a Person Quickly covers this in depth.

5. Dead ends and loops

A dead end is a branch that finishes with no next step. A loop is a menu that returns to the start whenever the caller does something unexpected. Both are fixed the same way: map each branch to the end, and make sure every path ends in an answer, a person, a voicemail or a callback.

Dead end versus finished branch

Dead endFinished branch
Wrong key pressedMenu restarts silently"Sorry, that was not an option" then repeats the choices once
No agent freeRings foreverOffers to wait, leave a message or request a callback
Branch gives informationPlays it and hangs upPlays it, then offers to repeat or reach a person

Mistakes 6 to 10: the upkeep

6. Stale information

Old opening hours, a department that was renamed, a recorded promotion that ended. Give someone the job of reviewing the recordings each quarter, and after any change in your business. See Routing Calls by Business Hours, Holidays and Closures.

7. Poor audio and pacing

Distorted recordings, background noise, rushed speech, or no pause between options all hurt comprehension. Record in a quiet room, leave a beat after each choice, and slow down. If you are weighing recorded voices against synthetic ones, read Creating IVR Prompts: Recording vs Text-to-Speech.

8. Ignoring after-hours callers

Many callers ring when you are closed. Give them your hours and something to do: voicemail, a callback request, or a pointer to your website.

9. Never testing or measuring

A menu that has never been called by a stranger and never reported on is guesswork. Test on a phone, not on a screen, and look at the numbers at least monthly, as described in Analyzing and Improving Your IVR.

10. Forgetting accessibility and language

Some callers are hard of hearing, in a noisy place, or speak another language. Give enough time to respond, repeat options on request, and consider offering a language choice early if your callers need it. Callers who cannot use a keypad should have another route, such as speaking to a person.

Why these mistakes survive for years

Almost nobody sets out to build a confusing menu. The problems creep in for understandable reasons, and knowing them helps you prevent a repeat.

A simple remedy is to give one person ownership of the whole caller journey and a standing monthly slot to review it. Imagine a small repair business that adds an option every time it launches a service. By the time it has seven options, a review would show that two of them receive almost no calls and that a third is the most common reason for pressing the key for a person. Merging the quiet options and promoting the common one costs an afternoon, and callers notice the difference immediately.

A quick self-audit

Audit your own line in fifteen minutes

  1. Call as a strangerUse a phone, in a normal place, without looking at your notes.
  2. Time itNote how long until you could reach a person.
  3. Try the wrong thingsPress an invalid key, say nothing, ask for a person.
  4. Call after hoursCheck the closed message and options.
  5. List what confused youFix the top three first.

Menu health checklist

  • Five or fewer options per menu
  • Greeting under about ten seconds
  • Customer words, not internal names
  • A route to a person at every level
  • Every branch ends with help
  • Hours and options verified this quarter
  • Audio clear, paced and tested
  • After-hours path tested
  • A monthly review is in someone's diary

Fixing it without breaking it

Resist the urge to rebuild everything. Change the worst problem first, test it, then move on. If you change many things in one go, you cannot tell which fix mattered. Record what you changed and when, so you can compare call patterns before and after. Share the change with your agents too, because they will hear first whether callers arrive less confused or more.

One last point: do not wait for a full rebuild to start. Fixing a single dead end or rewording one confusing option can improve the experience this week.

Doing it in Call

In Call, a phone line is answered by an AI agent you configure, and hours, queue closed messages, voicemail and callbacks are set in the phone line and queue settings. Practical fixes from this list that Call supports include setting business hours for a line, writing a closed greeting for a queue, choosing who is put through when a caller asks for a person, and letting a closed queue take a message. The routing simulator lets you see where a call would go without dialling, and practice calls let you hear your own flow. See Setting Up IVR and Business Hours in Call to get started.

Frequently asked questions

How many options should a phone menu have?

Aim for about five or fewer at each level. If you need more, ask whether some belong under a general option or a person.

How long should the greeting be?

As short as you can make it: who you are, then the choices. Put notices where they are relevant instead of in front of everything.

Is it a problem if callers press 0 a lot?

Not necessarily. It tells you what the menu does not cover. Look at where they press it and add or reword an option there.

How often should I check my menu?

Test it as a stranger at least once a quarter and after any change to hours, services or staff.

Should I record the prompts myself?

You can. The audio must be clear and the pacing slow. A synthetic voice is also an option; see the guide on recording versus text-to-speech.

What is the first thing to fix?

Whatever stops callers reaching help: a missing route to a person, a dead end or an out-of-date message.

Review your phone menu and routing rules in Call

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

Related guides