A caller reaches a business number and hears a list. Press 1 for sales. Press 2 for support. Press 3 and enter an order number. The menu sorts people by a key. It does not hear the sentence they actually wanted to say.
A voice agent answers in words. The caller says what they need. The agent follows a path the business already defined, or it passes the call to a person with what was said so far. Replacing the menu means retiring the keypad list for those paths. It does not mean every call ends without a person.
Key takeaways
An IVR menu sorts callers by a key. A voice agent sorts them by what they say.
Keep a spoken path only for requests the business has already written down, such as an order lookup, a sales question, or a booking from open times.
The caller should not have to repeat the story after a transfer. The person who picks up needs the transcript.
A keypad option can stay for a choice the agent is not allowed to make.
Share of calls handled alone, hold time, cost per call, and language counts are not results this article is reporting.
What the menu is doing
The menu is a tree. Each key opens the next list or a queue. It works when the request is one of a few known buckets and the caller is willing to listen. It fails when the request does not match a key, when the caller is already upset, or when they have to tell the whole story again after the transfer.
A useful menu has a small number of keys and a way to reach a person. A long menu hides that way. Replacing it starts by writing down which keys people actually use, and which calls always end in the queue anyway.
What the voice agent does instead
The agent speaks first with a short line that invites the request, not a list of keys. It listens, matches the request to a path, and either finishes that path or transfers.
Three paths cover most of a menu:
A known answer, such as hours, a document, or the next step in a process the business has approved.
A lookup, such as an order or an account, only when that lookup exists and the caller is allowed to hear the result.
A booking, only from times the business has opened. The agent offers those times. It does not invent a slot.
If none of those paths fit, the next step is a person. Guessing a policy on a live call is worse than the old menu, because the caller thinks the answer was real.
How one call moves
The caller reaches the number that used to play the menu.
The agent asks what they need, in one sentence.
The caller says it. They can interrupt and correct themselves. The agent keeps the correction.
The agent takes the matching path, asks the one detail that path needs, and states what it did.
If the path is blocked, the agent says it is transferring and sends the transcript with the call.
The caller should hear the outcome before the line drops. “I found the order and it is out for delivery” is an outcome. “Please hold” with no reason is the old queue.
A later text can carry a link that was agreed on the call, such as a tracking page or a payment page. Send that only when the call named it. Do not add a message the caller did not ask for.
How the old keys map to a spoken path
What the caller wants | Keypad menu | Voice agent | A person |
|---|---|---|---|
Sales question | Press 1, then wait | Answer from the approved product facts, or book a demo from open times | Takes pricing or terms the agent is not allowed to offer |
Support question | Press 2, then wait | Give the approved step, or look up a status if that lookup exists | Takes complaints and anything the steps do not cover |
Order status | Enter the number on the keypad | Ask for the order in words and read the status if the lookup exists | Takes a missing order or a status the lookup cannot show |
Appointment | Press 4, then an agent checks a calendar | Offer only the open times | Books anything outside those times |
“I want a person” | Often buried at the end of the menu | Transfer now, with the transcript | Continues the call |
What the call should record
Every finished call needs an outcome the team can filter.
Answered from an approved path.
Lookup completed, or lookup missing.
Time offered, and whether the caller accepted one.
Transferred, and why.
Caller hung up before the path finished.
That record shows which menu keys were real requests and which calls still need a person. A call with no outcome is a recording nobody will search.
Where a person steps in
The agent keeps the paths that used to be a key plus a wait. A person takes the call when:
The caller is unhappy, or the issue is a complaint.
The question needs a decision or account access the agent is not allowed to use.
The lookup fails, or the requested time is not open.
The caller asks for a human.
The transfer includes what was already said. The person continues the call. They do not ask the caller to press a key and start again.
What this is not
A voice agent on the business number does not, by itself, prove that most calls end without a person, that hold time is gone, or that the line costs less than a staffed queue. Those depend on how many requests are already written down, and on how often callers accept the answer. Treat the agent as a replacement for the keypad list, not as a measured resolution rate or a cost saving.
The same limit applies to how natural the voice sounds, how many languages it speaks, and how many calls it can take at once. Those are not outcomes this article is reporting. A clearer voice does not add an answer the business has not approved.
This article is also not the appointments, feedback, and collections call. Those are separate jobs with their own steps. Here the question is only what happens to the menu: which keys become a spoken path, and which calls still reach a person.
Explore Fonada
IVR replacement for swapping the keypad menu for a voice agent
Voice AI for the agent that speaks on the call
Telephony for the business number the menu used to sit on
Customer support for the calls a person still handles