The phone menu was a good answer to a real problem: too many calls, too few people, and no way to know what a caller wanted before picking up. It solved the routing problem by making the caller do the routing. That trade has aged badly.
The compounding drop
Menus are rarely one level deep. A caller picks a language, then a department, then a sub-option, and each of those is a chance to hang up, mis-press or wait through options that do not apply. The loss at each level is small. The loss across three levels is not.
- Level one, language selection: a few percent leave, usually the ones who do not hear their language listed.
- Level two, department: the largest drop, because this is where callers have to translate their problem into your org chart.
- Level three, sub-option: smaller, but the callers still on the line have now spent close to a minute and have not spoken to anyone.
Callers do not know your departments
A menu asks the caller to classify their own problem using categories they have never seen. Someone calling about a debit made from their account does not know whether that is cards, disputes or general banking. They guess. Roughly a fifth of the time they guess wrong.
“Our agents now spend their time on the hard cases instead of repeating the same five answers.”
Ask instead of listing
The alternative is not a shorter menu, it is no menu. A voice agent picks up and asks an open question. The caller describes the problem in their own words, in whichever language they reached for first, and the agent works out both the intent and the language from that one sentence.
Routing still happens, it just happens on the system's side of the call. If the request is routine the agent resolves it there and then. If it needs a person, it goes to the right person with the context already attached, which is a better transfer than any menu produces.
| Press-one menu | Open intent capture | |
|---|---|---|
| Time before first useful moment | 45 to 90 seconds | Under 5 seconds |
| Language handling | Fixed list, chosen upfront | Detected from speech, switchable mid-call |
| Misroute rate | High, caller classifies | Low, system classifies |
| Context on transfer | Menu path only | Full transcript and intent |
Where menus still earn their place
Two cases hold up. Regulatory disclosures that must be read before a conversation continues, and hard security gates where a caller has to authenticate before anything else happens. Both are short, both are unavoidable, and neither is really a routing menu.
Replace the menu, keep the routing
We will map your current tree against what callers actually ask for and show you what drops out.
Talk to usWritten by
Lucy Product
Product
