Try Omnifox free 7 days free. No credit card required.
Guides

Writing Chatbot Scripts in English and French That Do Not Annoy People

Scripting a bot for a bilingual Canadian audience: greetings, language detection, fallback answers, escalation wording and the phrases to avoid entirely.

August 17, 2026
In this article

    Writing Chatbot Scripts in English and French That Do Not Annoy People

    The fastest way to make a Canadian customer hate your website is a chatbot that opens with "Hi! I'm Ava, your virtual assistant! 😊 How can I help you today?", fails to understand three questions in a row, and then answers a French enquiry in the kind of French that reads as though it went through a machine on the way. The customer leaves. You have automated the loss of a lead.

    Writing chatbot scripts in English and French is a conversation design problem, not a technology problem. The model behind the bot matters far less than the wording you put in front of people: what it says first, how it establishes language, what it does when it does not know, and how it hands over. Canada makes this harder in one specific way — a meaningful share of your customers expect service in French, Quebec has its own expectations for French in commercial communications, and a bot that treats French as a translated afterthought is worse than an English-only bot that admits it.

    The opening message sets the contract

    Your first message is a promise about what this thing can do. Break it and everything afterwards feels like a con. Three rules for the opener:

    1. Say it is a bot, plainly. Customers are far more forgiving of a bot that admitted it than one they caught out.
    2. Say what it can actually do, in three or four concrete options — not "how can I help you today?", which invites questions it cannot answer.
    3. Say how to reach a human, in the first message, before anyone gets frustrated enough to ask.

    Better than "How can I help you today?": "Hi — this is the Lakeview Clinic assistant. I can book, move or cancel appointments, confirm our hours and location, and answer questions about what we treat. For anything else, type 'human' and I'll pass you to our front desk (open weekdays 8:00 a.m.–5:00 p.m. Eastern)."

    That version is longer and converts better, because the customer now knows exactly what to type.

    Handle language in the first turn

    Do not guess and do not wait. Establish language before anything else: a customer who has typed a question in French and received an English menu has already formed an opinion.

    Two workable approaches. Ask directly — one short bilingual line and two buttons, the most reliable option:

    "Bonjour / Hi! Continuons en français ou en anglais? / Shall we continue in French or English?"

    Or detect and confirm — read the language of the first message, respond in it, and offer a switch. Never infer silently from the page language: a francophone customer reading your English page is common.

    Whichever you use, three follow-through rules matter more than the choice: store the preference on the contact; make switching possible at any point, not only at the start; and route to a human who matches the language, because handing a French conversation to an English-only agent undoes everything the bot did well.

    Write French, do not translate English

    This is where most bilingual bots fall down, and Quebec customers notice within one sentence. The problem is not vocabulary but structure. English service writing is chirpy, short and imperative; French commercial writing is more measured, and a literal rendering of "Hey! Got it! Let me grab that for you!" lands as childish or bizarre. Two scripts written by someone who works in each language will always beat one script translated.

    Specific things to get right:

    • Vouvoiement. Use vous with customers unless your brand has a deliberate reason not to. Defaulting to tu because the English is casual is the most common error.
    • Real terminology. Use the French terms your Quebec customers actually use, not dictionary equivalents. A soumission is a quote; a devis may read as imported.
    • Accents and typography. Missing accents look careless, and ARRÊT without the circumflex in an opt-out instruction looks worse.
    • Bilingual footers must be genuinely bilingual. Sender identification and unsubscribe wording appearing only in English inside a French message gets noticed.
    • Have a francophone read it aloud before launch. Anything that makes them pause gets rewritten.

    Quebec has its own expectations for French in commercial communications, and consumer-facing businesses there should treat the French version as primary rather than a variant. This is general information rather than legal advice — confirm your obligations with your own counsel. The detail is in French language expectations for commercial messages in Quebec, and paired wording in bilingual message templates in English and French.

    Fallbacks: what the bot says when it does not know

    Every bot will fail to understand. What separates a tolerable bot from an infuriating one is entirely the failure behaviour. Never fail twice in the same way — the second "Sorry, I didn't get that" is where customers give up. Escalate the fallback each time:

    Attempt Bot behaviour Wording
    First miss Reframe, offer options "I'm not sure I follow. Is it about booking, hours, or something else?"
    Second miss Offer a human immediately "Let me get someone who can help properly — I'm passing you to our front desk."
    Out of hours miss Capture and promise "Our team is offline until 8:00 a.m. Eastern. Leave your number and they'll reply first thing."
    Sensitive topic detected Escalate without attempting "This should go to a person. I'm passing you across now."
    Language mismatch Switch and continue "Je peux continuer en français. Que puis-je faire pour vous?"

    The one behaviour to eliminate entirely is the loop — the bot returning to the same menu after a failed answer. Customers read that as being trapped, and it is the most common complaint about business chatbots.

    Escalation wording that does not leave people stuck

    Handing over to a human is not a defeat — it is the feature customers care most about. Confirm the handover is happening rather than that it might ("I'm passing you to Dana now" beats "I'll try to connect you"), give the reopening time in the customer's time zone if nobody is online, and always carry the transcript across. Asking a customer to repeat themselves after a handover is the moment goodwill collapses. When the wait is long, offer to text them back instead.

    Ground the bot in your own content

    A bot that improvises will eventually invent something — a policy, a price, a service you do not offer — and a customer will hold you to it. The controllable version answers only from your documented content: service pages, hours, policies, approved price ranges and a curated question bank. When something falls outside that, it says it does not know and escalates. That constraint is precisely what makes the bot trustworthy. Review the "I don't know" log weekly — those questions are your content roadmap. What to automate and what to leave to people is set out in AI in customer service: what to automate in Canada.

    Omnifox's chatbots and AI agents run inside the same shared inbox as SMS, email, web chat, WhatsApp and social DMs, so the bot's transcript, the human reply and the follow-up text all sit on one contact record.

    Sample turns in both languages

    Greeting (FR): "Bonjour — voici l'assistant de la Clinique Lakeview. Je peux prendre, modifier ou annuler un rendez-vous et répondre à vos questions sur nos heures et nos services. Écrivez « conseiller » à tout moment pour parler à une personne."

    Booking confirmation (FR): "C'est confirmé : mardi 14 mai à 10 h 30 avec la Dre Chen, 220, chemin Lakeview. Nous vous enverrons un rappel la veille. Pour modifier, répondez simplement ici."

    Escalation (FR): "Cela dépasse ce que je peux répondre correctement. Je vous transfère à notre réception — elle voit tout notre échange, vous n'aurez rien à répéter."

    The phrases that make bots infuriating

    Delete these on sight:

    • "I'm sorry, I didn't quite catch that" — twice in a row.
    • "Please rephrase your question" — the customer's phrasing was fine; the bot is the problem.
    • "Is there anything else I can help you with?" after failing to help with the first thing.
    • "Unfortunately I am unable to assist with that" with no offer of a human.
    • Excessive exclamation marks and emoji in a service context, especially in French.
    • Fake names presented as real people. "Ava" is fine as an assistant; "Ava from support" is not.

    A QA script to run before launch

    Run every item in both languages, on a phone and a desktop.

    1. Send the ideal question and confirm the answer is correct and current.
    2. Send a vague question ("hi, question") and confirm the bot reframes rather than loops.
    3. Send gibberish twice and confirm it escalates on the second miss, not the fifth.
    4. Ask for a human explicitly and confirm the handover carries the transcript.
    5. Test outside business hours and confirm the message states the real reopening time.
    6. Start in English, switch to French mid-conversation, confirm it stays switched.
    7. Ask about something you do not offer, and about pricing, and confirm it declines rather than invents.
    8. Have a francophone colleague read every French string aloud and flag anything that sounds translated.

    Frequently asked questions

    Should a chatbot say it is a bot?

    Yes, in the first message. Customers are far more tolerant of limitations when the bot was upfront, and far less tolerant when they work out mid-conversation that the "person" helping them was software. State it plainly, list what it can do, and give the route to a human immediately.

    How should a bilingual chatbot handle French?

    Establish the language in the first turn, either by asking with a short bilingual line or by detecting the language of the first message and confirming. Store the preference on the contact, allow switching at any point, route to a French-capable human on escalation, and write the French script natively rather than translating.

    What should a chatbot do when it does not understand?

    Reframe once with concrete options, then escalate to a human on the second miss. Never repeat the same apology, and never return the customer to the opening menu after a failure — that loop is the most common reason people abandon a chat.

    How do we stop a chatbot from inventing answers?

    Ground it in your documented content — service pages, policies, hours, approved price ranges and a curated question bank — and configure it to say it does not know and escalate when a question falls outside that. Then review the unanswered-question log weekly and turn recurring gaps into new content.

    Getting your bilingual bot right

    Writing chatbot scripts in English and French comes down to honesty and follow-through: say what the bot is and what it can do, settle the language immediately, fail gracefully, escalate early, and write French a francophone customer would recognize as their own.

    Omnifox lets you build chatbots and AI agents in both languages inside the same shared inbox as your web chat, SMS, email, WhatsApp and social channels, with escalation to a human who inherits the transcript. Start free at omnifox.io/register or compare the plans and pricing. For the wider picture, read the complete guide to AI chatbots for Canadian businesses and the playbook in bilingual customer service in English and French.

    Ready to try it in your business?

    Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.

    7 days free. No credit card required.

    Comments (0)

    No comments yet. Be the first to share your thoughts.

    Leave a comment

    Your email is never published. Comments are moderated before appearing.

    Markdown supported. HTML is stripped.

    Read more

    Message us on WhatsApp