Call2MeStart free
All posts
IVR

IVR replacement with AI: a step-by-step migration guide

How to replace an IVR phone menu with an AI voice agent without breaking your phone line: three migration patterns, an intent map, SIP setup, a pilot plan and rollback.

CTCall2Me Team
November 17, 202610 min read
An old switchboard patch cable, a symbol of rewiring an IVR phone menu to an AI voice agent

Most IVR menus were built years ago, by someone who has since moved on, for a business that has changed. Callers press zero to escape them. Your team answers calls that the menu sent to the wrong place.

Replacing the menu with an AI voice agent fixes the caller side quickly. The risk is in the migration: phone lines are infrastructure, and a mistake means calls that ring nowhere. This guide is the careful way to do it, step by step, with a pilot and a way back.

If you are still deciding whether to replace your IVR, start with our voice AI vs IVR cost comparison. This article is about how.

The short version

Keep your numbers and carrier. Map every menu option to what callers actually want. Pilot the AI agent on one slice of traffic for two weeks against a baseline you measured first. Then cut over one branch at a time, with the old menu one setting away.

What changes and what stays

An IVR replacement is smaller than it sounds. You are replacing one layer of your phone system, not the whole thing.

LayerBeforeAfter
Phone numbersYour numbersSame numbers
Carrier and contractsYour carrierSame carrier
PBX, queues, extensionsYour PBXSame PBX
The menuRecorded prompts, keypad or keyword choicesAI agent that listens and talks
Routing to peopleMenu option to queueAgent transfers to the same queues and numbers
Simple tasksUsually sent to a personAgent answers or completes them

Keeping the bottom of the stack untouched is what makes the migration safe.

Three ways to migrate

There are three common patterns. Most teams use them in this order.

PatternHow it worksGood forRisk
A. AI as a menu optionYour IVR gets a new option ("press 0 to speak to our assistant") that sends callers to the AI agentFirst pilot, no change to the main pathVery low; only callers who choose it reach the AI
B. AI after hoursOutside business hours, calls go to the AI instead of the menu or voicemailTesting on real traffic when staff are not thereLow; daytime path unchanged
C. AI as the front doorEvery call reaches the AI first; it answers, completes or transfersFull replacementMedium; needs a tested transfer map and rollback

Pattern A and B can both run at the same time. Move to C only when the pilot numbers say you should.

Step 1: Export your IVR tree

Write down every node of the current menu, including the ones nobody remembers adding. For each one, note:

  • the prompt the caller hears
  • what each key does
  • where the call ends up (queue, extension, voicemail, recording, hang-up)
  • how many calls reach that node each month, if your system reports it

Most teams find options that lead nowhere, duplicates, and recordings with out-of-date information. Write those down too; they are part of why callers press zero.

Step 2: Turn menu options into intents

A menu option is what your system offers. An intent is what the caller wants. The AI works from intents, so translate.

Listen to a sample of recent calls, or ask the people who answer them, and build a table like this:

Caller intentExample phrasingOld menu pathResolved byData needed
Opening hours"Are you open Saturday?"1 then 3 (recording)AI answersHours in knowledge base
Book or change appointment"Can I move my Thursday slot?"2 then queueAI completesBooking tool
Order status"Where is my order?"3 then queueAI completesOrder lookup tool, order number
Billing dispute"I was charged twice"4 then queueTransferBilling team number
Sales enquiry"I want a quote for..."1 then queueAI qualifies, then transferQualification questions
Anything else0TransferFront desk number

The "Resolved by" column is the core of the migration. There are only three values:

  • AI answers: information questions. These come from a knowledge base of your documents.
  • AI completes: a task with a clear end. These need a tool that talks to your system.
  • Transfer: anything that needs a person. These need a destination and a rule for when.

Step 3: Decide where keypad input stays

Do not remove the keypad on principle. Speech is better for "my boiler is making a noise". The keypad is better for:

  • account numbers, policy numbers and order numbers
  • PINs and verification codes
  • extensions, for callers who already know them

On Call2Me the dtmf_input built-in function collects digits in the middle of a spoken conversation: "Please type your eight-digit account number followed by the hash key." The caller gets the best of both.

Step 4: Build the agent around the intent map

Write the agent's instructions directly from the table in step 2. A useful order:

  1. Who it is and the one-sentence job: answer, complete or route calls for your business.
  2. The answer list: topics it may answer from the knowledge base.
  3. The task list: each tool, when to use it, and what to confirm before using it.
  4. The transfer list: each destination and the exact trigger, including "the caller asks for a person" and "the caller is upset".
  5. The never list: prices not in the documents, advice you are not licensed to give, card numbers over the phone.

For the tasks, connect your systems with custom functions: a lookup or a booking call to your API. Keep each one fast; under 500ms is ideal, and the agent should say "let me check that" while it waits.

For routing, enable transfer_call and set the destinations: your existing queue numbers, extensions or SIP addresses, or another AI agent for a specialised job. Enable hold_call if lookups sometimes take a moment, and end_call so finished calls close cleanly. Our guide on writing prompts for voice covers the style side.

Step 5: Connect the telephony

You have three options, from least to most change:

Forward to an AI number. Buy a number for the agent (available in 21 countries on Call2Me) and have your IVR or PBX forward the chosen calls to it. Simplest for pattern A and B.

Connect over a SIP trunk. Your carrier or PBX sends calls straight to the agent and the agent can transfer back into your PBX. On Call2Me:

  • transports: UDP, TCP or TLS; SRTP is negotiated when your carrier offers it
  • codecs: PCMU, PCMA and Opus
  • tested with NetGSM, Twilio, Telnyx, Vonage, Asterisk and FreeSWITCH
  • you whitelist the platform's signalling and media IPs, shown in the dashboard, on your firewall

The full walkthrough is in connect a SIP trunk to an AI voice agent.

Move the number. Rarely needed. Direct number porting is not self-serve on Call2Me; the supported path is to keep the number where it is and connect it over SIP.

Step 6: Measure a baseline before you switch

You cannot judge the pilot without numbers from before it. From your current IVR and call logs, record for at least two weeks:

MetricWhat it tells you
Calls per day, by menu pathWhere the volume is
Abandonment rate in the menuHow many callers give up before reaching anyone
Zero-out rateHow many callers press zero to escape
Transfers per callHow often callers land in the wrong place
Repeat calls within 48 hoursWhether the first call actually resolved anything
Average time to reach a personThe wait your callers experience

Use your own data. Industry averages will not tell you whether your menu is better or worse than typical.

Step 7: Run the pilot

Start with pattern A or B, on one or two intents from your map, for at least two weeks.

During the pilot:

  • Read transcripts every day for the first week. Every Call2Me call has a full transcript, and optional recording at $0.005 per minute.
  • Define post-call fields for the outcome you care about, such as intent, resolved (true or false) and transferred_to. A model fills them in from the transcript after each call, so you can count outcomes without listening to every call.
  • Watch the transfer events. Agent webhooks send call_transferred and transfer_failed, so you know immediately if a destination is not picking up.
  • Fix in the right place. Wrong answers are usually a document problem. Wrong routing is usually an instruction problem. Slow replies are usually a slow tool.

At the end, compare the same metrics as your baseline, for the pilot slice only.

Step 8: Cut over, one branch at a time

When the pilot beats the baseline, move to pattern C in stages: route one more intent to the agent each week, or start with the line that has the simplest menu.

Before each step, write down the rollback: which setting in your PBX or carrier sends calls back to the old menu, and who can change it. Keep the old IVR configuration intact for at least a month after full cutover. You will probably not need it, but the day you do, you will need it fast.

The cost model

Compare cost per resolved call, not per minute. An IVR minute is cheap, but a menu that sends most callers to a person anyway is not.

A simple model you can fill in with your own numbers:

Old cost per month
  = IVR platform cost
  + (calls reaching staff x average handle minutes x staff cost per minute)

New cost per month
  = (all calls x average AI minutes x $0.11)
  + (calls still transferred x average handle minutes x staff cost per minute)

On Call2Me there is no setup fee or subscription; inbound minutes are $0.11 ($0.10 voice plus $0.01 phone line), and ringing or unanswered attempts are not billed. If you connect over SIP, your carrier charges stay with your carrier. The pricing page has the full rate card, and our ROI calculator walkthrough shows how to model the staff side.

Mistakes we see in IVR migrations

  • Copying the menu into the prompt. "Say 1 for sales" read by an AI is still a menu. Build from intents, not options.
  • No transfer rule for upset callers. The agent must hand off when a caller is frustrated, not keep trying.
  • Removing the keypad entirely. Long numbers over speech fail more often.
  • Skipping the baseline. Without it, the pilot result is an opinion.
  • Switching everything on a Monday morning. Cut over at a quiet time, one branch at a time, with someone watching.
  • Forgetting the out-of-date recordings. Whatever the old menu said about hours and policies should be checked before it goes into the knowledge base.

When to keep the IVR

Replacement is not always the right call. Keep a simple menu, or keep it in front of the AI, if:

  • almost all your calls are a single routing choice that a keypad already handles well
  • a regulation requires a specific recorded disclosure at the start of every call (you can also have the agent read it, but check with your advisor)
  • your volume is so low that the menu rarely matters

For everyone else, the usual result is a phone line where callers explain what they need once and either get it or reach the right person.

Start with a pilot

Build an agent for one intent from your map, give it a number, and add it as an option in your current menu. Nothing else changes, and in two weeks you will have your own numbers.

Build your pilot agent free →

Frequently asked

Q.What is an AI IVR?

An AI IVR, sometimes called a conversational IVR, replaces the 'press 1 for sales' menu with a voice agent. The caller says what they need in their own words; the agent understands it, answers routine questions itself, completes simple tasks like booking or looking up an order, and transfers to the right person when needed. Keypad input can stay for things it does better, such as PINs and account numbers.

Q.Do I need to change my phone numbers or carrier to replace my IVR with AI?

No. The usual approach is to keep your numbers, carrier and PBX, and replace only the menu layer. You connect the AI agent to your existing setup over a SIP trunk, or your current IVR forwards some callers to the agent's number. Call2Me works with any carrier or PBX that speaks SIP over UDP, TCP or TLS.

Q.How long does an IVR to AI migration take?

A pilot on one call type can be live the same day. A full replacement takes longer, mostly because of the work around it: mapping the existing menu tree, writing transfer rules, connecting systems the agent needs to look things up in, and measuring a baseline. Plan a few weeks from inventory to full cutover, with a pilot of at least two weeks in the middle.

Q.Should I keep keypad input after replacing the IVR?

For some tasks, yes. Speech is better for explaining a problem; keypads are more reliable for long digit strings like account numbers, PINs and extensions. A good AI replacement lets callers speak by default and offers the keypad when digits are needed. On Call2Me the dtmf_input built-in function collects digits during the conversation.

Q.What does it cost to replace an IVR with AI?

On Call2Me you pay per minute with no setup fee or subscription: $0.10 per minute for the voice agent plus $0.01 per minute for the phone line, so $0.11 per minute for inbound calls. Recording is optional at $0.005 per minute. Your existing carrier or PBX costs stay as they are if you connect over SIP. The real comparison is cost per resolved call, not per minute.

ShareX / TwitterLinkedIn

Try Call2Me free

Spin up a voice agent in 5 minutes. No credit card required.

Start free trial

An interpreter or a voice agent, billed by the minute.

Start with free credit and no card. You pay only while a call is running.