AI Chatbot Wiki

IVR (Interactive Voice Response)

The press-one-for-sales phone menu, how it compares to an AI voice agent, and why the old IVR is usually still sitting in front of your new one.

Updated 2026-08-18

IVR (interactive voice response) is the automated phone menu: "press 1 for sales, press 2 for support." The caller navigates a fixed tree using keypad tones or, in newer systems, a few recognized spoken words. Every business phone system in the last thirty years has one.

Why it matters when you are buying or building

An AI voice agent is not an IVR with better audio. The difference is structural. An IVR routes; it cannot answer anything. Callers who want a store's hours have to guess which branch leads to a human who knows. An AI agent answers directly, asks follow-ups, and only transfers when it needs to.

Where an IVR still wins is determinism. It always does the same thing, it never invents an answer, and it costs nothing per call. For a simple two-option routing problem with high volume, an IVR is fine and an AI agent is overkill.

What you usually want is both. Compliance disclosures, language selection, and payment capture belong in scripted deterministic steps. Open-ended questions belong to the agent. The pattern I use most often is an AI agent as the front door with clean transfer paths into existing extensions, rather than replacing the phone system.

What I have seen in production

The thing nobody warns you about: the existing IVR is often the reason your new agent never gets a call. Getting a business's phone traffic to an AI number means working with whatever carrier system is already in place, and those systems have opinions.

On one client's Verizon One Talk setup, the obvious path was the auto-receptionist, which is the built-in IVR. It would not forward to an external number the way we needed. The configuration that actually worked was group forwarding instead, a completely different feature in a different part of the admin. Hours lost in the wrong menu. That kind of carrier quirk is the real work in most voice deployments, not the AI. See phone forwarding for AI agents.

Second lesson: keep DTMF support alive. Callers who have used your old menu for years will start mashing keys the moment they hear automation. If key presses do nothing, they hang up. Handle at least "0 for a person."

Third: whatever you do, test by calling the real number from a real cell phone before you tell the client it is live. Simulators do not carry caller ID or carrier behavior, and some faults only appear on a genuine call. That is covered in testing voice agents.