IVR and phone menus

Speech Menus vs Keypad Menus: Which IVR Input Works Better

Compare voice-driven and key-press phone menus on accuracy, accessibility, noise, cost of change and caller experience, and learn when to combine both.

Call editorial team · Published · 5 min read

For decades, phone menus meant pressing keys. Speech recognition promised something friendlier: just say what you need. In practice neither input is simply better. Each suits certain callers, situations and menu shapes. This guide compares them, explains where each fails, and shows how to combine them. For a wider view of voice systems, see IVR vs AI Voice Agent.

A person speaking into a phone in a busy street
Illustrative image

How each approach works

A keypad menu (often called DTMF, after the tones phones make) tells the caller which key to press. The system hears a tone and follows a rule. A speech menu asks the caller to say something. The system converts the audio to text and decides what it means, either by matching a list of expected words or by interpreting free language.

Keypad and speech at a glance

Keypad (DTMF)Speech
Caller effortPress a key; must remember the numberSay what they want; no numbers to remember
ChoicesA handful per menuMany choices possible without reading a list
NoiseWorks well in loud placesStruggles with background noise and poor lines
Accents and namesNot affectedCan misrecognise accents, names and numbers
Hands-free useNeeds a free hand and a screen-free phoneWorks when driving or hands are busy
PredictabilityVery highVaries with the speaker and the line
Changing the menuRe-record and remapUpdate phrases or training; may need re-testing

Where keypad menus win

Where speech menus win

Speech also exposes what callers actually say, giving you wording to improve your menu and your help pages. Speech Recognition on Phone Calls explains why telephone audio is a harder test than most people expect.

How each can fail

What goes wrong

  • MishearingSpeech systems pick the wrong option, particularly with accents, names and numbers.
  • Over-talkingCallers speak too early, too late or in full sentences the system was not expecting.
  • Key confusionCallers press the wrong key, or forget the options by the time the list ends.
  • Hidden optionsCallers do not know what they are allowed to say or press.
  • Frustrating loopsRepeated "I did not understand that" with no escape wears patience thin.

Whichever you choose, the way out matters more than the input. Limit retries to two, then switch to the other mode or to a person.

Use both, with keys as the safety net

Most successful menus accept either input. The prompt says what to do in plain words: "You can say or press. For orders, say orders or press 1." That wording teaches callers the keys while letting the confident ones speak. If speech fails twice, the system should switch to key presses without fuss.

A combined flow

  1. PromptOffer a short list in words and keys together.
  2. ListenAccept speech or a key press at any point, including during the prompt.
  3. Confirm when unsureIf the system is not certain, repeat what it understood and ask yes or no.
  4. Fall backAfter two misses, offer keys only, then a person.
  5. LearnReview misrecognised phrases and add them to the vocabulary or reword the prompt.

Accessibility and privacy

Some callers cannot speak clearly, and others cannot press keys. Offering both is the most inclusive default. Speech recordings may also count as personal data, so tell callers when audio is processed and kept, and keep only what you need. Accessible Phone Menus for Every Caller and Personal Information on Calls cover these points.

Choosing for your business

Whatever you decide, write the decision down with the reasons. Technology and callers change, and a record of why you chose keys, speech or both helps the next person judge whether the answer still holds.

Questions to settle the choice

  • How many destinations does the first menu need?
  • Where do your callers usually call from: quiet homes or busy places?
  • Are names, reference numbers or addresses required in the menu?
  • Who will maintain the speech vocabulary or prompts?
  • Can you test with callers from your real audience, not colleagues?
  • Is there a dependable route to a person when either input fails?

Writing prompts for either input

Prompts decide whether callers succeed with speech or keys. Start with a short question, offer a few examples of what can be said, and place keys after the words. For example: "Which department do you need? You can say sales, support or billing, or press 1, 2 or 3." Callers who are comfortable with speech answer straight away, and the rest simply press.

Avoid asking open questions when only a few answers are possible, because callers will respond in ways the system cannot map. Avoid long explanations before the question. And keep the same wording style across all menus so callers learn the pattern once.

Testing speech and keys properly

Menus tested only by their authors tend to work beautifully. Real callers use mobile phones in cars, speak quickly, and say things nobody anticipated. Build a test group that reflects your audience and give them tasks, not scripts: "Find out whether your delivery has shipped." Watch where they hesitate.

Testing an IVR Before Launch provides a fuller checklist, including error paths and closed-hours behaviour.

Keys and speech in Call

In Call, the main way to give callers a choice is the phone menu built from options that lead to queues, with business hours and holidays deciding where calls go. Voice AI agents can also answer a line, speak with callers and put them through to a person when they ask; this is designed to cover natural speech, though accuracy varies with audio quality, so test your own lines. Treat the keys as the dependable path and speech as a convenience. See Setting Up IVR and Business Hours in Call for the menu, and Testing Voice AI Agents for how to check a speech-driven line.

Frequently asked questions

Is speech recognition more accurate than keys?

No. Keys are almost always exact; speech is convenient but can misunderstand. The best approach lets the caller use either and falls back to keys.

Do callers prefer speaking to pressing keys?

It depends on the caller and the situation. Many like speaking when options are many; others prefer keys in noisy or private settings. Offering both removes the argument.

Is a speech menu more expensive?

Usually it takes more effort to build, tune and test, though costs vary with the technology. Compare the effort to maintain each, not only the purchase.

Can speech menus handle accents and names?

They can struggle. Test with speakers from your real customer base, and give callers a way to switch to keys.

Should I switch an old keypad menu to speech?

Only if you see a real problem, such as too many levels or poor completion rates. A working short keypad menu is hard to beat.

How do I measure which works better?

Compare completion rates, the share of callers who reach the right place, retries, and how many ask for a person. Run both versions for a period if you can.

Plan phone menus that accept both speech and keys in Call

In the demo console you can try incoming calls in a simulation.

Related guides