“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.





