Press One for Frustration: Auditing Your Phone Menu in Under a Minute

Most small UK firms build a phone menu once, tick it off the list, and never ring their own number again. That is a mistake. Your IVR — the recorded options that answer before a human — is often the first real conversation a caller has with your business. If it is clumsy, the caller does not think 'bad menu'. They think 'bad company'.

Why your phone menu needs a mystery shopper

You cannot judge a menu from the admin screen. You have to hear it as a customer does: slightly impatient, maybe on a mobile in a car park, maybe worried about a bill, maybe not sure which department they need. The good news is that you do not need a consultant or new hardware to find the problems. You need a stopwatch, a phone, and ten minutes of honesty.

The 60-second test (yes, actually time it)

Ring your main number from a mobile. Start a timer when the greeting begins. Try to reach the department a real caller would want — sales, support, bookings, whatever matters most. Count every key press. Note every moment of silence. Stop at 60 seconds.

If you have not reached a human or the right message by then, your menu is asking a lot of someone who may have rung you instead of a competitor. Do the test at 9am, lunchtime, and just before closing. Repeat once a month. Menus drift: holiday messages stay up, staff leave, option three becomes a dead end.

The usual suspects

The first mistake is too much choice. Seven options feel organised to the person who built them and exhausting to the person hearing them. Most small teams can survive with three: sales, support, and everything else.

The second is jargon. 'Accounts receivable' means something inside your firm. 'Billing' means something to a caller. Say the words your customers use, not the words on your internal org chart.

The third is hiding the human. If 'press 0' is buried, callers will press anything. Put 'press 0 at any time to speak to a person' near the top, and mean it.

Then there is the preamble. A long welcome message, a list of opening hours, a reminder to have an account number, and a request to listen carefully because options have changed — all before option one. Keep the housekeeping short. Callers will forgive a brief menu. They will not forgive being made to wait for one.

Other common problems: the menu does not match the website; the voice is too fast; the audio is muffled; an option loops back to the start; and nobody says when a message will be returned. Each one adds a small reason to hang up.

Accessibility is not a niche extra

A phone menu should work for someone with hearing loss, a cognitive impairment, a strong accent, or a noisy train carriage. That means clear speech at a sensible pace, one instruction at a time, and no reliance on 'press the hash key' unless you really must. It also means offering a route to a human early. Accessibility is part of decent customer service, not a specialist project.

A short checklist for reducing drop-offs

• Can a caller reach a human in one key press?
• Are there three main options or fewer?
• Does the greeting name the business clearly?
• Is the most common reason for calling option one?
• Does every option say what happens next?
• Is there a timescale for callbacks?
• Does the menu match your website and opening hours?
• Can you hear it clearly on a mobile outdoors?
• Is there an alternative for urgent or vulnerable callers?

Fixes that do not need new kit

Rewrite the script before you touch the technology. Reorder the options. Record a calmer, slower version. Add 'press 0' at every level. Put a real timescale on callbacks: 'by the next working day' beats 'as soon as possible'. Update the holiday message before you go on holiday. Then test it with someone who does not work for you.

The bottom line

A phone menu is not a maze and it is not a shield. It is a signpost. If your 60-second audit ends in confusion, fix the signpost before you spend a penny on new equipment.