E-commerce
July 1, 2026
"The chat starts from scratch on my computer." "The support email does not resume my mobile conversation." "The bot promises guest cart sync while policy says local." Three failures where a poorly calibrated cross-device bot loses context, ignores conversation_id, or hallucinates guest sync.
An e-commerce cross-device AI chatbot does not replace CROSSDEV agents (#749). It reads CROSSDEV-MAP, resumes mobile desktop email conversations via context token, cites cart_persistence_policy_copy, and performs handoff cart restore escalate to human ops.
This guide #750 covers intents bot_crossdev_*, flow CROSSDEVbot, and KPI crossdev_bot. Companion bot to the CROSSDEV playbook (#749). AI use case: maintain mobile desktop email conversational context without promised guest sync.
Summary
Why automate cross-device continuity with a bot?
"My cart disappeared on desktop", "resume our conversation?", and "email link to continue?" arrive via mobile widget footer cart email support. A calibrated bot resumes the conversation_id context, cites guest account policy without promising auto sync or losing history.
What the tier 1 cross-device bot resolves
Context resume: conversation_id CONTEXT-RESUME-BOT mobile desktop email
Cart policy: cart_persistence_policy_copy POLICY-CITE-BOT map
Login guide: session_sync_policy_copy AUTH-VERIFY-BOT map
Checkout resume: checkout_resume_policy_copy explain map
Email deep link: chat_context_policy_copy resume URL map
E-commerce AI agents must read live cart account data, not invent session states (Kn8, e-commerce agents 2026). Without a grounded bot, the AI loses context or promises guest sync.
CROSSDEVbot vs CROSSDEV #749, SCARTbot #438, email support, and #751 abandoned cart
Six contents, six distinct multi-device continuity flows.
Quick Matrix
#750 CROSSDEVbot: bot tier 1 context mobile desktop email handoff without sync guest promised
#749 CROSSDEV: agents cart restore checkout escalate ops
SCARTbot #438: bot restore link save distinct conversation context
#751 abandoned cart: playbook abandoned cart cross-device distinct chat context
Duplicate order: multi-device cause distinct bot continuity
Bot abandonment #192: objections checkout distinct cross-device session
Pipeline: #750 bot context mobile desktop email tier 1 → #749 agents cart restore checkout escalate ops.
Which bot_crossdev_* intents should be configured?
Eight cross-device bot intents mapped to crossdev_* typologies #749.
Eight bot_crossdev intents
bot_crossdev_policy: cart_persistence_policy_copy POLICY-CITE-BOT map
bot_crossdev_cart_lost: guest vs account login guide map
bot_crossdev_login_guide: session_sync_policy_copy AUTH-VERIFY-BOT map
bot_crossdev_checkout_resume: checkout_resume_policy_copy explain map
bot_crossdev_chat_resume: CONTEXT-RESUME conversation_id device switch
bot_crossdev_email_link: chat_context_policy_copy deep link resume map
bot_crossdev_save_fallback: saved_cart_fallback_copy SCART438 reroute map
bot_crossdev_handoff: cart merge dispute → #749
Tier 1 auto: policy, login, chat resume, email link if CROSSDEV-MAP active + guardrails NO-GUEST-SYNC-PROMISE-BOT.
bot_crossdev_handoff cart merge escalate → agents #749 payload email device conversation_id.
How to consume CROSSDEV-MAP #749?
The bot reads CROSSDEV-MAP #749: crossdev_program_id, cart_persistence_policy_copy, session_sync_policy_copy, checkout_resume_policy_copy, chat_context_policy_copy, saved_cart_fallback_copy, wishlist_sync_policy_copy, login_required_copy, supported_devices_copy, exclusions_copy, customer_communication_copy.
Lookup grounded
POLICY-CITE-BOT: cart_persistence_policy_copy cite map verbatim
CONTEXT-RESUME-BOT: conversation_id customer_token resume history device
AUTH-VERIFY-BOT: email account verify before cart lookup map
NO-GUEST-SYNC-PROMISE-BOT: no guest cart sync promised bot map
EMAIL-LINK-CITE-BOT: chat_context_policy_copy deep link resume map
SCART438-REROUTE-BOT: explicit save → SCARTbot #438 distinct context
CROSSDEV749-HANDOFF-BOT: cart merge dispute → #749 CD-7 agents
Anti-hallucination (#123) alignment: cart session context = CROSSDEV-MAP + API whitelist only.
CROSSDEVBOT-SUP policy in six rules
Six rules for a responsible cross-device bot.
CROSSDEV-MAP-GROUNDED-BOT: cart session continuity from map only
CONTEXT-RESUME-BOT: conversation_id resume before respond new device
POLICY-CITE-BOT: cart_persistence_policy_copy cited without omission
NO-GUEST-SYNC-PROMISE-BOT: no guest sync promised by bot on login or save map
AUTH-VERIFY-BOT: email verify before revealing map account cart
EMAIL-LINK-CITE-BOT: chat_context_policy_copy deep link resume map
Flow CROSSDEVbot CDB-1 to CDB-8
Flow eight steps bot cross-device context.
CDB-1 Classify: bot_crossdev_* intent detect device_from device_to widget email
CDB-2 Collect: email conversation_id device account_status question
CDB-3 CROSSDEV-MAP: cart session checkout chat save exclusions
CDB-4 Lookup: conversation resume AUTH-VERIFY cart logged_in verify
CDB-5 Guardrail: CONTEXT-RESUME POLICY AUTH NO-GUEST-SYNC EMAIL-LINK HANDOFF
CDB-6 Respond: TPL-CROSSDEVbot grounded customer_communication_copy
CDB-7 Handoff or close: cart merge dispute #749 payload
CDB-8 Log: intent crossdev_program_id tag crossdev_bot context_resumed handoff Y/N
Example TPL-CROSSDEVbot-RESUME
"Conversation resumed [conversation_id map.] [Summary 3 lines history CONTEXT-RESUME-BOT.] [cart_persistence_policy_copy map.] NO-GUEST-SYNC-PROMISE-BOT if guest map."
TPL-CROSSDEVbot and touchpoint templates
Four essential templates.
TPL-CROSSDEVbot-POLICY
[cart_persistence_policy_copy map.] Account: mobile desktop sync. Guest: local cart. [login_required_copy map.] POLICY-CITE-BOT NO-GUEST-SYNC-PROMISE-BOT.
TPL-CROSSDEVbot-RESUME
Context resumed [device_from map] → [device_to map.] [Conversation summary CONTEXT-RESUME-BOT.] Continuation: [last pending question map.]
TPL-CROSSDEVbot-EMAIL
Conversation resume link: [chat_context_policy_copy deep link map.] EMAIL-LINK-CITE-BOT. Valid for [link_ttl_hours map] hours map.
TPL-CROSSDEVbot-LOGIN
Log in [device_to map]: [session_sync_policy_copy map.] AUTH-VERIFY-BOT email [email map.] Cart sync after login map.
Touchpoints
Mobile widget footer cart : bot_crossdev_policy proactive
Desktop widget reopen : bot_crossdev_chat_resume CONTEXT-RESUME entry
Email support footer : bot_crossdev_email_link deep link entry
Keyword continue on computer : bot_crossdev_login_guide trigger
Edge cases and reroutes
Five cases outside tier 1 standard cross-device bot.
Guest lost cart: bot_crossdev_save_fallback SCART438-REROUTE-BOT #751 distinct context lost cart
Explicit save cart: SCART438-REROUTE-BOT #438 restore distinct link
Double order: DUPORDER-REROUTE-BOT multi-device duplicate playbook
Expired TTL conversation: EMAIL-LINK-CITE new session + map summary
Cart merge dispute: bot_crossdev_handoff CROSSDEV749-HANDOFF-BOT agents #749 only
Bot resume context policy tier 1. Cart merge escalate ops → agents #749.
Essential crossdev_bot KPIs
Five CROSSDEVbot steering metrics.
crossdev_bot_context_resume_rate: conversation resumed device switch / total crossdev bot
crossdev_bot_policy_cite_rate: POLICY-CITE-BOT / bot_crossdev policy cart
crossdev_bot_guest_sync_violations: sync guest promis bot audit target 0
crossdev_bot_email_link_click_rate: deep link email clicked / sent map
crossdev_bot_handoff_rate: cart merge dispute / total crossdev bot
Target: crossdev_bot_guest_sync_violations 0 and crossdev_bot_context_resume_rate greater than 70%.
CROSSDEVbot anti-patterns
Five common cross-device bot errors.
Lost context on device switch: CONTEXT-RESUME-BOT conversation_id before respond
Guest sync promised to bot: NO-GUEST-SYNC-PROMISE-BOT cart_persistence_policy_copy map
Cart without AUTH-VERIFY: account email verification before lookup cart map
Email without deep link: EMAIL-LINK-CITE-BOT chat_context_policy_copy map
LLM-invented history: CONTEXT-RESUME API transcript only no hallucination
CROSSDEVbot with Qstomy
Qstomy on Shopify: detect bot_crossdev intent, CROSSDEV-MAP RAG grounded, CONTEXT-RESUME conversation_id, email deep link, NO-GUEST-SYNC guardrail, handoff #749 ops tier 2.
Pipeline: #750 bot context mobile desktop email tier 1 → #749 agents cart restore checkout escalate ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
CROSSDEVbot Checklist (8 steps)
Sync CROSSDEV-MAP #749: RAG bot mobile desktop email footer widget
Policy CROSSDEVBOT-SUP: 6 CONTEXT-RESUME POLICY NO-GUEST-SYNC AUTH EMAIL-LINK rules
8 intents bot_crossdev_*: flow CDB-1 to CDB-8
4 templates TPL-CROSSDEVbot-*: POLICY RESUME EMAIL LOGIN
Conversation_id persistence API: CONTEXT-RESUME device switch test
Email deep link resume: bot_crossdev_email_link chat_context_policy_copy
Red team 10 prompts: lost context guest sync promis invented history
Dashboard KPI: crossdev_bot_* section 9 context_resume guest_violations email_click
FAQ
Difference #749?
#749 = agents cart restore checkout escalate ops. #750 = bot tier 1 mobile desktop email context handoff without guest sync promises.
Does the bot resume conversation on another device?
Yes. TPL-CROSSDEVbot-RESUME CONTEXT-RESUME-BOT conversation_id map.
Does the email resume the chat?
TPL-CROSSDEVbot-EMAIL EMAIL-LINK-CITE-BOT chat_context_policy_copy deep link map.
Difference SCARTbot #438?
#438 = restore cart link save. #750 = general cross-device conversational context.
Going further
This week: index CROSSDEV-MAP RAG widget, test CONTEXT-RESUME device switch mobile desktop, red team guest_sync_violations audit email deep link.
Enzo
July 1, 2026
