What is interactive voice response?
Interactive voice response, usually shortened to IVR, is the menu-driven system that answers a telephone line and routes a caller through numbered options. It handles a fixed set of paths defined in advance and collects input by keypad or through a small recognised vocabulary. A voice agent is generally deployed to replace it or to answer in front of it.
Also called: IVR, Voice menu
Why a menu is worth reading closely before it is replaced
Replacing an IVR is usually presented as removing it, and what actually happens is that its assumptions are inherited. The menu encodes years of decisions about which department owns which problem, and those decisions live in the routing table rather than in any document. A deployment that discards the menu without reading it recreates the same dead ends in conversational form. The other thing an IVR carries is caller habit, since a proportion of callers will press a key from memory before the agent has finished its greeting.
- The menu tree is documentation of how an organisation routes its work.
- Callers have learned the key sequences and will use them regardless.
- An IVR is predictable, which is why compliance teams trust its scripted paths.
- Replacing a menu without examining it reproduces its routing errors in conversation.
How interactive voice response works
- The line answers and plays a recorded or generated prompt.
- Keypad tones or a limited spoken vocabulary select an option.
- Selections traverse a tree towards a queue or an automated task.
- Caller data is retrieved and read back from a connected system.
- Unmatched input repeats the prompt and eventually transfers to a queue.
- A conversational agent is placed in front of this tree, keeping the existing routes available.
How interactive voice response is evaluated
An existing IVR is measured before any replacement, since that comparison is the business case. Examine the following on the menu in operation:
- completion rate per menu path against entries at the top
- depth at which callers abandon
- proportion of callers pressing zero or asking for a person immediately
- mis-routing rate measured at the receiving queue
- menu paths receiving almost no traffic
Limitations, risks and common failure modes
- Menu trees grow by addition and are almost never pruned.
- Key presses learned by regular callers are discarded by the replacement.
- Routing rules live only in the configuration of a vendor platform.
- The replacement is compared on speed alone while losing the menu's predictability.