Running an AI receptionist in French and English on one number

One number, two languages, no menu

Many Canadian businesses have solved the language question with a menu: press 1 for English, appuyez sur le 2 pour le français. It works, but it adds a step before the caller has said a word, and it is a poor fit for an AI receptionist whose whole point is that the caller speaks naturally.

The better pattern is a short bilingual greeting — the business name, then one sentence in each language inviting the caller to speak — followed by language detection on the caller’s first reply. If the caller answers in French, the rest of the call is in French. If they answer in English, the rest is in English. If the caller switches mid-call, the receptionist follows.

Order matters and is a business decision. A firm in Gatineau may lead with French; a firm in Mississauga with a French-speaking client base may lead with English and follow with French. Whichever comes first should be brief, so that the caller who wants the second language is not waiting through a paragraph.

Write two scripts, not one translation

The single most common mistake in bilingual setups is writing the English script, translating it, and calling it done. The result is French that is grammatically correct and sounds like a form letter. Callers notice, and the impression is that the French line is the second-class one.

Write the French script as a French-speaking receptionist would actually talk to a customer in your industry. That means using the terms customers use — “prendre rendez-vous”, “un dépanneur”, “une soumission” — rather than literal equivalents, choosing the level of formality your business already uses with clients, and handling numbers, dates and addresses the way they are spoken in Canadian French.

The same goes for the confirmations. “Je vous confirme donc jeudi le 12 à 14 h 30 avec Nathalie” is not a translation of the English read-back; it is what a person would say. Have someone who serves French-speaking customers every day review the script before it goes live, and have them listen to a recorded test call.

Escalation has to be language-aware

A receptionist that handles the call beautifully in French and then transfers the caller to someone who cannot speak it has failed at the moment that mattered most. Escalation rules for a bilingual receptionist carry the language along with the call, and the destinations differ by language.

• Maintain two destination lists — French-capable staff and English-capable staff — and let the receptionist pick the ring group or extension that matches the caller’s language.
• Where the business has only one bilingual person, route French escalations to them first and set a clear fallback: a message with transcript rather than a transfer to someone who cannot continue the conversation.
• Include the language in the whisper announcement before the transfer connects: “French caller, Marie, asking about an invoice”, so the person answering starts in the right language.
• Make the after-hours path bilingual too. An on-call technician who only speaks English should receive a transcript already summarized in English, with the caller’s original-language recording attached.
• Test both paths at different hours. The French path is the one most likely to have a gap, because it usually has fewer people on it.

Transcripts and messages your team can act on

Every call the receptionist handles produces a transcript and, where it took a message, a structured summary. For a bilingual line, both should be labelled with the language of the call, and the summary should be available in the language of the person who will read it.

That second point is easy to overlook. A French transcript delivered to an English-only dispatcher is a delay, not a message. The practical setup is a summary in the reader’s working language — name, number, reason, urgency — with the original transcript attached for anyone who wants the caller’s exact words. The receptionist should never paraphrase a caller’s meaning into the other language without keeping the original available.

Routing rules can also use the language label. A French message about billing can go to a French-speaking accounts contact; an English message about the same topic to a different one. Where the business has a shared inbox, the label lets the right person pick up the right message without opening all of them.

Details that make the French side sound right

A few small things decide whether French-speaking callers feel the line was built for them or bolted on. Time is spoken as “14 h 30”, not “deux heures et demie de l’après-midi”, in a business context. Dates are day-month. Phone numbers are read in pairs. Postal codes are read letter by letter with French letter names. Street types — rue, boulevard, chemin — come before the name.

Names and titles matter too. The receptionist should pronounce staff names as the staff do, which may mean recording a name list, and should use “madame” and “monsieur” or first names consistently with what the business does in person. If your salon calls clients by their first name, the receptionist should too, in both languages.

Finally, decide how the receptionist refers to itself. In French, “l’assistante virtuelle de la clinique” is clear; a made-up name is optional and, if used, should be the same in both languages.

Testing before going live

Test the bilingual receptionist with real speakers of each language, not with one person switching between the two. Have them call at different times, ask for the same things a customer would, and try the awkward cases: starting in one language and switching, using English words inside a French sentence, giving an address with a mixed-language street name.

Record the test calls and review them with the staff who will receive the escalations. The gaps that surface — a term the receptionist misheard, a transfer that landed on an English-only phone at 6 p.m. — are cheap to fix on a test number and expensive to discover on a live one.