What Quebec French Language Rules Mean for Marketing Automation Workflows

Set the language state before the trigger fires

The Charter of the French Language governs commercial communications to Quebec recipients, and Bill 96 amended it in 2022. Since the rules can reach businesses operating elsewhere, treat Quebec targeting and a contact's selected language as separate workflow inputs, rather than assuming one establishes the other.

A journey may pass through email, SMS, push notifications, and landing pages. Each step needs its own French version, not merely the initial message. Teams designing marketing automation should make language one of the fields evaluated with each trigger, then confirm the same route reaches every downstream message.

The OQLF oversees language questions, while federal anti-spam and privacy duties remain separate. Bill 96 widened the Charter's reach to commercial advertising, websites, and some automated messages. The workflow must therefore pair language routing with Canadian campaign requirements and the federal CASL framework.

Route contacts through a language branch

Use a language branch to select a message version from the contact's language field when a workflow trigger fires. Do not treat a postal address as proof of preference; a workflow audit can show where routing is absent or disconnected from later steps.

A fr-CA value can route the French email first and leave the English version one click away. An en-CA value can lead to a bilingual message with French first and both blocks at the same size. Keep the selected value explicit, so the route reflects recorded preference rather than an assumption.

Keep both language templates versioned together, and revisit the route whenever copy or sequence logic changes. A preference center can capture the contact's language preference, while the planned branch should be compared with the version that actually went live. Do not let the language value replace the separate permission record for sending.

Match prominence and disclosures in every version

Equal prominence is the working check for automated email, SMS, push, and landing-page content: French should be no less prominent or accessible than English. Where the Charter calls for markedly predominant French, that is a higher test, defined here by twice the area or twice the character size.

A Quebec commercial message also needs the sender's legal name, a physical mailing address, a contact method, and a working unsubscribe mechanism, with required information available in French and English. Keep these disclosures with the selected language version and connect the workflow to consent workflow checks, rather than relying on campaign-level review.

Federal CASL still calls for consent, sender identification, and an effective unsubscribe path; PIPEDA guidance addresses consent and records for personal information. An English-only send does not become acceptable through recipient silence, so test the French-facing experience before release and keep the French unsubscribe mechanism working.

Preserve evidence alongside the live messages

Preserve evidence at each send, not only a generic statement that the campaign had a French version. Store the live language version, send date, recipient segment, and the language value used to choose the route so a later review can connect each message with the decision that selected it.

If the contact selected a preference, retain that choice beside the consent record authorizing the send. Keep language evidence distinct from privacy evidence, but link them to the same contact and message. A CRM strategy that treats language as a lone checkbox will not show which version was sent or why.

For each Quebec workflow, retain:

The OQLF may request evidence during an inquiry, and federal privacy rules also make consent records relevant. Quebec's Law 25 and the Commission d'accès à l'information address personal information collected from Quebec residents. Keep privacy records beside language records, with each record connected to the contact, message version, and send evidence.

Test the full route before release

Before release, run the whole branch from trigger to unsubscribe rather than checking only the opening email.

Confirm every step has a French version, the selected language state reaches the intended route, and the French unsubscribe link works. Put the checks into release sign-off so they are completed before the sequence goes live.

The OQLF may issue a correction notice, while organizations with 25 or more employees must register and obtain a francization certificate, also required for eligibility for Quebec government contracts and subsidies; keep this organizational status separate from message-level workflow checks.

A complaint or an English-only send can prompt scrutiny, so preserve the path from selected field through delivered version and tested unsubscribe. Repeat the release checks whenever sequence logic, language values, or copy changes, keeping paired templates and evidence synchronized rather than repairing a missed language route after launch.