Everyone has been trapped in a terrible phone menu. What is striking is how consistent the failures are — the same handful of mistakes, made by businesses of every size, almost always because the tree was built around the org chart instead of around why people ring.
1. Start with the calls, not the departments
The most common mistake is building the menu to mirror your internal structure. Callers do not know your structure and should not have to learn it.
Instead, pull a few weeks of calls and list the actual reasons people rang, most frequent first. That list — not your department list — is your menu. It usually turns out that three reasons account for most of the volume.
2. Three to five options, maximum
Working memory gives out around four items. Offer seven and callers stop listening at about the fourth, then press whatever they heard last or hit zero in frustration.
If you genuinely need more coverage, a second level under a broad first choice is far better than a long flat list.
3. Put the most common option first
People choose the first plausible option they hear. If sixty per cent of your calls are one thing, that must be option one — otherwise most of your callers sit through irrelevant options every single time.
4. Say the purpose before the number
“For sales, press one” works. “Press one for sales” works less well, because the caller hears the number before they know whether it applies and has to hold it in memory. Small change, measurably fewer wrong selections.
Read it aloudNearly every IVR problem is audible within thirty seconds of listening to the whole thing at normal speed without skipping. If you find yourself impatient, so is every caller.
5. Always provide a way to a human
A zero-out option to reception. Not advertised loudly if you would rather steer people to the right team, but present. A menu with no escape route converts frustration into abandoned calls and complaints that arrive by another channel anyway.
6. Make out-of-hours behaviour explicit
Nothing damages trust faster than a menu that offers “press one for sales” at 9pm, then rings out. Time conditions should change the greeting to say you are closed, when you reopen, and what to do meanwhile.
Bank holidays need the same treatment on a separate schedule — otherwise the correct behaviour depends on someone remembering to change it, and eventually nobody does.
7. Decide what happens when nobody answers
The queue full, everyone on a call, nobody at their desk: this is the state most IVRs handle worst, because it gets designed last if at all.
Define it explicitly. Overflow to another team, divert to an on-call mobile, or offer a callback. Any of those beats ringing indefinitely into a queue with no agents.
Test it properly before go-live
Call every branch of the tree yourself, including the ones you think nobody uses. Then have somebody who did not design it try to reach three specific outcomes. If they hesitate, the menu is unclear — and they are being far more patient than a real caller.
We design call flows around your real call reasons, then test every branch.
See our IVR service
