IVR and phone menus

Accessible Phone Menus: Designing an IVR Every Caller Can Use

How to make phone menus usable for callers with hearing, speech, cognitive or mobility needs: timing, wording, alternatives, relay services and testing.

Call editorial team · Published · 5 min read

Phone menus are designed by people who can hear well, speak clearly and press small buttons quickly. Many of your callers cannot do one or more of those things comfortably. Some have a permanent disability; others are older, stressed, in a noisy place, or using a phone they are not used to. A menu that works only for the fastest, clearest caller shuts out a lot of customers. This guide offers practical ways to make a phone menu more accessible. It is general guidance, not a legal standard; accessibility duties differ between countries.

A caller using a phone with a large keypad while reading a printed note
Illustrative image

Who your menu may be failing

Callers who need more from a menu

  • Callers with hearing lossMay miss words, mishear options or rely on text-based relay services.
  • Callers with speech differencesMay not be understood by speech recognition, or may find voice-only input stressful.
  • Callers with cognitive needsMay struggle with long menus, unfamiliar terms or strict time limits.
  • Callers with limited dexterity or tremorMay find small keypads or timed key presses hard.
  • Older callers or those new to the technologyMay need slower prompts and reassurance.
  • Callers in difficult conditionsTraffic, crowds or a poor signal affect everyone, not only people with disabilities.

Designing for these callers helps everyone. Short menus, clear wording and generous timing are simply better menus.

Pace and timing

Time pressure is the commonest barrier. If the menu moves on before a caller has found the key, or hangs up after a short silence, anyone slower than average is shut out.

Clear, plain wording

Language that sounds fine to insiders can confuse others. Choose short sentences, everyday words and one idea per prompt.

Reworking a confusing prompt

BeforeAfter
Wording"For all customer-related enquiries regarding your account, billing and subscription, please select option one.""For billing, press 1."
Problem solvedLong, abstract, many ideasShort, specific, action first
OrderReason, then keyReason, then key, with a pause before the next option

Avoid jargon and internal team names. Put the action before the key, name the option rather than only the number, and use the same words each time. IVR Menu Design gives more guidance on wording and structure.

Always offer another way

The single most useful accessibility feature is a clear way to a person. Some callers cannot use a menu at all, and they should be able to say or press one thing to reach someone. Letting Callers Reach a Person Quickly explains how to place it so every caller can find it.

Alternatives worth providing

  1. A personA key that goes to an agent, or to a message with a callback offer if nobody is free.
  2. Keys and speech togetherLet callers use whichever suits them. See Speech Menus vs Keypad Menus.
  3. Relay and text servicesMake sure calls from text relay and video relay services are accepted and not blocked.
  4. Other channelsPublish an email address, message form or chat option for callers who cannot use voice.
  5. Extra time on requestA key that extends timeouts for callers who need longer.

Relay services and assistive technology

Many deaf, hard-of-hearing and speech-impaired callers use relay services, where an operator or software passes the call between text and voice. Calls through these services may be slower, have a different sound, and include a short delay before the caller can respond. Menus that time out quickly, or systems that block calls from unfamiliar numbers, can lock these callers out.

Callers who need adjustments often have to explain themselves repeatedly. Where your records allow it and the customer agrees, note a preference such as "needs extra time" or "uses relay service" so agents see it at the start of the next call. Handle such notes with care, because they can be sensitive personal information, and keep them to what you need. See Vulnerable Customers on the Phone and Personal Information on Calls.

Test with real people

You cannot judge accessibility from your own seat. Invite callers with different needs to try common tasks, and pay them for their time. Observe where they hesitate, mishear or give up, and ask what they would change. Include both disability groups and ordinary users in noisy places. Repeat the exercise after major changes. A broader test routine is in Testing an IVR Before Launch.

Accessibility review for your menu

  • Menu has no more than four or five options at each level
  • Prompts are short, plain and in the same wording every time
  • Silence timeouts are generous and the menu repeats on request
  • Callers can reach a person from every level
  • Both keys and speech are accepted where speech is offered
  • Relay service calls are not blocked or timed out
  • An alternative to voice exists, such as email or a message form
  • The menu has been tested with people who have different needs

Barriers that appear again and again

Each of these is easy to fix once spotted. The hard part is noticing them, which is why testing with real callers and reviewing complaints matter. A short monthly review of calls where the caller asked for a person or hung up early often points straight to the barrier.

Accessibility when using Call

In Call, the pieces that help most are the ones you configure: a clear option that leads to a general queue staffed by people, voicemail and callback requests for when nobody is free, and ring times on lines so a caller who asks for a person is not cut off too quickly. Call-blocking rules should be checked so they do not catch legitimate callers, and the monitoring or recording notice can be tuned per line so callers know what to expect. Where an AI agent answers, keep a way to reach a person and test how it copes with slow or unclear speech. Setting Up IVR and Business Hours in Call covers the building blocks.

Frequently asked questions

What is the single most important accessibility feature in an IVR?

A clear, early route to a person. Whatever the menu looks like, a caller who cannot use it should be able to reach someone or leave a message.

How long should the menu wait for input?

Longer than you think. Several seconds of silence after the last option is a common minimum, and it helps to repeat the menu once before taking another action.

Should I avoid speech recognition for accessibility?

Not necessarily, but do not rely on it alone. Some callers are not understood by speech systems, so keys and a person should always be available.

Can relay service calls reach my menu?

They should, if your phone system and any call-blocking rules allow them. Check settings and test with a relay service, and make sure agents know how to handle such calls.

Do I need to record special prompts for accessibility?

Usually not. Shorter, clearer versions of your normal prompts help everyone. Some businesses add a key for extra time or for a slower repeat.

How do I know whether my menu is accessible?

Test it with people who have different needs and listen to their feedback. A checklist is a start, but real users find the issues a checklist misses.

Give every caller a clear route to a person in Call

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

Related guides