AI IVR: How to Replace Your Phone Menu With a Voice Agent

An AI IVR replaces "press 1 for sales, press 2 for billing" with a voice agent that asks callers what they need, answers what it can on the spot and transfers the rest to the right person based on what they said. On echowin you build it as one agent: your instructions describe who handles what, the Transfer Call tool holds the phone numbers, and your knowledge base answers the questions that used to need their own menu option. As of November 2026 it's free to build, minutes cost $0.20 while the agent is talking and half that once a call is transferred, and each live number is $10 a month (current prices).

We rewrote this page in November 2026. The 2024 version compared conversational AI and IVR in general terms. This one shows the rebuild: how to turn a real phone menu into an agent, what happens when nobody picks up, and what it costs, checked against how echowin handles transfers today.

Conversational AI vs IVR: what actually changes?

A menu IVR is a decision tree. The caller listens to options, presses a key, and the system forwards the call. An AI IVR is a conversation with the same goal, plus the option to finish the job without a transfer.

	Menu IVR	AI IVR (voice agent)
How the caller says what they want	Listens to a list, presses a key or says a set word	Says it in their own words, in one sentence
Routing	Fixed tree you set up once	Your instructions, matched to what the caller actually said
Simple questions (hours, address, prices)	Recorded message, or a transfer	Answered from your knowledge base
Actions	None, it only forwards	Book an appointment, text a link, look something up in your system
After hours	A different recording	The agent knows the time and follows your after-hours rules
Changing it	Re-record prompts, rebuild the tree	Edit the instructions and save
Cost per call	Usually part of your phone plan	Per minute (see below)

The difference that matters for an operator: a menu can only send the call somewhere. An agent can resolve the easy calls itself, so the transfers that remain are the ones that need a person.

Is an AI IVR the same as a conversational IVR?

The names overlap. "Conversational IVR" usually means a menu that accepts speech instead of key presses: you say "billing" instead of pressing 2, and the call still goes down the same tree. "AI IVR" has come to mean a voice agent that understands a full sentence and can act on it. When you compare products, ask one question: can it only route, or can it also answer and do things during the call? Everything in this guide assumes the second.

If you're new to voice agents in general, start with what an AI voice agent is and how it works.

How do I replace my phone menu with an AI agent?

Here's the rebuild on echowin, using a typical service business menu as the example.

1. Write down the menu you have

List every option, who it reaches today and what callers usually want when they pick it. Your call logs or a week of listening will tell you more than the menu script does.

Option today	Reaches	What callers usually want
1. Appointments	Front desk	Book, change or cancel a visit
2. Status	Service team	"Is my order or job ready?"
3. Billing	Office manager	A question about an invoice
4. Hours and directions	Recording	Hours, address, parking
0. Operator	Front desk	Everything else

2. Decide what the agent answers, does or transfers

For each row, pick one of three outcomes.

Caller wants	New handling
Hours, address, parking, prices	The agent answers from the knowledge base. No transfer.
A new appointment	The agent books it with a calendar tool (Google Calendar, Outlook, Square or Wix).
To change or cancel an appointment	Transfer to the front desk. Calendar tools book new appointments but can't cancel or reschedule existing ones.
Order or job status	Look it up in your system with a webhook tool, or transfer to the service team if you don't have an API to check.
A billing question	Transfer to the office manager.
Anything unclear	Ask one clarifying question, then transfer to the front desk.

This step is where most of the value is. Every "answer" or "book" row is a call your team no longer picks up.

3. Add the Transfer Call tool

Open your agent, go to the Instructions tab, and in the Tools panel click Add Tool and pick Transfer Call. Add one target per destination. Each target has:

• Name: what the agent uses to pick the target, such as "Front Desk", "Service Team" or "Billing". Make names distinct and say what they cover.
• Phone Number: a US, Canadian or UK number.
• Ext. (optional): an extension the agent dials after the call is answered, for desks behind your own phone system.

There's also a Safe Transfer switch. With it off, the person you transfer to sees the caller's number. With it on, the call is routed through your agent's number, so they see your echowin number instead, which can make transfers more reliable with some carriers.

Put your catch-all destination (usually the front desk) first in the list. If the agent ever asks for a target name that doesn't match one you set up, the call goes to the first target.

The Call Transfer docs cover each field.

4. Write the routing rules in plain English

The agent decides where a call goes from your instructions, so write them the way you'd brief a new hire on the phones. For example:

You answer calls for Riverside Service Co.

Answer questions about hours, location, parking and prices from the knowledge base.
Do not transfer for those.

Book new appointments with the scheduling tool. If the caller wants to change
or cancel an existing appointment, transfer to Front Desk.

Transfer billing and invoice questions to Billing.
Transfer "is my job ready?" questions to Service Team.

Before any transfer, tell the caller who you're connecting them to.
If you're not sure what the caller needs, ask one short question.
If you're still not sure, transfer to Front Desk.

If the caller presses 1, book an appointment. If they press 3, transfer to Billing.
If they press 0, transfer to Front Desk.

Magic Instructions on the same tab can draft a first version from a sentence or two, which you then edit. Our call routing guide has more examples of routing rules.

5. Keep keypad presses for callers who want them

Some callers will press 0 out of habit. On the agent's Settings tab, Allow keypad input (DTMF) is on by default: it sends key presses to the agent so it can react to them. The last lines of the instructions above tell it what each key means. Turn it off if key presses during a call should be ignored.

6. Set your hours and the after-hours rule

The agent knows the current date and time in the Time Zone set on its Settings tab, and it checks your stated hours against it. Put your hours and holiday closures in the instructions, then say what happens outside them:

We're open Monday to Friday, 8am to 6pm, and Saturday 9am to 1pm.
Outside those hours, don't transfer. Answer what you can, book appointments,
and for anything else take the caller's name, number and reason for calling.

Then add a post-call workflow on the agent's Workflows tab that emails or texts the summary to whoever opens up in the morning, or sends it by webhook to your own tools. Our guide to sending every call to n8n shows that end to end.

7. Put it on your number

Buy a number under Configuration, then Numbers, and connect it on the agent's Deployment tab by clicking the Phone card. If you want to keep the number your customers already dial, forward calls from your existing number to the echowin one.

8. Test every path

Call it yourself and try each row from step 2, including a vague request, a key press and a call after hours. Every call shows up under Manage, then Conversations, with the transcript, the summary and the tools the agent used, including which target it transferred to. Fix the instructions where it guessed wrong and call again.

What happens when nobody picks up?

This is where a rebuilt menu most often goes wrong, so it's worth knowing exactly what happens.

When the agent transfers, it tells the caller who it's connecting them to, then rings the target for up to 45 seconds. If the target doesn't answer, the agent comes back on the line, tells the caller the transfer didn't go through because the line may be busy, and offers to help with anything else. It doesn't try again unless the caller asks.

So give it something useful to do next. Add a rule like this to your instructions:

If a transfer doesn't go through, take the caller's name, number and reason
for calling, tell them someone will call back, and text them a confirmation.

The Send Text Message To Caller tool sends that text during the call, and the post-call workflow from step 6 gets the message to your team. The workflow still runs after transferred calls too, so you get a summary of every call either way.

What does an AI IVR cost?

As of November 2026, on echowin's pay-as-you-go pricing:

Item	Price
Building and configuring the agent	Free
Phone number	$10 a month per live number
Minutes while the agent is on the call	$0.20 a minute
Minutes after the call is transferred to a person	$0.10 a minute (half rate)

Two details from how calls are billed: the agent's part and the transferred part are each rounded up to the next minute, and the ringing while a transfer connects counts as agent time. Premium voices add $0.08 a minute, and discounted monthly bundles for inbound calls are on the pricing page.

A worked example. A caller talks to the agent for 40 seconds, the transfer rings for 15 seconds, and they spend 3 minutes 20 seconds with your billing person. That's 1 agent minute ($0.20) plus 4 transferred minutes ($0.40), so $0.60 for the call.

For a month: if 600 of 1,000 calls are handled by the agent alone in about 2 minutes each ($0.40 per call) and 400 are transferred like the example above, the total is $240 + $240 + $10 for the number, or $490. Your own mix of answered and transferred calls is what moves that number, which is why step 2 matters.

When is a menu IVR still the better choice?

Be honest about the fit before you rebuild.

An AI IVR fits when:

• Callers often pick the wrong option, or press 0 to get past the menu.
• A good share of calls are questions or bookings that don't need a person.
• You want to own the routing rules and change them yourself, and wire calls into the tools you already use.

A menu may be enough, or better, when:

• Nearly every call needs a person and there are only two or three destinations that callers already know.
• Callers have to enter card numbers or account PINs on the keypad into a payment or banking system. Keep those steps in a system built for them.
• You run a contact center with queues, hold music and routing by agent availability. That's your contact center platform's job. An agent can sit in front of it, answer what it can and transfer into it, extensions included.

FAQ

Can the agent transfer to another AI agent instead of a person?

Yes. The Switch Agent tool hands the conversation to another echowin agent you've built, for example a dedicated booking agent or one set up for a second location.

Does the person who answers see who's calling?

By default they see the caller's number. Turn on Safe Transfer in the Transfer Call tool and they see your echowin number instead.

What about "press 2 for Spanish"?

Callers can just ask for Spanish, and the agent switches and stays in it. echowin supports more than 70 languages. If a line should only ever speak one language, you can set that on the agent's Settings tab.

How long does the rebuild take?

For a menu like the example above, most of the time goes into step 2, deciding what the agent should answer and who gets the rest. The setup itself is the tool, the instructions and a round of test calls.

Build your phone menu as an agent, free: start at echo.win.