Let's face it: customers hate using Interactive Voice Response systems (IVRs). They particularly dislike entering a seemingly endless series of prompts, wondering if they'll ever get an issue resolved. It's hardly surprising that most customers are dissatisfied with their IVR experiences.
According to a study by New York University, 83% of consumers said IVRs either provide them with no benefit at all or are only provided as a cost savings opportunity for the companies that deploy them. Consumer sentiment remains overwhelmingly negative toward IVRs.
As IVRs evolve from scripted prompts to AI-enabled IVA agents, its prevalence will only increase. Now is the time to take an honest look at your IVR system so you don’t repeat bad habits with new systems.
We recently dug deep into current IVR systems at some major brands to determine not only what people dislike about these systems, but also what works.
We ran hands-on diagnostics — mapping every caller path, transcribing every prompt, and grading what we heard against each brand's own voice and modern contact-center technology standards.
Across the three systems we assessed — a large national retailer, a major sports league, and a global automaker — every one scored an overall 3 out of 10, with the verdict "Rebuild" across dimensions from brand alignment to menu structure to emotional intelligence. None offered meaningful self-service at the head of the call. None sounded like the brand they belonged to. And all forced callers to navigate structures built around internal departments rather than caller intent.
Key finding: IVR is a time suck
A key component of customer dissatisfaction is that people feel like their time is being wasted. Today, companies force callers to enter information and play marketing messages, website information, and business hours — causing long delays and frustrating customers who often have no other way to do business with that company.
Our diagnostics put a stopwatch on this. A major sports league's subscriber support line burned an estimated 43 seconds before the caller's issue was acknowledged. A global automaker's line fared little better, with callers waiting 30-plus seconds just to reach the menu. When the experience is built around the company's needs rather than the callers’, the wait is the first thing the customer hears.
How do you improve contact center IVR design?
IVR software needs to cater to the user, not the company. This requires reviewing business rules, associate skill group mapping, and gaining up-front information on who customers are and what they may need based on account status.
An IVR can be proactive by accessing the customer database using the Auto Number Identifier (ANI) or the caller's account number, then providing information specific to that caller — asking "are you calling to make a payment?" when a bill is due, for instance. When a call is transferred, the associate should know everything the caller already provided.
But our diagnostics show how rarely this proactive posture exists. In one assessment of a large national retailer, a loyalty program with more than 100 million members went unacknowledged anywhere in the IVR — no ANI lookup, no recognition of returning guests, just generic boilerplate that could have belonged to any retailer from any decade.
A customer-centric Voice User Interface (VUI) design can strengthen customer satisfaction by enabling users to navigate options with ease and get tasks resolved quickly.
Here are 10 IVR design best practices:
1. Always provide customers with a live associate option
The first rule of the IVR is providing an option to reach a live associate. Yet our diagnostics found it routinely violated. In the major sports league's IVR, an automated audit mapped roughly 120 unique paths and uncovered four significant failures — including a "Help logging in" option that looped callers back to the same tech-support menu, and a cancellation path that looped indefinitely with no way to reach a human, a potential compliance risk.
Test every path for where it dead-ends, and ensure no caller is ever more than one choice away from a person.
2. Make 'call recording' announcements only on transfers
Customers understand calls are often recorded, but they don't need constant reminders — or any legal or disclaimer message — read up front. In one retailer diagnostic, a lengthy privacy-practices notice was read mid-call, unprompted, at a post-college reading level. In the automaker's IVR, calls opened with generic disclaimers before any useful option appeared.
Confine such messages to transfers or regulatory triggers and keep them in plain language.
3. Offer a non-primary language early
Placing this option early recognizes customers' needs. "Early" is the operative word: in the global automaker's diagnostic, the Spanish option was buried after lengthy English announcements, forcing non-English callers to sit through content they couldn't use before choosing their language. Place language selection at or near the very front of the call, before any substantive content.
4. Keep main menu options to 30 seconds
The sports league's line took an estimated 43 seconds before a caller's issue was acknowledged, and the automaker's took 30-plus seconds to reach the menu. Length isn't the only problem; density is.
In the retailer's IVR, options were read as long, qualifier-heavy sentences; a single option ran "Safety, property damage, injury, or illness concern with a product, press 3," repeated verbatim on every failed input.
Shorten prompts, split compound options, and get to the first choice quickly.
5. The IVR should sound like an associate
VUI designers can humanize the IVR with pre-recorded voice responses that sound like an associate, using the right inflection and tone. Voice quality was a recurring weakness we found. The automaker relied on a low-quality text-to-speech voice that sounded unnatural and off-putting. The sports league's prompts included no brand vocabulary, and no acknowledgment of the caller as a fan.
Invest in a natural, well-tuned voice, and write prompts in the brand's own tone. The IVR is often the first human-sounding thing a caller encounters.
6. Use voice recognition and silence for turn-taking
Strong voice recognition lets the IVR provide natural pauses so customers can speak just as they would in a conversation. Too many systems we diagnosed haven't made this leap at all.
The sports league's IVR was keypad-only throughout, with no open-ended dialogue, no natural language understanding, and not even basic speech recognition. The automaker compounded this with overly fast delivery, insufficient pauses, and short timeouts that left callers scrambling.
Replacing DTMF-first menus with an intent-driven, natural-language front end is one of the highest-impact upgrades a brand can make.
7. Allow barge-in for all prompts
If your IVR doesn't have speech recognition to allow callers to interrupt, make sure prompts are worded so callers know they shouldn't speak until the prompt is completed. When callers can't interrupt, every long prompt becomes a hostage situation.
Keep prompts short if barge-in isn't available; enable it where speech recognition is in place so callers can move at their own speed.
8. Make sure instructions are provided only when an error is made.
There's no need to irritate callers with superfluous instructions. This also applies to prompts that fire at the wrong moment. In the automaker's IVR, the "have your VIN ready" prompt was delivered after callers had already navigated to the next menu.
Audit your call flow: instructions should appear exactly when they're actionable, and only then.
9. Rethink error messages from the customer perspective
Rephrase the options if callers make a mistake. Our diagnostics found error handling that does the opposite.
The automaker delivered abrupt, insensitive error messages with little guidance. The retailer greeted mistakes with "Sorry. That isn't a valid option," and some paths terminated without recovery: "Thanks for calling. Goodbye," sometimes without any resolution.
Rephrase rather than repeat, offer a clear next step, and never disconnect for failed inputs. Three failed attempts should mean a warm offer to connect to a human, not a hang-up.
10. Information provided by a customer to the IVR should be extended to an associate
One of the greatest frustrations is having to repeat information. When the IVR is purely a routing mechanism, this best practice becomes impossible — because the IVR never gathered anything worth passing along.
The fix starts with intent-based call flows: capture what the caller needs before the transfer, resolve what can be resolved in self-service, and pass the full context so the conversation picks up where the IVR left off — not starts over.
What’s the next chapter for call center IVR?
Too often, IVRs are built without a coherent brand and caller model, where options reflect internal structure rather than caller intent, self-service is nearly absent, and the experience sounds nothing like the company behind it.
The remedy is to treat the IVR as a CX product rather than a telephony feature. Document the caller persona, define a brand voice, replace DTMF menus with a natural-language front end, build always-on self-service for top intents, and monitor continuously so failures are caught automatically rather than by ad-hoc audit.
Create a system for customers to quickly resolve issues, and they will embrace the channel rather than repel it.
For more, download 5 ways to increase customer satisfaction using IVR.
