What is interactive voice response?
Interactive voice response (IVR) is the automated system that answers a phone call before a person does. It plays a greeting, offers options (“press 1 for billing, press 2 to report a fault”) and acts on the caller’s choice. Callers respond by pressing keys on their phone (often called DTMF input) or, in more modern systems, by speaking.
An IVR does two main jobs. First, it routes the call: the caller’s choices, along with data such as the number they rang from, tell the automatic call distribution (ACD) system which queue or which agent skill the call needs. Second, it can resolve simple requests on its own, such as reading out an account balance, confirming an appointment or giving the latest outage update. This is a form of customer self-service.
How an IVR works
A typical IVR call flow follows a series of steps:
- Answer and greet. The system picks up and plays a welcome message, sometimes with an urgent notice first (for example, a known outage in the area).
- Identify the caller. It may ask for an account number or match the caller’s phone number against the CRM.
- Capture the reason for calling. The caller picks a menu option or says what they need. Speech-enabled IVRs use automatic speech recognition to interpret the answer.
- Self-serve or route. Simple requests are completed in the IVR. Others are passed to a queue, often using skills-based routing so the call reaches an agent who can handle it.
- Pass context to the agent. A well-integrated IVR sends what it has collected to the agent’s screen through computer telephony integration, so the caller doesn’t have to repeat themselves.
Why IVR matters
A good IVR gets callers to the right place first time, which improves first contact resolution and reduces transfers. It takes simple, repetitive calls away from agents, freeing them for conversations that need judgement. And in a sudden spike such as a call avalanche, a single accurate message at the front of the call can answer thousands of callers at once.
A poor IVR does the opposite. Long menus, unclear options and dead ends frustrate callers, push up abandonment and leave agents dealing with customers who are already annoyed.
Good practice in IVR design
- Keep it short. Limit the number of options and levels, and put the most common reasons for calling first.
- Use customers’ language. “Report a power cut” is clearer than “network services”.
- Always offer a way out. Callers who need a person should be able to reach one without guessing.
- Prioritise urgent calls. Safety and hazard calls should have a fast, obvious path to an agent.
- Keep messages current. An out-of-date outage message causes more calls, not fewer.
- Measure it. Track where callers drop out, which options they choose and how often they reach the wrong queue, then adjust.
From menus to conversation
Many organisations are now replacing or supplementing touch-tone menus with an AI voice assistant built on conversational AI. Instead of navigating a tree, the caller simply says what they need. The assistant works out the intent, completes routine tasks and transfers more complex calls to a person. Success is often measured by containment rate, alongside customer satisfaction, because the aim is to resolve calls properly rather than simply keep callers away from agents.