The Office québécois de la langue française logged 10,371 language complaints in 2024-2025, up 14% in a single year and roughly 140% over five years (OQLF Annual Report 2024-2025). If you serve Quebec customers, one AI agent can detect whether someone writes in English or French and reply natively in that language, 24/7, without you hiring and scheduling two bilingual desks. This guide covers where French is actually required, how a single AI "brain" handles both languages, the tone and quality bar Quebec customers expect, and the routing mistakes that turn a service slip into a legal one.
Where is French legally required for a small business in Canada?
In Quebec, any business with five or more employees must be able to serve customers in French, and if a customer writes to you in French you must reply in French. That requirement comes from the Charter of the French Language, amended by Bill 96 (Law 14, 2022), and it is enforced by the Office québécois de la langue française. For most small businesses outside government — home services, retail, local trades — this Quebec law, not federal bilingualism, is the one that actually binds you.
The obligation goes beyond a greeting. Commercial documents, websites, social-media pages, order forms, receipts, and warranties must be available in French, and voicemail or telemarketing greetings used in Quebec must include a French version (Éducaloi, 2026). Crucially for any chat tool: if a customer messages you in French, you reply in French; if they write in another language, you may reply in that language.
Federal rules are narrower than people assume. The Official Languages Act (1969) binds federal institutions, not private small businesses. A newer statute, the Use of French in Federally Regulated Private Businesses Act, has been enacted but is not yet in force, and even when proclaimed it will cover telecoms, banks, and interprovincial transport — not a local HVAC shop or boutique. The penalties for getting the Quebec rules wrong are real: OQLF fines run $3,000 to $30,000 per day for a first offence, doubled for a second and tripled after that (Éducaloi, 2026).
One more distinction worth holding in your head: the language law is not the privacy law. Bill 96 governs the language of service through the OQLF, while Quebec's Law 25 governs how you handle personal data through a different regulator, the Commission d'accès à l'information. A chat transcript contains personal information, so any AI customer-service tool touches both regimes at once — but they are two separate checklists with two separate enforcers. This article is about the language side. Treat the data-residency, consent, and privacy-impact-assessment questions as their own project.
| Requirement | Who it applies to | Legal basis | Enforcer |
|---|---|---|---|
| Serve customers in French | Businesses with 5+ employees in Quebec | Charter of the French Language (Bill 96, 2022) | OQLF |
| Reply in French when the customer writes in French (incl. chat/social) | Any business serving Quebec consumers | Charter of the French Language | OQLF |
| French website + invoices, order forms, receipts | Businesses with a Quebec establishment | Charter of the French Language (Bill 96) | OQLF |
| Voicemail/telemarketing greetings include French | Businesses operating in Quebec | Charter of the French Language | OQLF |
| French service from federally regulated businesses | Telecoms, banks, interprovincial transport | Use of French in Federally Regulated Private Businesses Act (enacted, not yet in force) | Federal (Canadian Heritage) |
| Federal institutions serve the public in EN/FR | Federal government bodies only | Official Languages Act (1969) | Commissioner of Official Languages |
How can one AI agent serve both English and French customers?
A single AI agent detects the customer's language from their first message and responds natively in English or French, holding one knowledge base, one set of business rules, and one escalation logic underneath. Instead of staffing two language desks, you run one "brain" that simply renders the conversation in the customer's language. That is the entire efficiency argument, and it matters because bilingual front-line labour is scarce, expensive, and hard to schedule around evenings and weekends.
The demand is not theoretical. In 2024-2025, 40% of all OQLF complaints concerned the right to be served in French, up from 25% five years earlier (OQLF Annual Report 2024-2025). Meanwhile only 18.0% of Canadians — about 6.58 million people — could hold a conversation in both official languages in 2021, rising to 46.4% inside Quebec (Statistics Canada, 2021 Census). Bilingual staff are a genuinely thin slice of the labour pool, so a contractor who relies on humans alone often ends up routing French callers to a unilingual English voicemail. That is now the single largest complaint category at the OQLF.
The one-brain model is most powerful outside Quebec's bilingual hubs, where finding bilingual staff is hardest but Francophone minority communities still expect French service. Omago, an AI agent platform that helps SMEs automate customer conversations across WhatsApp, Telegram, and web chat, is one tool built for exactly this: detect language, answer in kind, and route to a human when the situation calls for judgment. The key is that the agent does not just translate a script — it serves from the same underlying logic in either language, so a French customer and an English customer get the same accurate answer, not a watered-down version.
If you are weighing this against simply hiring, it is worth reading how to think about AI versus hiring and when to automate before you commit to either path.
What quality of French do Quebec customers and the OQLF expect?
The French an AI agent produces must be of a quality "at least equivalent" to the English version, and the OQLF explicitly cautions against relying on raw machine translation for commercial use because the output may not meet its bar. This is the part most businesses underestimate. A generic model that spits out literal or France-centric French reads as foreign to a Quebec customer, and the regulator actively monitors the quality of service French, not just whether French exists.
Quebec French is its own register. Vocabulary and idiom differ from France: Quebec uses "magasiner" for shopping and "stationnement" for parking, and audiences notice and reward authentically Québécois phrasing. Since 1990 the OQLF has even run its Mérites du français awards, including a "Langue de commerce" category that rewards businesses for the will to serve clients in French and the quality of the means deployed to do it. The signal is clear: presence is the floor, quality is the expectation.
Why does this bar exist in the first place? Because the regulator treats service French as a measurable thing, not a checkbox. The 40% of complaints now tied to language of service — up from 25% five years earlier — are people reporting that they could not get served in real French, not just that a sign was missing (OQLF Annual Report 2024-2025). A chatbot that answers in stilted or France-flavoured French is exactly the kind of experience that generates those complaints. Quality is the compliance surface, and for an AI agent it is also the difference between a customer who trusts you and one who switches to a competitor mid-conversation.
Then there is register — the tu/vous question. Quebec is markedly more open to tutoiement than France, even in some commercial and first-contact settings, but vouvoiement remains the safe default for service interactions, older customers, and formal trades. A well-configured AI agent should:
- Default to "vous" on first contact and hold a professional service tone.
- Use Quebec vocabulary and idiom rather than France-centric phrasing.
- Keep French output at parity with English — same detail, same accuracy, never an abbreviated afterthought.
- Let a human reviewer spot-check transcripts early so you catch tone drift before customers do.
If you are building the underlying content the agent draws from, our guide on how to build an AI knowledge base walks through structuring it so both languages stay accurate.
What language-routing mistakes break bilingual AI service?
The single most damaging mistake is serving a French customer in English — it is now the largest OQLF complaint category, which makes it a legal risk and not just a service lapse. Most bilingual AI failures trace back to a handful of predictable bugs, and each one is fixable with the right configuration.
Here are the classic failure modes to design against:
- Wrong-language replies. Answering a French message in English. This is the legal landmine, and the one regulators hear about most.
- Detection errors on short or mixed messages. A one-word "Oui" or a code-switched "Bonjour, can you help?" trips up agents that guess language from too little text.
- "Sticky language" lock-in. The agent locks to the first language it detected and refuses to switch when the customer switches mid-conversation.
- Cross-channel inconsistency. French on web chat, then an English confirmation by text — the same customer, two languages, one annoyed person.
The fix is straightforward in principle: run per-message language detection rather than locking once, offer an explicit and easy language toggle, and default to French for any Quebec-based contact unless the customer clearly opts into English. Designing these branches deliberately is its own discipline; our walkthrough on how to design conversation flows covers the logic of detection, fallback, and escalation.
Be honest about what AI cannot do here. Language detection is probabilistic, so a small number of ambiguous messages will be misread, which is exactly why a clear toggle and a low-confidence escalation path matter. The goal is not a perfect machine — it is a system that catches its own uncertainty and hands off gracefully instead of plowing ahead in the wrong language.
When should the AI agent hand off to a human?
Automate the repetitive, high-volume, low-judgment work, and route anything that needs human authority or carries liability to a person. The split is what keeps bilingual automation both useful and safe. An AI agent should comfortably handle FAQs, after-hours lead capture and qualification, appointment booking and rescheduling, quote-request intake, and the language detection itself. It should escalate genuine emergencies, complex quotes that need a site visit, upset or vulnerable customers, and anything requiring professional or safety judgment.
This matters across both languages equally. A French-speaking customer with a billing dispute deserves the same human escalation an English-speaking one would get — the agent's job is to recognize the boundary, not to improvise past it. Done right, the AI takes actions inside its lane (capturing the lead, booking the slot, sending the intake form) and flags the edge cases for a human, rather than answering everything itself.
The handoff itself should be bilingual too. When the agent escalates, it should pass the full transcript and the detected language to the human picking up, so a French customer is not suddenly greeted in English by the next person in the chain. This is where the "one brain" model pays off: the language context travels with the conversation instead of being re-guessed at every step. For trades and home services in particular, fast handoff matters — leads contacted within five minutes are 21 times more likely to qualify than those reached at 30 minutes (MIT / InsideSales, 2007), and once a caller hits voicemail, 86% hang up without leaving a message (Invoca / CallJolt, 2025). An agent that captures and qualifies a French-speaking after-hours lead, then routes a clean bilingual handoff to the morning crew, is the difference between booking that job and losing it to the next contractor on the list.
| Automate with the AI agent | Route to a human |
|---|---|
| FAQs: hours, service area, pricing ranges | Genuine emergencies needing immediate dispatch |
| After-hours lead capture and qualification | Complex quotes requiring a site visit |
| Appointment booking and rescheduling | Upset, distressed, or vulnerable customers |
| Quote-request intake forms | Professional or safety judgment (e.g., gas advice) |
| Language detection and EN/FR response | Negotiation or high-value custom proposals |
| Confirmations and reminders (consent-compliant) | Edge cases the AI flags as low-confidence |
One practical Canadian note: if you follow up by text or messaging app, Canada's anti-spam law (CASL) requires consent and an easy way to opt out, so build "STOP" handling into any reminder flow from day one.
Why is a bilingual AI agent cheaper than hiring two language desks?
A single AI agent runs one knowledge base and one set of rules in two languages, so you avoid paying, training, and scheduling separate English and French staff for coverage you may only need at the margins. The labour math is unforgiving: bilingual workers are roughly one in five Canadians nationally (18.0% in 2021, per Statistics Canada), and 24/7 coverage in both languages with humans means multiple hires and shift premiums. An AI agent gives you round-the-clock bilingual coverage at a flat software cost.
It also fixes consistency. Two human desks drift — different answers, different tone, different French quality on a bad day. One brain renders the same vetted answer in either language, which is precisely the parity the OQLF expects. And because only one in five Canadian SMEs has reached high digital maturity while more than half sit at low levels (BDC, 2023), simply automating the bilingual front desk is a real competitive edge in most local markets.
On pricing, transparency helps: a tool like Omago starts free for up to 50 messages, with paid tiers at Core $49, Plus $99, and Max $369 per month (USD), and annual billing saves two months. WhatsApp and Telegram channels start at the Plus tier, while web chat is available throughout. For a small home-services or retail business in Quebec, that is a fraction of one bilingual hire — and it answers at 11 p.m. in either language without overtime. For the full picture on what these tools actually cost to run, see the real cost of AI agents for small business.
Frequently Asked Questions
Do I have to serve customers in French in Quebec?
If your business has five or more employees and operates in Quebec, yes — you must be able to serve customers in French under the Charter of the French Language as amended by Bill 96. And regardless of size, if a customer writes to you in French, you must reply in French. Enforcement sits with the OQLF, with fines of $3,000 to $30,000 per day for a first offence (Éducaloi, 2026).
Can an AI chatbot meet Quebec's French-language requirements?
It can help with the language-of-service requirement if it detects French and replies natively in quality French, but configuration matters. The OQLF expects French "at least equivalent" to the English version and cautions against raw machine translation, so the agent must use authentic Quebec phrasing and maintain parity, not produce a literal or abbreviated translation.
Should a Quebec business use "tu" or "vous" in customer service?
Default to "vous" for first contact, service interactions, older customers, and formal trades. Quebec is more open to "tu" (tutoiement) than France, but "vous" remains the safe professional default. A well-configured AI agent should start with "vous" and a professional tone.
Is bilingual French service required outside Quebec?
For most private small businesses, no federal law forces it the way Quebec's Charter does. The federal Official Languages Act binds government institutions, and the Use of French in Federally Regulated Private Businesses Act is enacted but not yet in force and only covers sectors like telecom and banking. That said, Francophone minority communities outside Quebec still expect and value French service.
How does one AI agent handle two languages without confusion?
It uses per-message language detection rather than locking to the first language, offers an explicit language toggle, and draws from one shared knowledge base so answers stay consistent across English and French. To avoid the common "sticky language" bug, it should re-detect each message and switch when the customer switches, escalating low-confidence cases to a human.
Sources: OQLF / Government of Quebec Annual Report 2024-2025 (2025); Éducaloi (2026); Statistics Canada, 2021 Census (2022); BDC (2023).
