IVR Design: A Voice Menu That Does Not Lose the Caller

What an IVR is and how to design one: menu depth, option counts, prompt wording, out-of-hours flows and the route to a human.

An IVR is the caller’s first contact with you. That first contact either routes them correctly or exhausts their patience — and the difference usually comes down to three or four design decisions.

Five fundamental rules

  1. At most four or five options per menu. Human memory cannot hold more; by the sixth option the listener has forgotten the first.
  2. No more than two levels deep. Abandonment rises sharply at the third level.
  3. Say the topic before the key. “Press 1 for sales” works better as “For sales enquiries, press 1” — the listener hears the subject first and remembers the key after.
  4. Put the most-used option first. Menu order should be decided by volume data, not by your org chart.
  5. Offer a route to a human at every step. “Press 0 at any time to reach an agent” is the most important line in the whole IVR.

Writing the prompts

  • Keep them short. The greeting should not exceed ten seconds. “Thank you for calling; customer satisfaction is our…” tires a waiting caller.
  • Leave promotions to the hold music. A campaign announcement before the menu is the fastest way to raise abandonment.
  • Use one voice. Different recordings at different levels make the system feel disjointed.
  • Say the numbers clearly. Key numbers can be lost under background music.

The waiting experience

Three things reduce uncertainty for someone in a queue:

Queue position

“There are three callers ahead of you” makes the same wait far more bearable.

Estimated wait

The estimate must be realistic; being wrong costs more trust than the wait itself costs patience.

Callback option

“Hang up without losing your place and we will call you back.” It is the single feature that most reduces abandonment.

Out-of-hours flow

A phone ringing out of hours is like an unanswered message. The options:

  • A prompt that states your hours clearly (do not just say “we are closed” — say when you are open).
  • Voicemail that turns into a support ticket.
  • Routing to an on-call line for emergencies.
  • Redirecting to WhatsApp or web chat — “you can message us at any time”.

Connecting to the CRM

On its own an IVR is a routing tool; connected to the CRM it becomes intelligent:

  • If the calling number is recognised, the caller can be greeted by name.
  • A customer with an open ticket can be routed straight to the agent handling it.
  • The menu choice arrives on the agent’s screen as context — the caller does not repeat themselves.
  • An unanswered call can turn automatically into a callback task.

Measuring whether the IVR works

  • In-menu abandonment: how many hang up before choosing? Above 10% is a design problem.
  • Misrouting rate: what share of calls reaching an agent get transferred elsewhere?
  • Zero-out rate: a high rate means the menu is not understood.
  • Time spent in the menu: if the average passes 30 seconds, simplify.

Frequently asked questions

Does a small business need an IVR?

With a single line a simple greeting is enough. A menu earns its place when you need to route to more than one team.

Is voice recognition better than key presses?

When it works, yes — but a recognition error is more frustrating than a key menu. Starting with keys and deciding from data is safer.

How many people before one menu stops being enough?

It is decided by the variety of calls, not headcount. If 80% of calls are about one topic, you may not need a menu at all.

Next step: to see the IVR and CRM working together, request a demo.