Short answer: callers do not object to menus. They object to being made to wait through information they did not ask for, being unable to reach a person, and being asked to classify their problem using words the company invented. All three are fixable in an afternoon.
A menu that answers the call instantly and routes correctly is genuinely better than ringing a desk nobody is at. The reputation problem comes from a short list of specific, common mistakes.
1. The Preamble
"Thank you for calling. Your call is very important to us. Please listen carefully as our menu options have recently changed."
Three sentences, none of which help. "Options have recently changed" is particularly counter- productive: for the 95% of callers who never memorised the old menu, it is noise, and for the 5% who did, it tells them to pay attention to something they will now have to re-learn.
Fix: name yourself in a few words and go straight to the first option.
2. Hiding the Zero
Some businesses deliberately remove or hide the option to reach a person, hoping to push self-service.
What happens instead: callers press 0 anyway, discover it does nothing, press it repeatedly, hang up and call back. You did not deflect the contact — you made the same contact more expensive and angrier.
Fix: offer 0 explicitly. Callers who can reach a person often choose not to, once they know they could.
3. Internal Vocabulary
"For post-sales service escalation, press 3."
Nobody outside your company has ever described their problem as post-sales service escalation. They would say "the thing I bought is broken".
Fix: name options the way a customer would describe the problem. Test by reading the menu to someone who does not work with you and asking what each option means.
4. Depth
Every nesting level loses people. One level is fine. Two is where callers give up and press 0. If your menu needs three, the phone is the wrong channel for that task.
Fix: group aggressively and keep it one level deep. See IVR menu design.
5. Silence After a Keypress
The caller presses 2 and hears nothing for several seconds. They assume the call dropped, hang up and redial — which appears in your stats as two calls, one abandon, and no clue why.
Fix: confirm every selection. "Connecting you to support."
6. Ringing Out at the End
The menu works perfectly, routes the caller correctly, and then rings a desk where nobody is sitting. From the caller's side the whole system failed.
Fix: every path needs a terminal state that is not silence — a queue, a person, or voicemail. Out of hours, say so and capture a message. See after-hours handling.
7. An Outage With No Message
When something is genuinely broken, call volume spikes and every caller is asking the same question. Making them navigate a menu to reach an agent who says "yes, it's down" wastes both sides' time.
Fix: put the status at the front of the flow during an incident. See service status and outage updates. A menu you can update in minutes is worth a great deal on a bad day.
8. Never Looking at the Data
The most common problem is not a design flaw. It is that the menu was set up once, years ago, and nobody has listened to it since. The business changed; the menu did not.
Fix: read the call logs quarterly. Which option takes the traffic? Which takes none? How many press 0 immediately? Each answer is a specific change.
The Honest Test
Call your own main number from a mobile, as a customer would, without warning your team.
Time how long until you could press the first key. Count the options. Try pressing nothing, and then something invalid. Try to reach a human. If any of that annoys you — and it usually does — it is annoying every caller you have.