E-commerce
July 1, 2026
"Hello, where is my order? Thank you." "The bot answers in English, I write in French." "Can you help me with my return?" Three tickets where the mix of languages blocks the bot, the agent, or both.
The mixed multilingual e-commerce conversational support covers code-switching, hybrid FR-EN messages, vague language preference, and bilingual handoff. It completes the multilingual chatbot support (#16): here, the customer alternates or mixes languages within the same thread, rather than using an end-to-end translated store.
This guide #891 deploys the MIXLANG-SUP policy, flows ML-1 to ML-8, and the MIXLANG-MAP matrix. Future customer service pair: code-switching bot (#892).
Summary
Why does mixed multilingual content generate tickets?
Expats, cross-border workers, tourists, bilinguals: the customer code-switches without announcing their preferred language. The bot forces a language, the agent replies in FR even though the customer started in EN.
Five typical mixed-language frictions
Code-switching: changes language in the middle of a chat
Hybrid message: FR and EN in the same sentence
Wrong-language bot: English response to a French-speaking customer
Mismatched agent: agent language ≠ customer language
Unclear preference: customer doesn't know which language to choose
DTC retail example
International DTC fashion, 7k mixed-language tickets/month. After MIXLANG-MAP: mixlang_preference_resolution_rate 86%, useless language handoffs -39%.
MIXLANG #891 vs MULTI #16, KB #268, CHATTYP #890 and bot #892
Five international language contents, five distinct angles.
Quick matrix
#891 MIXLANG: manage tickets mixing languages code-switching hybrid
MULTI #16: when to use a multilingual chatbot strategy
CHATTYP #890: FR mistakes synonyms distinct multilingual
CHATMIS #879: misunderstanding distinct subject language
Bot #892: bot follow language change widget
#891 = I mix FR and EN. #16 = do we need a multilingual bot on the store.
Promise #891
Policy MIXLANG-SUP, tree MIXLANG-GATE, 8 macros, detect preference and respond consistently, KPI mixlang_preference_resolution_rate.
Which mixlang_* typologies should be classified?
Action-oriented classifier: code_switch ≠ hybrid_message ≠ bot_wrong_lang.
Eight MIXLANG-MAP typologies
mixlang_code_switch: alternates languages between messages
mixlang_hybrid_message: FR and EN in the same message
mixlang_bot_wrong_lang: bot replies in the wrong language
mixlang_agent_mismatch: agent language ≠ customer language
mixlang_preference_unclear: language preference unknown
mixlang_translate_request: wants translated policy
mixlang_frustration: anger due to language barrier
mixlang_handoff_lang: wants agent in a specific language
MIXLANG-SUP Policy: agent and escalation rules
The MIXLANG-SUP policy sets preference detection without forcing a single language from the outset.
Six MIXLANG-SUP rules
DETECT-PREF-FIRST : macro MIXLANG-DETECT-PREF dominant thread language
Respond preference : MIXLANG-RESPOND-PREF language consistency
Bilingual if hybrid : MIXLANG-BILINGUAL-SUMMARY key point in two languages
Language handoff : MIXLANG-HANDOFF-LANG competent agent #12
Translate the essential : MIXLANG-TRANSLATE-KEY short policy
Log i18n : MIXLANG-LOG-I18N feeds #892
Situation matrix (agent)
Clear language : RESPOND-PREF + resolve CS
Ambiguous hybrid : DETECT-PREF question or BILINGUAL-SUMMARY
Bot wrong language : RESPOND-PREF + LOG-I18N #892
Topic poorly understood : handoff CHATMIS #879, not MIXLANG alone
Flow ML-1 to ML-8: standard resolution
Eight sequential steps, P3 SLA mixlang < 24 h, escalate i18n if recurrent bot_wrong_lang.
Flow ML-1 to ML-8
ML-1 Triage: read thread, tag mixlang_*, language or topic #879?
ML-2 Detect: dominant language, code-switch, hybrid
ML-3 Confirm pref: DETECT-PREF if preference_unclear
ML-4 Classify: mixlang_* via MIXLANG-MAP
ML-5 Execute: RESPOND-PREF, BILINGUAL, TRANSLATE, HANDOFF-LANG
ML-6 Confirm: macro MIXLANG-DONE resolution language
ML-7 Test: customer understands response in expected language
ML-8 Close: KPI mixlang_preference_resolution_rate + export #892
Eight ready-to-paste MIXLANG-* macros
Aligned language preference macros and bilingual handoff.
MIXLANG-* Library
MIXLANG-ACKNOWLEDGE: "We understand that the mix of languages has complicated the exchange. We are adapting our response."
MIXLANG-DETECT-PREF: "Do you prefer to continue in French or in English? / EN or FR?"
MIXLANG-RESPOND-PREF: Entire customer service response in the confirmed language map
MIXLANG-BILINGUAL-SUMMARY: "FR: {{résumé}}. EN: {{summary}}."
MIXLANG-TRANSLATE-KEY: "Key feedback point: {{FR}} / {{EN}}."
MIXLANG-HANDOFF-LANG: "Agent {{langue}} takes over. Reference: {{id}}."
MIXLANG-LOG-I18N: "Language report transmitted to bot team. Thread: {{langues}}."
MIXLANG-DONE: "Recap: language {{pref}}. Resolution: {{action}}. i18n report: {{oui_non}}."
MIXLANG-GATE tree and agent-ready languages registry
Decision tree before enforcing FR or ignoring EN preference.
MIXLANG-GATE
Clear dominant language? u2192 RESPOND-PREF
Hybrid message? u2192 BILINGUAL-SUMMARY or DETECT-PREF
Bot in the wrong language? u2192 RESPOND-PREF + LOG-I18N #892
Agent speaks another language? u2192 Competent HANDOFF-LANG
Policy to be translated? u2192 TRANSLATE-KEY registry #268
Minimum Internal Registry
Document helpdesk: agent languages, FR EN ES macros, language handoff procedure, KB link #268. Train agents: mixlang u2260 FR typo #890 u2260 misunderstanding #879.
KPI, QA and handoff to bot #892
Measuring MIXLANG detects bot i18n that is not adapted to code-switching.
Four MIXLANG KPIs
mixlang_preference_resolution_rate : customer receives response in expected language / total
mixlang_detect_pref_rate : % preference_unclear with DETECT-PREF
mixlang_bot_wrong_lang_rate : bot wrong language tickets / total mixlang
mixlang_i18n_logged_rate : % LOG-I18N traced to #892
Handoff #892
Export weekly MIXLANG-MAP: mixlang_code_switch mixlang_bot_wrong_lang are priorities. Guardrail MIXLANG-CODESWITCH-LOOP: each LOG-I18N feeds dynamic language detection #892.
Edge cases: three languages, rare language, client refuses to choose
Three cases outside the standard flow.
FR EN ES in the same thread
DETECT-PREF three options or HANDOFF-LANG trilingual agent if available.
Unsupported store language
ACKNOWLEDGE + TRANSLATE-KEY EN FR if possible. HANDOFF if complex policy.
Customer refuses to choose a language
BILINGUAL-SUMMARY key points. Do not force monolingual if hybrid suits customer comfort.
Agent training: 20 minutes MIXLANG
Module: DETECT-PREF, coherent RESPOND-PREF, short BILINGUAL, LOG-I18N, distinguish #879 #890 #892.
Exercises
Ticket A: "Hi, mon colis?" u2192 DETECT-PREF then RESPOND-PREF
Ticket B: bot responds in EN to FR customer u2192 RESPOND-PREF FR + LOG-I18N
Ticket C: poorly routed return subject u2192 handoff CHATMIS #879
How Qstomy structures MIXLANG in your stack
Qstomy route mixlang_*, detects agent thread language, bilingual macros and LOG export to code-switch #892.
Three bricks
Routing: mixed_language vs typo_fr vs sav_issue intent
Lang detect panel: sync MIXLANG-* dominant switch macros
Bot #892: track widget language change
Scenario: EU retail, 6 tickets/month code-switch. DETECT-PREF + RESPOND-PREF agents, #892 dynamic lang. mixlang_preference_resolution_rate goes from 68% to 88% in 5 weeks.
FAQ and MIХLANG deployment checklist
FAQ
Always reply in bilingual?
No. DETECT-PREF or dominant language. BILINGUAL if hybrid or requested.
Difference #16?
#891 = manage language mix in ticket. #16 = shop multilingual bot strategy.
Difference #892?
#891 = agents. #892 = bot detect follow code-switch widget.
7-Day Checklist
D1: MIXLANG-SUP + MIXLANG-MAP + agent languages
D2: 8 helpdesk macros FR EN
D3: routing matrix #16 #268 #879
D4: 20-min agent training
D5: mixlang_* tags + KPIs
D6: test DETECT vs BILINGUAL vs HANDOFF
D7: bot brief #892 CODESWITCH-GATE
Interlinking
Enzo
July 1, 2026
