
An IVR system: a phone menu callers don’t hang up on
An IVR system is the menu a caller hears before they reach anyone: “For a fault, press 1.” Done well, it gets the caller to the right colleague first time; done badly, it is the reason they hang up and call someone else. This is how to build a phone menu that helps callers faster instead of holding them up.
A phone menu is only useful if it gets a caller to the right person faster than a plain hunt group or a receptionist would.
Keep a few options per level, the busiest first, in the caller’s own words, and always leave a route to a person.
Measure where callers hang up and which option they get wrong; that is where the improvement is, not in re-recording the greeting.
What an IVR system does, and when you do not need one
IVR stands for interactive voice response: the caller chooses with their keypad or their voice, and the phone system routes the call. A simple version is called an auto attendant in many phone systems and in Teams. More elaborate versions also check opening hours, ask for an account number or answer a question themselves, such as the status of an order.
The question that comes first: do you need one at all? If one team takes every call, a menu only adds waiting time. A group that rings everyone who is free, or a receptionist who puts calls through, is faster and friendlier. A phone menu only pays for itself when there really are different people for different questions, or when you want something different to happen out of hours.
The structure: few options, busiest first
Most phone menus grow one department at a time, and that is how they sound. Start the other way round: from the reasons people call, in order of how often they come up. Take them from your call logs, or ask whoever answers to keep a tally for a week.
- No more than four options per level. Beyond that, callers have forgotten the first by the time they hear the last, and press something at random.
- The busiest reason first. Whoever calls most often then listens for the shortest time.
- No more than two levels. Every extra level is another place to pick the wrong option or give up.
- Always a route to a person. A fixed key for “something else” or “speak to someone” that works on every level. Callers who do not hear their question in the menu should not have to guess.
- Option first, then the number. “For a fault, press 1” beats “press 1 for a fault”: the caller hears first whether it is about them.
The prompts: short, and in the caller’s words
A phone menu fails on its wording more often than on its technology. Name the caller’s question, not your department: “an invoice or payment” means more to a customer than “accounts receivable”.
- Keep the greeting short. The organisation’s name and straight into the first option. No advertising, no pointer to the website the caller has just chosen not to use.
- Read it aloud to someone who does not know your organisation, and ask which key they would press for three ordinary questions.
- One voice, one tone. Recorded or text-to-speech, but not mixed; a menu that changes voice halfway sounds like a fault.
- No “our menu options have changed”. Callers do not know your old menu by heart; that sentence only costs time.
If you take calls in more than one language, the language choice is the first question. Put it before everything else and keep it short, or give each language its own number so the choice is not needed at all.
Opening hours, bank holidays and outage messages
Much of the annoyance happens out of hours: a menu that still says “press 2 for sales” at eight in the evening and then leaves the caller in an empty queue.
- Opening hours in the menu, not only in the group. Out of hours, the caller hears straight away what is possible: a callback request, an on-call number or a voicemail someone actually listens to the next morning.
- A bank holiday calendar that someone owns. Enter the dates a year ahead in the phone system and name an owner; otherwise Boxing Day runs as a working day.
- An outage message you can switch on quickly. During a major incident you want to play one sentence at the front of the menu without needing an engineer. Agree beforehand who may do that and how, for example through the phone system’s app or a fixed key code.
After the menu: queue position and callbacks
The menu is half of what the caller experiences; the queue behind it is the other half. Someone who picks the right option and then hears music for minutes remembers the wait, not the menu.
- Say how long it will take. A queue position or an estimated wait lets callers decide for themselves whether to hold.
- Offer a callback as soon as the wait builds up. The caller keeps their place and hangs up; you call back when someone is free.
- Set a limit. After an agreed time the call moves to a second group or to voicemail, instead of running on indefinitely.
- Do not repeat every thirty seconds that the call is important. Once is enough; after that it irritates more than the music.
How to set up queues, groups and callback options in a phone system is covered on our page about the cloud phone system.
Measuring your IVR system: where callers hang up
A phone menu is never finished. The phone system records what happens at each option, and that shows the improvements you would otherwise miss.
- Where do callers hang up? During the greeting, on the second level, or only in the queue. Each place needs a different fix.
- Which option is chosen most? If it is not first, make it first.
- How often are calls transferred? Lots of transfers between two groups means callers misunderstand the options. You fix that in the wording, not with the staff.
- How often do callers choose “speak to someone”? If that is the most popular key, the menu does not match the questions.
Also call it yourself, once a month and out of hours as well. Keep a log of which change you made when, so you can trace a shift in the figures back to what you did.
Speech recognition and AI in the phone menu
More and more phone systems let callers say what they want instead of pressing a key. That works well with a limited set of clear topics, and less well with strong accents, background noise or a question that fits nowhere.
- Keep the keypad as a fallback. Anyone who is not understood twice should still be able to choose, or reach a person.
- Do not let a bot keep the door shut. A voice assistant that does not understand the question and keeps the caller in a loop costs more than a three-option menu.
- A voice is personal data. Ask where the speech is processed, whether recordings are kept and whether the vendor uses them to improve its own models.
Think too of callers for whom a spoken menu is difficult, such as people with hearing loss. Another channel, such as chat or email, clearly signposted on your website, belongs with an accessible phone menu.
Where our work stops
We do not supply call minutes, line rental or phone numbers. Those stay with the carrier you choose. The phone system or contact centre platform the menu runs in belongs to a third party, with its own features and limits; we cannot make more of it than the product allows.
What we do: build and configure the menu in your phone system or in Teams, set up opening hours, bank holidays and outage messages, the queues and callback options behind it, the handsets and headsets, the network underneath and the support afterwards. The wording, and which questions go to which colleague, remain yours; we help think it through and put it in place.
Questions we get about this
The five that come up most often.
What is an IVR system?
IVR stands for interactive voice response: a phone menu in which callers use the keypad or their voice to choose where their call goes. The phone system then routes them to the right group, a voicemail or a callback request. More elaborate versions also check opening hours or give information themselves.
How many options should a phone menu have?
Keep to no more than four options per level and no more than two levels. With more, callers have forgotten the first option by the time they hear the last. Put the most common reason first and make sure every level has a route to a person.
What is the difference between an IVR and an auto attendant?
An auto attendant is the simple version: a greeting and a few options that put the call through to a group or a person. An IVR can do more, such as ask for an account number, look up information or recognise speech. For most organisations the simple version is enough.
Can we change the phone menu ourselves?
With most cloud phone systems you can, through an admin portal or app. Agree who is allowed to, so not everyone can change the menu, and keep a log of what you changed when. An outage message you can switch on and off yourself is the most useful thing to keep in your own hands.
Do you supply the numbers and the call minutes too?
No. Numbers, line rental and call minutes stay with the carrier you choose, and the phone system belongs to a third party. We set up the menu, the queues and the opening hours, supply the handsets and the network underneath, and support it afterwards.
Further reading
What a phone menu connects to.
Shall we call your phone menu once?
Send us the number and the list of reasons your customers call. We will ring your menu and tell you which options, prompts and hours we would change.
Practical IT knowledge in your inbox
New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.