E-commerce
1 juillet 2026
« Le bot ne comprend pas que je vis au Canada et livre en France. » « L'IA me dit d'appeler car mon +1 est invalide sans format E164. » « Transféré à un agent qui n'avait ni pays résidence ni pays livraison. » Trois échecs bot où l'IA traite l'expatrié comme touriste, accuse fraude carte ou handoff vide.
Un chatbot IA clients expatriés e-commerce ne remplace pas EXPAT-FLOW agents (#467). Il détecte country split residence ship, classifie bot_expat_* intents, lookup EXPAT-MAP grounded, guide checkout phone currency gift bundle, handoff subdomain avec payload complet.
Ce guide #468 couvre intents bot_expat_*, flow EXPATBOT et KPI expat_bot. Distinct du playbook expatrié (#467) et du bot devise (#394) : ici, cas d'usage IA clarifier pays devise livraison expatrié cross-border.
Sommaire
Pourquoi automatiser le support expatrié par bot ?
Les expatriés contactent souvent le support hors fuseau HQ, avec des questions multi-axes (livraison famille, téléphone, devise) qu'un bot générique international ne décompose pas.
Volume et opportunité bot expat
Sur DTC diaspora, 55 à 72 % des tickets expat sont botifiables tier 1 si EXPAT-MAP grounded et country split detector actifs avant handoff agents.
Trois risques bot expatrié non calibré
Fraud tone : carte pays A ship pays B accusé arnaque
Single country assume : bot ignore ship home gift pattern
Empty handoff : agent sans residence ship phone context
Ecommerce Times estime que 22 à 38 % des acheteurs cross-border sont expatriés ou diaspora (Ecommerce Times, cross-border 2026). Baymard note que checkout international mal guidé augmente abandon 15 à 22 % (Baymard, checkout international 2025).
Angle #468 vs contenus voisins
SAV expat #467 : EXPAT-FLOW agents execute. Le #468 = bot tier 1 guide handoff.
Devise préférée #466 : PREFCUR selector. Le #468 = bundle expat phone ship.
Bot devise #394 : FX explain litige. Le #468 = setup checkout pas dispute débit.
International #100 : vue globale. Le #468 = persona expatrié automate.
Multilingue #16 : langue bot. Le #468 = pays devise livraison pas langue seule.
Exemple DTC diaspora
FR brand, 56 expat tickets/mois baseline #467. Après EXPATBOT : expat_bot_auto_resolve 71 %, expat_bot_fraud_tone_violation 0, expat_bot_handoff_quality 93 %, expat_bot_csat 4,5/5.
Bot guide pas execute billing
EXPATBOT-SUP : bot clarify checkout handoff, agents #463 #464 execute post-order.
Off-hours diaspora chat volume
61 % expat bot sessions outside HQ business hours : EXPATBOT tier 1 critical timezone coverage.
Singapore-France diaspora pair
Highest expat_bot_gift_home volume pair FR diaspora : preload TPL-EXPATBOT-GIFT corpus Q4.
En quoi EXPATBOT diffère-t-il de EXPAT #467 et CUR-BOT #394 ?
Playbook expatrié humain, bot devise FX et bot expatrié bundle : trois layers international bot distincts.
Matrice bot → rôle expatrié
#468 EXPATBOT : country split classify guide handoff
#467 EXPAT-FLOW : agents subdomain execute invoice return
#394 CUR-BOT : FX litige presentment explain
#466 PREFCUR : currency selector layer inside expat bot
#379 INT-RET : return handoff post-order
Shared EXPAT-MAP corpus
#467 définit EXPAT-MAP JSON. #468 bot consomme same map : ship allowed phone rule macro template.
Quatre BOT-EXPAT-TYPE flows
bot_expat_gift_home_guide : ship family abroad checkout
bot_expat_phone_e164 : format international retry
bot_expat_currency_bundle : selector + residence context
bot_expat_subdomain_handoff : invoice VAT return agents
Promesse #468
Policy EXPATBOT-SUP, 12 intents bot_expat_*, flow EXPATBOT EB-1 à EB-8, guardrails, handoff payload, KPI expat_bot_*.
Pipeline bot amont aval
#468 EXPATBOT tier 1 → #467 agents execute → #466 PREFCUR currency → #463 invoice → #379 return.
Formation bot ops 30 minutes
Module 1 : country split vs FX litige. Module 2 : TPL-EXPATBOT walkthrough. Module 3 : handoff payload review. Quiz 90 % before prod.
Intent router upstream
Keywords expatrié diaspora livrer famille pays résidence route EXPATBOT before generic international #100 or currency #394 macro.
Quels intents bot_expat_* classifier ?
Douze intents bot expatrié avant flow EXPATBOT.
Douze intents bot_expat
bot_expat_gift_home : commander pour famille pays origine
bot_expat_phone_reject : numéro international refusé
bot_expat_currency_residence : devise vs pays résidence
bot_expat_ship_allowed : livraison pays X depuis pays Y
bot_expat_market_reset : site repasse market IP
bot_expat_card_mismatch : carte pays A livraison B
bot_expat_billing_invoice : facture adresse résidence
bot_expat_self_ship : achète et reçoit pays résidence
bot_expat_relocation : déménagement adresses mixtes
bot_expat_return_abroad : retour depuis pays résidence
bot_expat_timezone : horaires support fuseau
bot_expat_fx_litige : reroute #393 not expat setup
Tier bot execution
Tier 1 auto : gift_home, phone_e164, currency_residence, ship_allowed, market_reset, card_mismatch empathy, timezone, self_ship guide.
Tier 2 handoff : billing_invoice, return_abroad, relocation complex.
Tier reroute : bot_expat_fx_litige immediate #394 or #393 not EXPATBOT.
Champs session bot obligatoires
expat_intent, residence_country, ship_country, billing_country, phone_country_code, display_currency, country_split_detected, handoff_subdomain, auth_level.
Country split detector
EB-2 flags country_split when residence ≠ ship or billing ≠ residence from user message or order API pre-checkout.
Confidence threshold expat intent
Classifier below 0,75 : ask residence ship clarifying before EB-4 not generic international FAQ.
Post-handoff bot silence
After EB-7 subdomain handoff : bot stops checkout guidance same session prevent contradictory agent steps.
Comment le bot consomme EXPAT-MAP #467 ?
Le bot lit EXPAT-MAP #467 pour grounded ship phone billing rules sans inventer livraison.
Lookup EB-4 bot
residence + ship pair : allowed carrier macro
phone_validation : E164 international_accept
currency_link : PREFCUR-MAP #466 row
billing_rules : checkout guidance text
bot_can_execute : guide only | handoff subdomain
gift_home_flag : link #205 gift option
Pre-checkout no order
Collect residence ship countries user message EB-2 → EB-4 EXPAT-MAP → TPL-EXPATBOT-* respond.
Post-checkout auth order
EB-3 auth order email → read shipping billing presentment countries → subdomain handoff if correction needed.
Map miss handling
Country pair not in EXPAT-MAP : honest unsupported or handoff agent, never LLM promise delivery.
RAG corpus expat
/pages/expat + EXPAT-* macros #467 chunks. Proactive widget international PDP link.
Stale EXPAT-MAP version alert
Bot RAG hash mismatch #467 source : block ship allowed answers handoff until sync.
Order API post-checkout enrich
EB-3 read shipping_address.country billing_address.country presentment_currency for handoff payload accuracy.
Comment rédiger la policy EXPATBOT-SUP en huit règles ?
La policy bot expatrié EXPATBOT-SUP encadre clarify bundle sans fraude tone ni execute billing.
Huit règles EXPATBOT-SUP
Country split detect : EB-2 residence ship billing separate always
EXPAT-MAP grounded : ship allowed from map not LLM
NO-FRAUD-TONE : card mismatch empathy not accusation
FX litige reroute : bot_expat_fx_litige → #393 #394 not expat guide
Phone E164 guide : format before handoff theme bug
Handoff payload complete : countries intent map result phone
Subdomain not duplicate : billing → #463 VAT → #464 return → #379
/pages/expat link : self-service every expat thread once
Interdit bot production
Accuse fraud on card country split. Promise ship country not in EXPAT-MAP. Execute invoice correction API. Invent phone format by country without map. Treat expat as generic international FAQ only.
Tourist vs expat
One-week trip keywords : lighter #100 FAQ not full gift home bundle unless user confirms diaspora pattern.
Empathy guardrail
NO-FRAUD-TONE-01 block « suspicious », « fraude », « arnaque » on card mismatch unless fraud_score API flag.
Neutral country wording
TPL-EXPATBOT avoid « votre pays étranger » : use « pays de résidence » « pays de livraison » inclusive tone.
Gift option inline bundle
TPL-EXPATBOT-GIFT always mentions gift checkbox #205 when ship country ≠ residence : single bundled response not separate gift bot session.
Comment appliquer le flow EXPATBOT EB-1 à EB-8 ?
Le flow EXPATBOT EB-1 à EB-8 structure triage expatrié bot grounded maps.
Huit étapes EB-1 à EB-8
EB-1 Intent classify : bot_expat_* from message
EB-2 Country collect : residence ship billing phone split detect
EB-3 Context : pre-checkout | post order auth API countries
EB-4 EXPAT-MAP lookup : allowed phone currency macro
EB-5 FX litige check : reroute #393 if dispute debit keywords
EB-6 Respond tier 1 : TPL-EXPATBOT-* grounded bundle steps
EB-7 Branch : auto close | subdomain handoff | theme bug escalate
EB-8 Log : countries intent handoff csat /pages/expat click
EB-6 bot_expat_gift_home
TPL-EXPATBOT-GIFT : billing residence, shipping family country, gift option #205, link /pages/expat.
EB-6 bot_expat_phone_reject
TPL-EXPATBOT-PHONE E164 examples +65 +33 +1. Valid still reject → theme handoff ops.
EB-6 bot_expat_currency_residence
Bundle PREF-SELECTOR #466 within expat response TPL-EXPATBOT-CURRENCY.
EB-7 bot_expat_billing_invoice
Post-order handoff #463 INVADDR payload residence billing correction context.
EB-7 bot_expat_return_abroad
Handoff #379 INT-RET residence country return macro link.
EB-2 clarifying question
If residence ship not stated : « Où vivez-vous ? Où livrer le colis ? » before EB-4 lookup reduce wrong country assume.
SLA bot expat tier 1
EB-6 macro delivery under 5 s. Handoff acknowledgment under 10 s with reference number.
Quels templates TPL-EXPATBOT-* et guardrails configurer ?
Huit templates bot expatrié et guardrails NO-FRAUD-TONE FX-REROUTE.
TPL-EXPATBOT-GIFT (cadeau famille)
« Expatrié [résidence] → livraison [pays origine] : checkout billing votre adresse actuelle, shipping adresse famille. Option cadeau masque prix. Détail : [URL /pages/expat]. »
TPL-EXPATBOT-PHONE
« Téléphone format international : +[code][numéro] ex. +65 91234567. Sélectionnez pays shipping avant saisie si champ bloqué. »
TPL-EXPATBOT-CURRENCY
« Résidence [pays] : sélecteur devise [header] pour afficher [EUR/USD]. Persistance compte si connecté. Voir aussi /pages/currency. »
TPL-EXPATBOT-CARD
« Carte [pays] livraison [pays] : courant pour expatriés. Si refus paiement : vérifiez 3DS banque. Pas blocage automatique de notre côté. »
TPL-EXPATBOT-SHIP-OK
« Livraison [ship_country] depuis [residence_country] : autorisée. Délai estimé [X j] selon carrier EXPAT-MAP. »
TPL-EXPATBOT-HANDOFF
« Votre demande nécessite agent [facture/retour] : transfert avec dossier pays résidence [X] livraison [Y] sous [SLA]. »
Guardrail NO-FRAUD-TONE-01
Block accusatory fraud language on card country split unless Shopify fraud API high risk.
Guardrail FX-REROUTE-01
Keywords débité plus arnaque devise montant différent → route #393 not TPL-EXPATBOT.
Touchpoints widget
International PDP proactive « expatrié ? » T1
Checkout phone error hook T2
/pages/expat footer chat link T3
Handoff Gorgias expat_bot payload JSON
TPL-EXPATBOT-TIMEZONE
« Support [fuseau]. Email réponse sous [SLA]. Chat [heures]. Commande non urgente : email recommandé votre fuseau. »
TPL-EXPATBOT-MARKET
« Market détecté par IP [USD]. Connectez compte + footer market selector pour stabiliser. Voyage : cookie session. Détail /pages/expat. »
Quels cas diaspora, nomade et combined traiter ?
Les cas bot expatrié spéciaux exigent branch EXPAT-MAP ou subdomain handoff.
Q4 diaspora gift peak
Scale bot_expat_gift_home capacity Nov-Dec proactive widget diaspora landing.
Digital nomad 3-month
bot_expat_market_reset + bot_expat_currency_residence combo PREF-IP-RESET #466 link.
APO military row
EXPAT-MAP APO row TPL-EXPATBOT-APO if configured #467, else handoff agent.
Combined prefc + expat
Dual intent : currency within expat bundle one response not two separate bot sessions.
Multilingual expat
Respond checkout language user + link multilingue #16 if language not checkout issue.
Auth post-order subdomain
CIV #462 before billing handoff #463.
VAT expat professional
bot_expat_billing includes VAT question : subdomain #464 not EXPATBOT explain.
Theme phone libphonenumber
Persistent reject valid E164 : EB-7 theme_bug tag not repeat TPL-EXPATBOT-PHONE loop.
Checkout abandon hook
Shopify checkout phone validation error T2 : auto-trigger bot_expat_phone_reject with cart preserved context.
Consolidated onboarding Klaviyo
First international order email link /pages/expat + chat widget reduces repeat expat_bot_session_rate.
Quels KPI expat_bot mesurer ?
Les KPI bot expatrié lient auto-resolve, zero fraud tone et handoff quality.
Huit métriques clés
expat_bot_session_rate : sessions bot_expat / 100 international chats
expat_bot_auto_resolve : tier 1 closed sans agent / sessions
expat_bot_handoff_rate : tier 2 subdomain transfer / sessions
expat_bot_handoff_quality : payload countries complete / handoffs
expat_bot_fraud_tone_violation : NO-FRAUD-TONE blocks (cible 0)
expat_bot_fx_reroute_accuracy : #393 routed / fx litige sessions
expat_bot_checkout_continue : user confirms proceed post macro
expat_bot_csat : satisfaction post session expat path
Benchmark DTC diaspora
expat_bot_auto_resolve 65-75 %, expat_bot_fraud_tone_violation 0, expat_bot_handoff_quality > 90 %, expat_bot_csat > 4,3/5.
Dashboard hebdo bot international
Intent breakdown, country pair top 10, phone reject bot vs theme bug, gift home seasonality.
A/B proactive diaspora widget
International PDP hook vs passive : expat_bot_session_rate and checkout complete cohort.
expat_bot_phone_loop_exit
Track sessions 3+ TPL-EXPATBOT-PHONE same user : auto theme_bug handoff not infinite loop.
expat_bot_ticket_delta agents
Measure expat agent tickets month over month post-EXPATBOT : target 45-60 % tier 1 deflection handoff quality maintained.
Quels anti-patterns bot expatrié éviter ?
Douze anti-patterns bot expatrié à bannir production.
1. Fraud accusation card split
NO-FRAUD-TONE-01. TPL-EXPATBOT-CARD empathy.
2. Single country assume
EB-2 country split mandatory.
3. Invent ship allowed
Règle 2 EXPAT-MAP not LLM.
4. FX litige as expat setup
FX-REROUTE-01 #393.
5. Skip phone E164 guide
Règle 5 before theme handoff.
6. Empty handoff payload
Règle 6 countries intent map.
7. Execute invoice bot
EB-7 #463 handoff not API.
8. Generic #100 macro only
TPL-EXPATBOT bundle persona.
9. Ignore gift flag diaspora
TPL-EXPATBOT-GIFT #205 link.
10. Currency without PREFCUR map
TPL-EXPATBOT-CURRENCY #466 grounded.
11. Loop phone macro theme bug
EB-7 escalate after 2 valid E164 fail.
12. Skip /pages/expat link
Règle 8 every thread once.
13. Mix WISMO expat same session
Intent router : tracking question after expat setup resolved separate turn not combined confuse.
14. Duplicate subdomain handoff
Billing and VAT same session : single handoff payload both tags not two separate transfers agent repeat intake.
Comment Qstomy implémente EXPATBOT ?
Qstomy sur Shopify exécute EXPATBOT : bot_expat_* classifier, country split detector, EXPAT-MAP #467 lookup, NO-FRAUD-TONE FX-REROUTE guardrails, subdomain router #463 #464 #379, TPL-EXPATBOT-* bundle responses.
Capacités expat bot Qstomy
expat_intent_classifier : 12 bot_expat intents
country_split_detector : residence ≠ ship flag
expat_map_bot_lookup : ship phone currency rules
fraud_tone_guard : empathy card mismatch
fx_litige_rerouter : #393 branch EB-5
subdomain_handoff_payload : countries chain subdomain tag
Pipeline #468 #467 #466 #394
#468 bot tier 1 expat bundle. #467 agents execute. #466 currency layer. #394 FX litige reroute.
Scénario DTC chiffré
Diaspora FR, 56 expat tickets/mois, 48 % phone reject baseline.
Après EXPATBOT-SUP + Qstomy : expat_bot_auto_resolve 73 %, expat_bot_fraud_tone_violation 0, expat_bot_handoff_quality 94 %, expat_bot_csat 4,6/5.
Explorez support client et demander une démo.
Governance IA international
EB-8 logs feed gouvernance IA (#124) monthly expat_bot guardrail audit.
Weekly expat bot guardrail audit
Sample 25 sessions regex fraud tone and ship invent zero tolerance.
Corpus sync cadence
Re-index EXPAT-MAP and /pages/expat within 24 h of #467 policy update prevent stale ship allowed bot answers.
Quelle checklist pour déployer EXPATBOT ?
Checklist EXPATBOT (12 étapes)
Sync EXPAT-MAP #467 JSON into bot RAG
Rédiger policy EXPATBOT-SUP 8 règles
Deploy 12 intents bot_expat_* classifier
Implémenter EB-1 à EB-8 + country split detector
Activer guardrails NO-FRAUD-TONE FX-REROUTE
TPL-EXPATBOT-* templates + /pages/expat corpus
Subdomain handoff schema #463 #464 #379
Widget proactive international PDP diaspora T1
Test 8 scenarios : gift home, phone E164, currency bundle, card empathy, ship ok, FX reroute, billing handoff, return handoff
Dashboard KPI expat_bot section 9
Link PREFCUR #466 in TPL-EXPATBOT-CURRENCY
Red team fraud tone FX confusion quarterly
En bref
#468 = bot expatrié bundle, pas FX litige #394
Country split detect : EB-2 mandatory
NO-FRAUD-TONE : card mismatch empathy
EXPAT-MAP #467 : shared corpus
KPI expat_bot_handoff_quality : cible > 90 %
FAQ
Bot comprend expatrié vs touriste ?
EB-2 collect residence pattern. Tourist short stay lighter #100 FAQ.
Différence #467 ?
#467 agents execute invoice return. #468 bot guide handoff tier 1.
Numéro +65 refusé ?
TPL-EXPATBOT-PHONE E164. Theme bug if valid escalate.
Débit banque différent ?
FX-REROUTE #393 not expat bot setup.
Handoff agent reçoit quoi ?
Intent, residence, ship, billing, phone, EXPAT-MAP result, subdomain tag.
Aller plus loin
Cette semaine : import EXPAT-MAP into bot RAG, deploy country split detector, activer NO-FRAUD-TONE guardrail, configure subdomain handoff payload, test gift home phone currency 8 scenarios, lancer dashboard expat_bot_fraud_tone_violation zero tolerance.
Partagez ce guide #468 avec ops bot et international : un country split detector vaut dix bots traitant l'expatrié comme un client domestic, un handoff payload pays complet vaut vingt agents repartant de zéro sur tickets diaspora Q4.
Go-live test matrix
8 scenarios sign-off : gift home SG-FR, phone E164, currency bundle, card empathy, ship allowed, FX reroute #393, billing handoff #463, NO-FRAUD-TONE block test.
Q4 diaspora bot capacity
Pre-scale EXPATBOT Nov-Dec gift home proactive widget and handoff queue before diaspora holiday peak 2x session rate.
Enzo
1 juillet 2026
