Every caller who presses one, then two, then sits through hold music before hanging up is a booking, a claim or a repair job walking away quietly. Phone menus were built decades ago to save a business the cost of another operator, never to make a caller feel heard, and today callers vote with their thumbs: they hit zero, or they just hang up. What replaces that menu is already familiar to anyone who has used a smart speaker: a system that lets a caller simply say what they want.
Why the menu exists in the first place
The first interactive voice response system, IVR for short (a computer that plays a recorded menu and reads the numbers a caller presses), went live in the United States in 1973 to help a company check warehouse stock over the phone. Call centres adopted the idea through the 1980s once hard drives became cheap enough to store and play back digitised speech, because a machine that could sort callers into the right queue cost far less than hiring another operator. By the 1990s, "press one for..." had become the standard way hotels, banks, airlines and utilities greeted a caller, and the format has barely changed since, even though the phones on both ends of the line have grown far smarter.
Why callers hate it more than they hate hold music
A phone menu is built around departments, not around the problem sitting in the caller's head. Take Rashid, a composite example calling a dealership in Bausher about a service booking that also needs a tyre check and a question about his warranty. There is no button that covers all three, so he picks the closest one, gets transferred twice, and repeats his number plate to each new voice on the line.
- Say the one sentence that explains the real problem
- Skip the parts of the menu that do not apply to them
- Reach a person once, not after two or three transfers
- Avoid repeating the same details to every new voice
None of that fits neatly onto a tree of numbered options. Every extra key press adds a small tax of time and irritation, and by the second or third transfer, many callers have already decided to try a competitor, send a complaint by email, or simply give up.
A phone menu was built to save the business money on operators. It was never built to make a caller feel understood.
The real cost of press one, in Omani rial
Put real numbers on it and the size of the problem gets obvious fast. Take a composite case: a call desk for a polyclinic group in Muscat handling 300 calls a day during flu season, split across two branches with three staff answering the phones.
| What happens | With a press one menu | With a conversational line |
|---|---|---|
| Calls arriving in a day | 300 | 300 |
| Calls that reach a person within a minute | 210 (70%) | 270 (90%, composite estimate) |
| Calls abandoned inside the menu | 45 (15%) | 15 (5%, composite estimate) |
| Average value of a kept appointment | OMR 12 | OMR 12 |
| Revenue at risk from abandoned calls, one day | OMR 540 | OMR 180 |
Swap in a business's own call volume and its own average ticket, a service booking, a room rate, an insurance premium, and the same maths applies to a dealership, a hotel or an insurer. The formula stays the same: calls abandoned multiplied by what an answered call is worth.
What changes when the caller can just talk
The fix was never a smarter menu. It was letting the caller start with a sentence instead of a keypad. A conversational agent (voice software that understands normal speech and replies in kind) listens to something like "the air conditioning in room 214 has been leaking since this morning, can someone come up" and pulls out the room number, the problem and the urgency in one pass, with no numbered options at all.
That matters even more when the sentence lands in Omani Arabic, mixes in English mid-thought the way callers here actually talk, or trails off entirely before the point comes out. Phone lines built to handle exactly that kind of sentence, including CustomerCare.OM's Omani Arabic phone agents, are already turning what was said into notes an operations lead can read later, instead of a call that vanished into hold music.
The caller was never confused about what they needed. The menu was the one that could not listen.
What this means for you
Pull up a day of call recordings, or the IVR analytics dashboard most phone systems already have and rarely open. Count how many calls hang up before reaching a person, then multiply that by what one handled call is worth. If a business already runs a front desk, a service centre or a call desk with staff on the phones, that number is a real business case, not a hypothetical one.
There is no need to rip out the whole phone system overnight. Start with the calls that matter most: after hours, the peak season rush, or the callers who already press zero and refuse the menu outright. Route just those calls to a conversational line first, and measure the difference for a month before deciding on anything bigger.
Half our calls today are someone repeating their problem three times before a person ever hears it.
Should a business remove its phone menu completely?
Not necessarily. Keep a short menu for simple routing like billing or emergencies, and let a conversational option handle everything else.
Is this only useful for large call centres?
No. Any business with a shared phone line, three staff or thirty, can count abandoned calls and test a conversational option on its busiest hours first.
What about callers who prefer pressing numbers?
They can keep doing exactly that. A conversational line adds a way to speak. It does not remove the keypad for people who like it.
The bottom line
Phone menus solved a cost problem from the 1980s, not a caller's problem today. The business case is already sitting in a business's own call logs: count the hang ups, price them against what an answered call is worth, and start with the calls that matter most instead of overhauling everything at once.
Sources checked for this article
Practical information, not legal advice. Rules and dates were checked on 22 September 2026; verify current official positions before acting.
