AI voice agent vs. IVR: why the press-1 menu is on its way out
"Press 1 for sales, press 2 for support." Everyone has stood in that queue, phone on speaker, waiting for the option that describes their problem and not finding it. That menu is an IVR, short for interactive voice response, and for decades it was the only way to sort calls without a person. A voice agent sorts them differently: it asks what you need and listens to the answer. This post explains both, says honestly where the old menu still wins, and gives you a rule for choosing.
What a phone menu really is
A phone menu is a tree. Someone drew it once: sales on branch one, support on branch two, "all other enquiries" on branch nine. The caller walks the tree by pressing keys, and every caller walks it alone. The menu does not know why you called and cannot find out. It can only offer the branches it was given.
This has a hidden cost that never shows up on an invoice: the sorting work is done by the caller. They have to translate "my invoice is wrong and my delivery has not arrived either" into a single digit. When the tree does not fit, they press 0, or hang up, or pick a wrong branch and get transferred twice.
What a voice agent does instead
A voice agent turns the tree the other way round. The caller says what they want in their own words, and the agent does the sorting. It can ask a follow-up question, take two requests in one call, and answer the simple ones itself instead of routing them. "Are you open on Saturday?" gets an answer, not a department.
The branches still exist, but they are for the agent, not the caller. In NordTell you draw them on a canvas as a flow: collect these fields, call this tool, hand over here. The caller only ever hears a conversation. When a person is needed, the agent can do a warm transfer, which means it briefs the colleague before connecting, so nobody repeats themselves. That is a bigger difference than it sounds, and we wrote it up in How a warm transfer works.
Where the menu still wins
It would be dishonest to pretend the old menu has no strengths. It has several, and you should weigh them.
- It is predictable. The same key always goes to the same place, and nothing is ever misheard.
- It is cheap per call and costs nothing per minute of waiting.
- It works in a noisy van, on a bad line, and for callers who would rather press than talk.
- It is easy to audit. A regulator or a lawyer can read the whole tree on one page.
- If you only need to split calls between two or three clearly named teams, a menu does that job well.
Where the voice agent wins
The agent wins whenever the caller's request does not fit a digit. That covers a lot: a question that needs an answer rather than a department, a booking that needs a calendar, a message that needs a name and a number, a caller who speaks a different language from the menu. It also wins after hours, when there is no department to route to and a menu can only offer voicemail.
It wins on the caller's time. Every branch of a menu is time the caller spends listening to options that are not theirs. The agent asks one question and moves on. And it wins on what you learn: every call ends with a transcript, a summary and an outcome, so you can see what people actually ask for instead of which digit they pressed.
It has honest weaknesses too. It can mishear, especially unusual names. It needs instructions written by you, and it will follow them literally. It costs per minute of talk rather than per call. And it must be set up to say it is an AI and to keep a way to a person, or callers will rightly distrust it.
A rule for choosing, and a way to move gradually
Pull the numbers from your phone system before you decide. Count how many callers press 0, hang up inside the menu, or reach the wrong team and get transferred. If that share is small and your teams are clearly named, keep the menu. If it is large, or if most calls are questions rather than routing, the caller is telling you the tree does not fit.
You do not have to switch in one day. Put the agent in front and keep the old departments as its transfer targets. Give it your opening hours, your FAQ and your price list. Test it in the browser with a microphone until it handles the ten most common calls cleanly. Then move one number across, read the summaries for a fortnight, and move the rest. Here is a testing routine.
Where NordTell fits
NordTell is a way to build the agent side of this comparison: instructions in plain words, flows drawn on a canvas, warm and cold transfers to the teams you already have, and thirteen languages with safety nets. It always says it is an AI and always keeps a way to a person. The servers are in the EU and the company is in Copenhagen.