Running a business line in both English and Quebec French is not a matter of recording a second greeting. The call itself is the part almost everyone gets right. The chain that follows it, the confirmation, the reminder, the invoice and the person who eventually phones back, is a set of questions worth putting to any provider rather than promises to take on faith, and it is where most setups quietly give up. We answer business calls in English and Quebec French around the clock, and this is what we have learned about the rest of that chain.
Bilingual is not a translated greeting
The common version of bilingual service is a menu. Press one for English, press two for French. It sounds bilingual and it fails for a plain reason: a menu asks the caller to make a decision before anyone has listened to them. People with an urgent problem do not want to choose a language, they want to describe a leak. And a menu only covers the doorway. Behind it, the confirmation text is in English, the reminder is in English, the invoice is in English, and the callback comes from whoever is free rather than whoever speaks the right language.
What a caller actually experiences as bilingual is much simpler. They speak, and the answer comes back in their language without them having to ask. Then everything downstream matches. That second half is where most businesses quietly give up, because keeping two languages consistent across four channels is genuinely hard when a person is doing it by hand and impossible when nobody owns it.
There is a competitive angle here worth naming plainly. A lot of software sold into this market treats French as a translation project that will happen later. If your front office genuinely works in French, you are not competing on features. You are competing on being usable, which is a much shorter argument.
What a Quebec caller is actually listening for
Quebec French is not France French with a different accent, and callers hear the difference in under a sentence. The vocabulary is the giveaway. It is a courriel, not an e-mail. It is a texto. You take a rendez-vous. A contractor sends a soumission, not a devis. Nobody says "bonjour, comment puis-je vous assister" out loud in Trois-Rivières.
Register matters just as much. Quebec business French is warm and direct at the same time. It moves to vous with a stranger, drops the corporate padding, and is comfortable being brief. An assistant that sounds like a translated press release makes people suspicious, because they have all heard that voice before and it usually belonged to a call centre a long way away.
Then there is the mixing. Real Quebec callers switch languages inside a single sentence, especially around technical words and street names. A line that can only handle one language per call is going to mishear the important half of a sentence about a boulevard, an intersection or a part number. Automatic detection has to work mid-conversation, not just at hello. Our page on bilingual AI reception in Canada covers how that switching behaves in practice.
The switch has to survive the hang-up
Here is the test to run on any bilingual claim, ours included. A caller phones in French, books an appointment, and hangs up. What language is the confirmation text in? What language is the reminder two days later? What language is the invoice? What language is the email that goes out when they did not book?
If the answer is "English, because that is what the system defaults to", the business is not bilingual. It is bilingual for the length of one phone call. Worth being blunt here: this is not automatic anywhere, ours included. Treating a caller's language as a fact about the person rather than about one call is a discipline rather than a checkbox: somebody has to decide it, set it up, and then actually check the messages that go out. What we will state without any hedging is the call itself. We answer in the language the caller uses, we switch when they switch, and when we ring a customer back, we ring them back in the language they used.
That last point is the one owners underestimate. Calling a customer back in the language they used is a small courtesy that people remember for years, and it is exactly the kind of thing that gets lost when the return call is placed by whoever happened to be free.
What Quebec customers expect now
Two expectations have hardened over the last few years, and both are worth designing around rather than arguing with.
The first is French by default, not French on request. Being served in French without asking is the baseline in most of the province, and having to ask for it registers as friction even with people who speak perfect English. A greeting that opens in French and moves to English the moment the caller does is not a political statement. It is just good service.
The second is transparency about what happens to personal information. Quebec's privacy reform, the one everybody refers to as Law 25, is why callers here are now used to being told what a business collects and to being asked before it is used. That is background context rather than legal advice, and every business should get its own. What it means practically for a phone line is that people are less surprised by a clear notice and more suspicious of silence. We take the same view about the AI itself: callers are told plainly that they are speaking with an automated assistant, and reaching a person is never a puzzle. Honest disclosure is not a posture for us, it is the reason people keep talking instead of hanging up.
How we set up a bilingual line
The practical version, for an owner who wants to know what the work looks like:
- One number, both languages. No menu, and no separate French line to maintain and then forget.
- A greeting written twice, not translated once. The French greeting is written in Quebec French from scratch rather than run through a translator from the English one.
- Your vocabulary, both ways. Service names, neighbourhoods, and the words your customers actually use for what you sell. This is where generic translation fails hardest.
- Wording decided in both languages while you are setting up. Write what your customers will read in each language yourself, rather than leaving either version to whatever default a system happens to ship with.
- An escalation path in both languages. Deciding in advance who takes a French call that needs a person, and what happens when that person is not there.
None of this is exotic. It is work that has to be done once, deliberately, by someone who cares whether the French sounds like French.
Beyond English and Quebec French, our receptionist also speaks thirty or more other languages with automatic detection, which matters more than owners expect in Montreal, where a caller's third language is sometimes the one they are most comfortable describing a problem in. If you want the local version of all this, our page for a virtual receptionist in Montreal is written in French, and the plan and usage details live on our pricing page. We are onboarding businesses in small waves, and a bilingual line is exactly the kind of setup that benefits from that pace.