Skip to content
Implementation

The phone menu is going. Here is how to retire it without losing anything.

A phone menu that has been running for a few years is more than nine options. It is queues, time rules and recorded messages nobody remembers writing. Eight steps for replacing it with a voice agent – without any of that quietly disappearing.

A grey-haired man in a navy wool coat sits alone in a grey armchair in a bright hotel lobby, holding his phone in front of his face as he listens, a travel bag at his feet, low afternoon sun from the windows on the left and a receptionist out of focus behind a light wooden desk in the background

“Press 1 for sales, 2 for service, 3 for billing.” Most businesses considering a voice agent have a menu like that today, and most would happily get rid of it. There is good reason to: the menu makes customers sort their own problem into categories someone else invented, and anyone who cannot find theirs presses zero and hopes.

But a phone menu that has been running for a few years is rarely just a menu. It is a collection of rules that grew up one at a time: a separate queue for business customers, a night-time message, an option that only exists during the summer shutdown, a forward to a mobile someone set up long ago. None of them is written down anywhere else. Replace the menu without finding them first and they disappear quietly – and you notice only when your customers do.

Here are eight steps for making the switch without losing anything on the way.

1. Write down what the menu actually does

Do not start with the agent. Start by calling your own number and pressing through every single option – during the day, after closing and at the weekend. For each option, note where the call ends up, what happens if nobody answers, and what the caller hears while they wait.

Then get the configuration from your telephony provider or switchboard. That is where the menu keeps what callers never hear: time-of-day routing, priority between queues, overflow to another number when a queue is full. You will often also find options that still work but that nobody staffs any more.

2. Find out what people actually press

Most telephony systems can show how many callers choose each key, how many press zero or nothing, and how many hang up while the menu is still playing. Pull the numbers for the last few months.

Two things usually stand out. One is that a couple of options carry most of the traffic. The other is that “other” or zero is often among the largest. Those are the calls the menu could not sort – and they are exactly the calls a voice agent is best at, because it can ask what the call is about instead of asking the caller to choose.

These numbers are also the baseline you will measure against later. Keep them.

3. Turn keys into call types

The temptation is to have the agent read the menu aloud: “Is this about sales, service or billing?” Then you have built a voice-controlled phone menu, with the same categories and a new way to get it wrong.

Instead, turn each option into a call type and decide what the agent should do with it. A simple table is enough:

Key today What customers actually call about What the agent does
1 – Sales Prices, quotes, “do you have…?” Answers from the knowledge base, transfers when the customer wants to order
2 – Service Faults, complaints, status of a case Takes the case with what the technician needs, transfers if it is urgent
3 – Billing Due dates, payment extensions, wrong amounts Answers general questions, passes specific cases on
0 or nothing Everything else Asks what the call is about, and routes it

The middle column is the one that matters. Fill it in with the people who answer the phone today, not from the menu prompts.

4. Write the opening as a question, not a list

Once the categories are no longer read out, the agent needs an opening that lets callers state their business in their own words: who they have reached, that an AI is answering, and one open question. How to write that sentence is covered in Everyone hears the first sentence. Here is how to write it.

Customers who have called you for years will still press 2 out of habit. Decide what should happen then. If your setup supports keypresses, the agent can accept them for a transition period. If not, it should say that it no longer uses the keys and ask what the call is about. Either works. What does not work is nothing happening.

Want to talk it through with someone who has done this before?

Fifteen minutes on a call. We will tell you honestly whether a threll fits your setup – and what has to be settled before it goes live.

15 minutes · no obligation · pick your own time

5. Keep every destination the menu sent callers to

Every key in the old menu ended somewhere: a queue, a team, an on-call phone. All of them need to exist as possible transfers for the agent, with the same time rules. Otherwise the business customer who used to land straight in their own queue now ends up alongside everyone else.

For each transfer you need three answers: when it applies, what happens when nobody picks up, and what the person at the other end is told before they answer. That last one is among the biggest gains from the switch. A menu can only report that the caller pressed 2. An agent can say what the call is about. More on the handover in Designing the escalation from voice agent to human.

6. Move the messages into what the agent knows

Many menus play recorded messages before the options: “We are currently experiencing long waiting times”, “For power outages, please see our website”, “The office is closed between Christmas and New Year”. They are often the most important thing a caller hears, and they are easy to lose in a switch because they do not sit under any key.

Go through every active and scheduled message and decide, for each one, whether the agent should say it to everyone, only to the callers it concerns, or not at all. A service notice that affects one area works better as an answer than as an introduction everyone has to sit through. Decide, too, who adds the next message, now that it is no longer a recording.

7. Start with zero, not with everything

The safest first step is not to switch off the menu. It is to let the agent take the option that is already a leftover category: zero, “other” or no key at all. Customers who know what they want keep the route they know, while the agent gets the calls the menu could not sort anyway.

Read the calls in the first week. If the agent routes correctly and transfers land where they should, move the next option over. One option at a time lets you see what goes wrong before it goes wrong for everyone.

8. Measure against the baseline – and clean up after yourself

Compare with the numbers from step 2: how many callers hang up before getting help, how many are transferred more than once, and how many call back about the same thing. The last one tells you the most, and it is the same number that settles whether customers really wanted a human – see Customers don't hate the bot. They hate calling twice. The share of calls the agent “handled” tells you the least, for reasons set out in The numbers that flatter your voice agent.

When the last key is gone, there is a clean-up job nobody thinks of: web pages, invoices, email signatures and customer letters that still say “press 3 for billing”. Find them before your customers do.

The menu was a promise to your customers

A phone menu is clumsy, but it is predictable, and that predictability is something customers have got used to. That is not what you are getting rid of. What you are getting rid of is the customer having to do the sorting.

Make the switch one option at a time, with the rules written down first, and customers get a phone line that asks what they need – and you lose nothing the old menu knew.

Threll.ai answers on the number you already have, asks what the call is about and transfers to the right person.