E-commerce
July 1, 2026
"The bot doesn't understand that I live in Canada and delivers to France." "The AI tells me to call because my +1 is invalid without E164 format." "Transferred to an agent who had neither country of residence nor delivery country." Three bot failures where the AI treats the expatriate as a tourist, accuses card fraud, or performs an empty handoff.
An e-commerce expatriate customer AI chatbot does not replace EXPAT-FLOW agents (#467). It detects country split residence ship, classifies bot_expat_* intents, looks up grounded EXPAT-MAP, guides checkout phone currency gift bundle, and performs subdomain handoff with complete payload.
This guide #468 covers bot_expat_* intents, EXPATBOT flow, and expat_bot KPIs. Distinct from the expatriate playbook (#467) and the currency bot (#394): here, AI usecase to clarify cross-border expatriate country delivery currency.
Summary
Why automate expat support with a bot?
Expats often contact support outside of HQ business hours, with multi-faceted questions (family delivery, phone, currency) that a generic international bot cannot break down.
Volume and opportunity for expat bot
On DTC diaspora, 55 to 72% of expat tickets are tier 1 botifiable if EXPAT-MAP grounded and country split detector are active before agent handoff.
Three risks of an uncalibrated expat bot
Fraud tone: country A card shipped to country B accused of scam
Single country assume: bot ignores ship home gift pattern
Empty handoff: agent left without residence, ship, and phone context
Ecommerce Times estimates that 22 to 38% of cross-border buyers are expats or diaspora (Ecommerce Times, cross-border 2026). Baymard notes that poorly guided international checkout increases abandonment by 15 to 22% (Baymard, international checkout 2025).
Angle #468 vs related content
Expat CS #467: EXPAT-FLOW agents execute. #468 = bot tier 1 guide handoff.
Preferred currency #466: PREFCUR selector. #468 = bundle expat phone ship.
Currency bot #394: FX explain dispute. #468 = checkout setup, not debit dispute.
International #100: global view. #468 = automated expat persona.
Multilingual #16: bot language. #468 = country, currency, delivery, not just language.
DTC diaspora example
FR brand, 56 expat tickets/month baseline #467. After EXPATBOT: expat_bot_auto_resolve 71%, expat_bot_fraud_tone_violation 0, expat_bot_handoff_quality 93%, expat_bot_csat 4.5/5.
Bot guides, does not execute billing
EXPATBOT-SUP: bot clarifies checkout handoff, agents #463 #464 execute post-order.
Off-hours diaspora chat volume
61% of expat bot sessions occur outside HQ business hours: EXPATBOT tier 1 offers critical timezone coverage.
Singapore-France diaspora pair
Highest expat_bot_gift_home volume pair FR diaspora: preload TPL-EXPATBOT-GIFT corpus Q4.
How does EXPATBOT differ from EXPAT #467 and CUR-BOT #394?
Human expat playbook, FX currency bot, and bundle expat bot: three distinct international bot layers.
Bot → expat role matrix
#468 EXPATBOT: country split classify guide handoff
#467 EXPAT-FLOW: agents subdomain execute invoice return
#394 CUR-BOT: FX dispute presentment explain
#466 PREFCUR: currency selector layer inside expat bot
#379 INT-RET: return handoff post-order
Shared EXPAT-MAP corpus
#467 defines EXPAT-MAP JSON. #468 bot consumes same map: ship allowed phone rule macro template.
Four 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
Promise #468
Policy EXPATBOT-SUP, 12 intents bot_expat_*, flow EXPATBOT EB-1 to EB-8, guardrails, handoff payload, KPI expat_bot_*.
Upstream downstream bot pipeline
#468 EXPATBOT tier 1 → #467 agents execute → #466 PREFCUR currency → #463 invoice → #379 return.
Bot ops 30-minute training
Module 1: country split vs FX dispute. Module 2: TPL-EXPATBOT walkthrough. Module 3: handoff payload review. Quiz 90% before prod.
Upstream intent router
Keywords expat diaspora deliver family country residence route EXPATBOT before generic international #100 or currency #394 macro.
Which bot_expat_* intents should be classified?
Twelve expatriate bot intents before the EXPATBOT flow.
Twelve bot_expat intents
bot_expat_gift_home: order for family in country of origin
bot_expat_phone_reject: international number rejected
bot_expat_currency_residence: currency vs country of residence
bot_expat_ship_allowed: delivery to country X from country Y
bot_expat_market_reset: website switches back to IP market
bot_expat_card_mismatch: country A card, delivery B
bot_expat_billing_invoice: residence address invoice
bot_expat_self_ship: purchases and receives in country of residence
bot_expat_relocation: relocation with mixed addresses
bot_expat_return_abroad: return from country of residence
bot_expat_timezone: support hours by timezone
bot_expat_fx_litige: reroute #393 not expat setup
Bot execution tiers
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, complex relocation.
Tier reroute: bot_expat_fx_litige immediate #394 or #393 not EXPATBOT.
Required bot session fields
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.
Expat intent confidence threshold
Classifier below 0.75: ask clarifying residence-ship questions before EB-4, not generic international FAQ.
Post-handoff bot silence
After EB-7 subdomain handoff: bot stops checkout guidance in the same session to prevent contradictory agent steps.
How does the bot consume EXPAT-MAP #467?
The bot reads EXPAT-MAP #467 for grounded ship phone billing rules without inventing delivery.
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.
How to draft the EXPATBOT-SUP policy in eight rules?
The EXPATBOT-SUP expatriate bot policy governs clarify bundle without fraud tone or execute billing.
Eight EXPATBOT-SUP rules
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 dispute reroute: bot_expat_fx_litige u2192 #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 u2192 #463 VAT u2192 #464 return u2192 #379
/pages/expat link: self-service every expat thread once
Prohibited 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", "fraud", "scam" on card mismatch unless fraud_score API flag.
Neutral country wording
TPL-EXPATBOT avoid "your foreign country": use "country of residence" "delivery country" inclusive tone.
Gift option inline bundle
TPL-EXPATBOT-GIFT always mentions gift checkbox #205 when ship country u2260 residence: single bundled response not separate gift bot session.
How to apply the EXPATBOT EB-1 to EB-8 flow?
The EXPATBOT EB-1 to EB-8 flow structures the expat bot triage with grounded maps.
Eight steps: EB-1 to 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 dispute 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 but 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: "Where do you live? Where should the package be delivered?" before EB-4 lookup to reduce assuming the wrong country.
SLA bot expat tier 1
EB-6 macro delivery under 5 s. Handoff acknowledgment under 10 s with reference number.
Which TPL-EXPATBOT-* templates and guardrails should be configured?
Eight expat bot templates and NO-FRAUD-TONE FX-REROUTE guardrails.
TPL-EXPATBOT-GIFT (family gift)
"Expat [residence] → delivery [origin country]: checkout billing is your current address, shipping address is family. Gift option hides price. Details: [URL /pages/expat]."
TPL-EXPATBOT-PHONE
"Phone in international format: +[code][number] e.g., +65 91234567. Select shipping country before entering if field is locked."
TPL-EXPATBOT-CURRENCY
"Residence [country]: currency selector [header] to display [EUR/USD]. Account persistence if logged in. See also /pages/currency."
TPL-EXPATBOT-CARD
"Card [country] delivery [country]: common for expats. If payment is declined: check bank 3DS. No auto-blocking on our end."
TPL-EXPATBOT-SHIP-OK
"Delivery [ship_country] from [residence_country]: authorized. Estimated time [X days] according to carrier EXPAT-MAP."
TPL-EXPATBOT-HANDOFF
"Your request requires an agent [invoice/return]: transfer with country file residence [X] delivery [Y] within [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 charged more scam currency different amount → route #393 not TPL-EXPATBOT.
Touchpoints widget
International PDP proactive "expat?" T1
Checkout phone error hook T2
/pages/expat footer chat link T3
Handoff Gorgias expat_bot payload JSON
TPL-EXPATBOT-TIMEZONE
"Support [timezone]. Email response within [SLA]. Chat [hours]. Non-urgent order: email recommended for your timezone."
TPL-EXPATBOT-MARKET
"Market detected by IP [USD]. Log in to account + footer market selector to stabilize. Travel: session cookie. Details /pages/expat."
Which diaspora, nomad, and combined cases should be processed?
Special expat bot cases require EXPAT-MAP branch or 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.
Which KPIs should expat_bot measure?
The expat bot KPIs link auto-resolve, zero fraud tone, and handoff quality.
Eight key metrics
expat_bot_session_rate: bot_expat sessions / 100 international chats
expat_bot_auto_resolve: tier 1 closed without 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 (target 0)
expat_bot_fx_reroute_accuracy: #393 routed / fx dispute sessions
expat_bot_checkout_continue: user confirms proceed post macro
expat_bot_csat: satisfaction post session expat path
DTC diaspora Benchmark
expat_bot_auto_resolve 65-75 %, expat_bot_fraud_tone_violation 0, expat_bot_handoff_quality > 90 %, expat_bot_csat > 4.3/5.
Weekly international bot dashboard
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.
Which expat bot anti-patterns should be avoided?
Twelve expat bot anti-patterns to banish from 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
Rule 2 EXPAT-MAP not LLM.
4. FX litige as expat setup
FX-REROUTE-01 #393.
5. Skip phone E164 guide
Rule 5 before theme handoff.
6. Empty handoff payload
Rule 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
Rule 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.
How does Qstomy implement EXPATBOT?
Qstomy on Shopify runs 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.
Qstomy expat bot capabilities
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.
Encrypted DTC Scenario
FR Diaspora, 56 expat tickets/month, 48% phone reject baseline.
After 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.
Explore customer support and request a demo.
International AI Governance
EB-8 logs feed AI governance (#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.
What checklist is needed to deploy EXPATBOT?
EXPATBOT Checklist (12 steps)
Sync EXPAT-MAP #467 JSON into bot RAG
Draft EXPATBOT-SUP policy 8 rules
Deploy 12 intents bot_expat_* classifier
Implement EB-1 to EB-8 + country split detector
Activate 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
In brief
#468 = expat bot bundle, not FX dispute #394
Country split detect: EB-2 mandatory
NO-FRAUD-TONE: card mismatch empathy
EXPAT-MAP #467: shared corpus
KPI expat_bot_handoff_quality: target > 90 %
FAQ
Does the bot understand expat vs tourist?
EB-2 collect residence pattern. Tourist short stay lighter #100 FAQ.
Difference with #467?
#467 agents execute invoice return. #468 bot guide handoff tier 1.
Number +65 rejected?
TPL-EXPATBOT-PHONE E164. Theme bug if valid escalate.
Bank debit different?
FX-REROUTE #393 not expat bot setup.
What does the handoff agent receive?
Intent, residence, ship, billing, phone, EXPAT-MAP result, subdomain tag.
Going further
This week: import EXPAT-MAP into bot RAG, deploy country split detector, activate NO-FRAUD-TONE guardrail, configure subdomain handoff payload, test gift home phone currency 8 scenarios, launch dashboard expat_bot_fraud_tone_violation zero tolerance.
Share this guide #468 with bot ops and international: one country split detector is worth ten bots treating expats as domestic customers, a complete country handoff payload is worth twenty agents starting from scratch on Q4 diaspora tickets.
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
July 1, 2026
