A call center IVR (interactive voice response) answers inbound calls, asks what the caller needs by keypad or voice, handles a few simple requests itself and routes the rest to a queue. Whether to keep yours, tune it or add AI agents depends on where its calls end, and your platform already reports that.
The table below sets out the options side by side. After it comes a scorecard: six numbers to pull from your own reports, how to calculate each one, and which option a bad reading points to.
Should you keep, tune or replace your call center IVR?
Choose by the problem your numbers show. If the menu sends callers to the wrong place or takes too long to get through, tune it or add speech recognition. If the menu works and callers still give up in the queue behind it, no menu change will help. That takes capacity: more people, or something that finishes calls before they join the queue, such as an AI agent option.
| Option | What changes for the caller | Effect on the queue behind the menu | What you build | Choose it when your numbers show |
|---|---|---|---|---|
| Leave it as it is | Nothing | None | Nothing | Calls that end in the menu end with the task done, and few of those callers ring back |
| Tune the menu | Fewer options, in the order people need them, and one step to a person | Fewer calls land in the wrong queue, and the same number reach agents | New prompts and option order in your flow designer | Long menu time, many requests for a person, or agents transferring calls the menu routed |
| Add speech recognition | Says why they are calling instead of pressing a digit | Calls arrive better sorted, and the volume stays the same | Intents, sample phrasings, a confidence threshold and a path for unrecognized answers | Callers pick the wrong option, or "everything else" is one of your biggest branches |
| Add an AI agent option to the menu | Can choose an agent that answers now and finishes the request, or keep waiting | Calls the agent finishes never join the queue | Knowledge, transfer rules, access to the systems that hold the answers, and testing | Callers abandon the queue, and many queued calls need one lookup or one booking |
| Send every call to an AI agent first | Talks to an agent from the first ring, and it transfers what it cannot finish | The biggest change, with the most to get wrong | Everything in the row above, for every call type | An agent option has already shown which call types it finishes |
Tuning and speech recognition change how calls get sorted. Only the two agent rows change how many calls need a person, so rebuilding a menu that already routes well does nothing for a queue that is too long. Speech recognition has its own guide, what conversational IVR changes and what it leaves alone, with a worksheet that goes through your menu one option at a time.
What does an IVR do in a call center?
The IVR is the first stage of an inbound call. It answers, works out who is calling or why, offers self-service where it can, checks the hours and hands the call to a queue, an outside number or voicemail. All of that happens before the automatic call distributor puts the call in line for an agent.
The platforms draw that line in their own reporting. Amazon Connect defines contact flow time as "the IVR time, the time from the start until contact is queued" (Amazon Connect metric definitions). Genesys Cloud reports its IVR flows in a separate Flows Performance view, which it describes as measuring self-service success, and its Destinations tab shows how voice calls enter and leave each IVR flow (Flows Performance Summary view).
That gives the menu reports of its own, apart from the queue and agent reports a supervisor reads every day. The rest of the call, from the queue to wrap-up, is laid out stage by stage in the inbound call center guide.
Which numbers show whether your IVR is working?
Six numbers, pulled monthly and per menu branch where your platform allows it, show where the menu loses callers. Three come from standard reports. The other three need a marker in the flow at the step that matters, which is a one-time change in your flow designer.
| Number | How to calculate it | Where to find it | A bad reading points to |
|---|---|---|---|
| Time in the menu | Seconds from answer to queue, averaged over calls that reached a queue | Amazon Connect: contact flow time. Elsewhere, your IVR or flow report | Too many options, or prompts that run long. Tune it, and compare it with the average wait in the queue behind it |
| Where calls leave the menu | Calls ending at each outcome (sent to a queue, sent to an outside number, ended by the menu, dropped) divided by calls that entered | Amazon Connect: flows outcome percentage. Genesys Cloud: flow outcomes and the Destinations tab | If nearly every call goes to a queue, the menu only routes, and tuning it will not shorten the line |
| Tasks finished in the menu | Calls that reached the confirmation step of a self-service task, divided by calls that entered | A success outcome or milestone you set at that step | Self-service options that callers start and do not complete |
| Requests for a person | Calls that pressed 0 or asked for an agent, divided by calls that entered, per option | A marker on that branch | High on one option means its self-service is failing. High everywhere means callers are skipping the menu |
| Transfers after the menu | Contacts agents transferred out, divided by contacts answered | Amazon Connect: contacts transferred out by agent | The menu sends calls to the wrong queue. Tune the options, or add speech recognition |
| Abandons in the queue | Contacts abandoned, divided by contacts queued | Amazon Connect: abandonment rate | The problem sits behind the menu, in too few people for the calls that need one |
Amazon Connect's flow outcomes separate a call that dropped out of the flow from one that reached a disconnect block, one sent to a queue and one sent to a phone number, and its abandonment rate leaves out contacts queued for a callback (metric definitions). What the outcome report cannot tell you is whether the caller got what they called for. A balance lookup that failed and played a goodbye reaches the same disconnect block as one that worked, which is why the third row needs its own marker. Callers who finish in the menu and ring back the next day about the same thing were not served either, and net call deflection subtracts them per call type.
Read the six together. Long menu time, frequent requests for a person and transfers after the menu add up to a sorting problem, which tuning or speech recognition can fix. A short, accurate menu in front of a queue callers abandon is a capacity problem, and no menu change touches it: the answer is more people, callbacks, or an agent that finishes the simpler calls, depending on what those queued calls are.
One planning check, which is a rule of thumb rather than an industry benchmark: if callers spend longer in your menu than in the queue behind it, the menu costs them more time than your staffing does, and that is the first thing to fix.
How do you tune an IVR you are keeping?
Start from the outcome report, not the org chart. Put options in the order callers choose them, merge options that end in the same queue, keep a one-step way to a person at every level, and change one thing at a time so the next month's numbers show which change worked.
- Rank the options by how many callers choose each one last month, and put the most chosen first.
- Merge any two options that send calls to the same queue. Every extra option adds listening time for each caller who waits for theirs.
- Keep the way to a person on every level, and track requests for a person per option instead of hiding it. A rising count on one option tells you where its self-service broke.
- Make one change a month and read the scorecard again before the next one.
How much does a call center IVR cost?
On platforms priced per agent seat, the IVR is a feature of the plan rather than a line of its own, so check which plan includes it; our comparison of AI call center software lists published seat prices. On usage-priced platforms you pay for every minute a caller is connected, and the minutes in the menu count. Amazon Connect publishes the rates for both kinds of menu.
| Charge on Amazon Connect, read October 28, 2026 | Customer Basic plan | Amazon Connect Customer |
|---|---|---|
| Voice usage for the whole call, menu included | $0.018 a minute | $0.038 a minute |
| Speech recognition and self-service in the menu | $0.008 a minute, plus Amazon Lex at $0.004 per spoken request | Included in the voice rate |
| US inbound telephony on a direct number (AWS's US West example) | $0.0022 a minute, plus $0.03 a day per number | The same telephony rates |
Rates are from the Amazon Connect pricing appendix, which bills voice usage on how long the caller is connected, and Amazon Lex pricing.
Take 20,000 calls a month that each spend 40 seconds in the menu, which is 13,333 menu minutes. On the basic plan a touch-tone menu costs about $269 a month for those minutes, voice usage plus per-minute telephony. The same menu with speech recognition, at two spoken requests a call, costs about $536: $376 in minutes and $160 in speech requests. Cutting ten seconds from every call saves 3,333 minutes, or about $67 a month on the touch-tone menu. The call count and menu time are made up for the example, so put your own in their place.
At these rates the menu's own bill is small. The bigger cost sits in the agent minutes behind it: calls the menu sends to the wrong queue, which an agent then has to transfer, and callers who give up waiting and call back. Amazon Connect Customer prices the whole call at $0.038 a minute with self-service included, so the choice between its two plans turns on the minutes after the menu more than the minutes in it.
How Telvana adds an agent to the IVR you have
Telvana attaches as one more option in your existing menu, pointed at the agent's number, so calls reach it from any phone system that can transfer to an outside number. Callers who choose it are answered at once, and callers who would rather wait for a person keep their place in line (hold queue relief).
The agent answers from the knowledge base you give it and takes the actions you allow: looking up a customer, checking availability, booking, rescheduling and cancelling. When a call needs a person, it transfers to the number you name under your rules. Every call is recorded, transcribed, summarized and tagged by outcome, so the option gets its own row on the scorecard: what it finished and what it handed back.
Our team builds the agent from your scripts, FAQs and transfer rules, tests it on your own call types, and you approve it before it takes a live call. Pricing starts at $399 a month based on call volume, plus a one-time setup fee for the build (pricing).
Frequently asked questions
What does IVR stand for in a call center?
IVR stands for interactive voice response. In a call center it is the automated system that answers calls, plays the menu, takes keypad or spoken input, handles simple self-service and sends each call to a queue or a number. Many teams call the menu itself "the IVR."
What is the difference between an IVR and an ACD?
The IVR works out what the caller needs. The automatic call distributor, or ACD, holds the call in a queue and gives it to an available agent with the right skill. On cloud platforms both live in the same product, but they report separately: menu time and flow outcomes for the IVR, waits and abandons for the queue.
What is IVR containment?
Containment is the share of calls that ended in the IVR without reaching a person. A caller who gave up counts the same as one who got an answer, so read it next to tasks finished in the menu and repeat calls. The call deflection worksheet shows how to subtract the calls that come back.
Can an IVR use AI?
Yes, in two different ways. Speech recognition lets callers say what they want instead of pressing digits, and the call is still routed to a queue. An AI agent option finishes the request on the call, so the call never joins the queue. Only the second one reduces the calls your team handles.
Should callers always be able to reach a person?
Yes. Every level of the menu should offer one step to a person, and requests for a person per option is one of the six numbers worth tracking. A menu that hides the way out looks good on containment and sends the work back to your team as repeat calls and complaints.
How much does an IVR cost per call?
On Amazon Connect's basic plan, a touch-tone menu costs $0.0202 a minute in voice usage and telephony, so a 40-second menu comes to about 1.3 cents a call. With speech recognition and two spoken requests, it is about 2.7 cents. On seat-priced platforms the menu has no per-call price; it is part of the plan you buy.
Bring your menu report to a demo
Book a demo and bring last month's flow outcome report, or just a list of your menu options with their call counts. We will show you which options an agent could finish, let you hear it take one of your call types, and quote the monthly price and setup fee against your volume. More on menus, routing and inbound setup sits under inbound calls and IVR.