Bilingual call flows: greeting, menu and voicemail design for English and French callers

The one rule: choose once, then stay in that language

The most common bilingual call-flow mistake is a greeting that alternates languages line by line — “Thank you for calling, merci d’avoir appelé, for English press one, pour le français faites le deux, our office hours are, nos heures d’ouverture sont…” — and then continues to alternate through the menu. Callers in both languages hear twice as much as they need and understand half of it.

The better pattern is simple: a short, symmetrical prompt that offers the choice, then a complete experience in the chosen language. Once the caller has pressed one or two, or has said “English” or “français”, everything that follows — the menu, the hold music announcements, the queue position, the voicemail greeting, the transfer announcement — is in that language only.

The choice should be the very first thing the caller hears after the company name, not something buried after a marketing message. A greeting of “3CTel. For English, press one. Pour le service en français, faites le deux.” is complete. Anything the business wants to say about itself can wait until the caller is in their language.

Where the language choice can live

There are three reasonable places to make the language decision, and businesses often use more than one.

• At the front door: the first prompt on the main number offers the choice. Works for any business and any caller. The default when nothing else is known.
• By the number dialled: a business that publishes one number in its French advertising and another in its English advertising can skip the prompt entirely and assume the language from the number. Callers still get a way to switch.
• By caller recognition: a returning customer whose record says French can be greeted in French directly, with the phone system reading the preference from the customer record. This requires a connection to your customer system and a fallback for unknown callers.
• By an AI receptionist: an automated receptionist can greet briefly in both languages and follow whichever language the caller answers in, removing the keypress. It should still offer a way to switch if it guessed wrong.

Build the menu once, record it twice

The structure of the menu — how many options, what they are, where each one goes — should be identical in both languages. If English callers can press three for billing, French callers should also press three for billing. Keeping the structure identical means one diagram, one set of routing rules and one place to change things. Only the recordings differ.

Write the French menu as French, not as a translation of the English one. “Press two for accounts receivable” becomes “Pour la comptabilité, faites le deux,” with the action stated after the destination as French callers expect. Have a native speaker in each language read both scripts aloud before recording; anything that sounds stilted when read will sound worse on the phone.

Record both sets with the same voice quality and the same pace. A crisp English recording followed by a French one made on a laptop microphone tells French callers where they stand. If you use a text-to-speech voice, listen to it in both languages and check how it pronounces your company name and the names of any people it mentions.

Keep the menu short. Four options is comfortable; six is the upper limit before callers lose track. Every option that exists in one language exists in the other, including the option to reach a person.

Routing each branch to people who can answer

The language choice only matters if it changes who answers. Behind each branch, decide which people or teams can handle a call in that language and build ring groups or queues accordingly. A bilingual staff member can sit in both groups; a unilingual one sits in one.

For small teams, the practical shape is often one English queue, one French queue, and a shared bilingual overflow. If the French queue is empty for the moment, the call overflows to a bilingual person rather than to a unilingual English speaker. For larger teams and contact centres, skills-based routing does the same thing more precisely: each agent has a language skill, and the system matches callers to agents who have it.

The transfer announcement is part of this. When a French caller is transferred to a named person, the whisper the staff member hears — “French caller from the billing menu” — tells them which language to pick up in. That small cue avoids the awkward first three seconds where both people guess.

Plan for the mismatch. A French caller who reaches the English branch by mistake, or who is transferred by a colleague to a unilingual person, needs a graceful path back. A standard phrase both teams know — “Un instant, je vous transfère à un collègue qui parle français” — and a known extension for the bilingual group is enough.

Voicemail, messages and after-hours in both languages

Each language branch should end in its own voicemail box or its own message-taking path, so the greeting the caller hears matches the language they chose and the message that arrives is already tagged with the language. A single shared voicemail box with a bilingual greeting works, but it means every message has to be listened to before anyone knows who should return the call.

After-hours rules follow the same logic as the daytime flow. The after-hours greeting states the hours in the caller’s language, offers the same options that exist after hours — leave a message, reach the on-call line, hear the address — and does not assume the caller will understand a bilingual recording read at speed. If an AI receptionist takes after-hours calls, it should detect and keep the language in the same way.

Test the whole path in both languages, from the outside, with someone who did not build it. Dial the number, choose French, go down every branch, leave a voicemail, and confirm the message reaches a person who reads French. Then do it again in English. The flow is done when both walkthroughs feel like the primary experience rather than the secondary one.

Common questions

Two questions come up in most bilingual call-flow projects.