IVR Language Selection Menus: Design Tips for Multilingual Callers
How to offer language choices in a phone menu: when to ask, how to word the options, which languages to offer first, and what to do when a caller needs help.
A caller who cannot understand the first thirty seconds of your phone menu will hang up, or press random keys. For businesses with customers who speak different languages, the language selection step is therefore the most important part of the menu: if it fails, nothing after it matters. This guide covers when to ask, how to word the options, and how to avoid the traps that catch most first attempts. If you are new to menus in general, read What Is IVR? first.

Should you ask for a language at all?
Language selection adds a step, and every extra step costs patience. It earns its place only when a meaningful share of callers would otherwise struggle. Before you add it, look at your own evidence: which languages do callers use in chat, email and voicemail, and where do agents currently struggle?
Three ways to handle languages
| Single language | Menu selection | Detect and switch | |
|---|---|---|---|
| How it works | One menu, one language | Caller chooses a language early in the call | The system recognises the language from speech, or from the number dialled |
| Best for | Local businesses with a narrow customer base | Teams with real coverage in a few languages | Voice agents and setups where several languages are handled in the same flow |
| Main risk | Excludes other speakers | Extra step; wrong key presses | Wrong detection; needs a safe fallback |
| Staff need | None | Agents or prompts per language | Depends on the system; test carefully |
For a related decision, see Multilingual Voice AI, which looks at how automated agents cope with several languages.
Designing the language menu
Put it first, and keep it brief
The language choice should be the first thing callers hear after a one-line greeting, because everything later depends on it. Keep the list short. Three or four options is comfortable; beyond that, callers forget the first option before the list ends. If you serve many languages, offer the top two or three and give a way to reach the rest.
Say each option in its own language
A prompt that says "for Spanish, press 2" in English is useless to the person who needs it. Record each option in the language it names: "Para español, oprima el 2." Use native speakers or professional voice talent rather than guessing at the phrasing, and avoid idioms that do not travel.
A simple language-selection flow
- GreetingA short welcome, ideally bilingual if you serve two main languages.
- Language promptEach option spoken in its own language, one key per language.
- DefaultIf the caller presses nothing, continue in your main language after a short pause.
- Language menuThe usual menu, now in the chosen language, with the choice remembered for the rest of the call.
- Way outA route to a person who can help, or a message in the chosen language if nobody is available.
Order, defaults and edge cases
Do not assume the order is neutral. The first language people hear feels like the "main" one. Order options by caller volume, not by alphabet or by what you consider most prestigious. Where two languages are roughly equal, a common approach is to alternate or to offer both within the same greeting.
- No input: continue in your main language rather than looping. Repeating the prompt once is fine; repeating it forever strands people.
- Wrong key: repeat the prompt once, then fall back to the default.
- A language you do not offer: say so briefly in the languages you do have, and offer the nearest alternative, such as an email address or a message.
- Returning callers: if your phone system knows the caller from past contact, you may be able to start in their previous language and let them change it. Handle this carefully, because a wrong guess is worse than asking.
What has to exist behind each option
A language option is a promise. If the caller presses the key for a language, they expect to talk to someone who speaks it, or to hear prompts they understand throughout. Check the whole path:
Before adding a language option
- Prompts for every menu level are recorded or generated in that language
- Hold and queue messages are available in that language
- Voicemail greeting and after-hours message are available in that language
- Agents who speak it are scheduled when the line is open, or a clear alternative exists
- Reports can show how many callers chose each language
- Someone owns updating the prompts when the menu changes
Tone, speed and accessibility
Callers listening in a second language often need slower speech and shorter sentences. Keep prompts plain, avoid abbreviations, and leave a short pause between options so listeners can translate in their head. Our guide to Accessible Phone Menus for Every Caller covers more ways to keep menus usable, and Recording IVR Prompts and Text-to-Speech explains how to produce good audio in each language.
Measure and refine
After launch, look at which languages callers choose, where each group hangs up, and how often they press zero or return to the menu. A language option that few people choose may belong in a sub-menu; one that is chosen often and then abandoned usually has a quality or staffing problem behind it. Review the data monthly in the first quarter, then every season. IVR Analytics explains which measures to track.
Example flows for different situations
The right design depends on how many languages you serve and how the calls are staffed. These hypothetical examples show how the same ideas change shape.
A clinic serving two main languages
A small clinic might greet callers in both languages in a single sentence, then ask them to choose with one key each. Because the choice is only two options, callers decide quickly, and there is no need for a long list. Both options lead to the same menu structure, so staff only maintain one flow translated twice.
A busy support line with several languages
A larger support line might offer its two highest-volume languages by key and add one more option for "other languages". That option can lead to a message in plain language explaining how to reach support by email, or to a callback request that is handled by an interpreter service. The aim is to give every caller a way forward, even if it is not a live conversation.
An after-hours line
After hours there may be nobody to transfer to, but the language step still matters: callers should hear the opening hours and leave a message in a language they understand. Record the closed greeting in each language you offer in the menu, and keep the wording consistent so callers do not feel they have been given a lesser service.
Common mistakes to avoid
- Asking too late. If the language choice comes after two other menus, callers have already struggled.
- Using flags or country names as shorthand. A language is not a country; many people speak languages that do not match their location.
- Mixing languages in a single prompt. A sentence that switches language halfway confuses both audiences.
- Forgetting the details. Opening hours, addresses and spelling of names should be checked in each language, not machine-translated and left.
- Not updating all versions together. When a menu option changes, every language needs the update on the same day.
Language handling in Call
In Call, each phone line has a main language for calls. When an AI agent answers the line, it greets callers in that language, and a caller who speaks another language is answered in theirs. For queues staffed by people, the team decides which languages to offer and builds the routing accordingly, using skills so calls reach agents who can help. The overview in Setting Up IVR and Business Hours in Call shows where these settings live. Because voice AI behaviour can vary by language and line quality, test each language you intend to rely on before launch.
Frequently asked questions
How many languages should an IVR offer?
Offer as many as you can serve well, usually two to four at the first menu. A longer list is harder to remember. Put less common languages behind a further option or an alternative contact route.
Should I use numbers or speech to choose a language?
Keys are simplest and work for everyone, including callers who struggle to be recognised. Speech can be friendlier, but a system that mishears the language is frustrating, so always provide keys as a fallback.
What if the caller chooses a language and nobody speaks it?
Tell them clearly and give a next step: leave a message, request a callback, or use another channel. Avoid silently routing them to an agent who cannot help.
Should the language choice be spoken in English?
Not only. Speak each option in its own language so that the person who needs it can recognise it. A short bilingual greeting before the list also helps.
Can I remember a caller's language for next time?
If your phone system or customer record stores a language preference, you can use it as a starting point and still let the caller change it. Be careful with privacy and make the preference easy to correct.
How do I test a multilingual menu?
Ask native speakers to call and attempt real tasks. Listen for awkward phrasing, wrong accents, mixed-up options and prompts left in the wrong language.