Voice AI conversation gets all the attention, which means a lot of teams build a full conversational agent to collect an answer that is one of three options. It works, but it is the expensive way and the fragile way.
The alternative is a keypad agent: play a short spoken menu, read the key pressed, act on it. Press 1 to confirm, 2 to reschedule, 9 to opt out.
Why it beats a conversation for this job
It cannot mishear. A DTMF tone is unambiguous. Speech recognition on a bad line from a moving vehicle is not, and "two" and "true" are genuinely hard for a model when half the frequency range has been stripped by the phone network. If you only need one bit, introducing speech recognition adds the single most failure-prone component in the stack for no benefit.
It works on any handset. No accent handling, no code-mixing, no background noise problem. A ten-year-old feature phone in a noisy market produces the same clean signal as a new smartphone in a quiet room.
It is cheap. No language model in the loop and cached audio, so the economics look like an announcement rather than a conversation.
It is auditable. Every keypress is logged with its call. When someone says "I never agreed to that", there is a record of exactly which key was pressed and when — which is a materially better position than "the transcript says they said yes".
Where it fits
- Appointment confirmation. 1 to confirm, 2 to reschedule. The reschedules become a call list for a human.
- Delivery windows. 1 for morning, 2 for afternoon.
- Attendance and RSVPs. One press, thousands of people, an hour.
- Opt-out on any large campaign. Press 9 and the number is suppressed for future calls automatically.
- Simple triage. Route the person to the right follow-up without a human answering first.
Designing a menu people actually complete
Three options, maximum. People cannot hold five in their head while listening. If you need more, you need a conversation.
Say the action before the number. "To confirm, press 1" beats "press 1 to confirm" — the listener knows whether to care before the digit arrives, rather than having to remember three digits and match them afterwards.
Say why you are calling first. A menu that opens cold gets hung up on. One sentence of context, then the options.
Always include an opt-out. It costs one line, and it is the difference between a campaign that annoys people once and one that generates complaints.
Repeat once, then stop. If nothing is pressed, replay the menu a single time and end the call. Looping is what made IVR hated.
The combination that works well
Announcement for the information, keypad for the one decision, conversation only for the people whose answer needs a discussion. A thousand confirmations get handled for the price of announcements; the eighty who pressed 2 become a short call list for a person who can actually solve the scheduling problem.
That is usually the cheapest correct design, and it is three agents rather than one clever one.
Keypad activity is visible in the dashboard so you can see the response distribution as it comes in — which is also the fastest way to learn that your menu wording was confusing.