E-commerce
July 1, 2026
"The bot is inventing SKUs that I hadn't added." "The AI promises to rebuild my cart without checking my account." "My promo code is not reapplied after the bot rebuild." Three failures where a miscalibrated abandoned cart bot hallucinates products, ignores login, or forgets the promo recovery map.
An e-commerce abandoned cart AI chatbot does not replace LOSTCART agents (#751). It reads LOSTCART-MAP, guides login first, lookups browse history SKU variants, quotes promo_recovery_policy_copy, and hands off rebuild execute OOS substitute to human ops.
This guide #752 covers intents bot_lostcart_*, flow LOSTCARTbot, and KPI lostcart_bot. Bot pair to the LOSTCART playbook (#751). AI conversion use case: finding products, variants, and promos without executed rebuild or invented SKUs.
Summary
Why automate abandoned cart recovery with a bot?
"My cart has disappeared," "which products did I have?" and "my promo code is lost" arrive as empty carts in the help page chat widget. A calibrated bot guides through LOGIN-FIRST, looks up the SKU API browse history without running a rebuild or inventing variants.
What the tier 1 bot resolves for lost carts
Recovery steps: recovery_steps_policy_copy RECOVERY-CITE-BOT map
Login guide: account_recovery_policy_copy LOGIN-FIRST-BOT map
Find products: browse_history_fallback SKU-API-GROUNDED lookup
Variant check: inventory API variant available map
Promo recover: promo_recovery_policy_copy cite map
Baymard reminds us that cart friction generates abandonment if recovery is opaque (Baymard, checkout 2026). Without a grounded bot, the AI invents cart items or ignores login recovery.
LOSTCARTbot vs LOSTCART #751, SCARTbot #438, CROSSDEVbot #750 and forfeit #47
Six contents, six distinct cart recovery flows.
Quick Matrix
#752 LOSTCARTbot: tier 1 bot retrieve products variants promo handoff without rebuild executed
#751 LOSTCART: agents rebuild oos substitute promo escalate ops
SCARTbot #438: bot restore save token distinct loss without save
CROSSDEVbot #750: distinct conversation context recovery SKU
Abandon #47: passive email follow-up distinct active ticket recovery
Discount bot: general promo code distinct lost cart rebuild
Pipeline: #752 bot retrieve products variants promo tier 1 → #751 agents rebuild oos substitute escalate ops.
Which bot_lostcart_* intents should be configured?
Eight abandoned cart bot intents mapped to lostcart_* typologies #751.
Eight bot_lostcart intents
bot_lostcart_recovery : recovery_steps_policy_copy RECOVERY-CITE-BOT map
bot_lostcart_login_guide : LOGIN-FIRST-BOT account_recovery_policy_copy map
bot_lostcart_find_products : browse_history SKU-API-GROUNDED lookup map
bot_lostcart_variant_check : inventory variant available OOS flag map
bot_lostcart_promo_recover : promo_recovery_policy_copy cite map
bot_lostcart_rebuild_guide : rebuild_policy_copy steps without execute map
bot_lostcart_oos_flag : oos_substitute_policy_copy cite map
bot_lostcart_handoff : rebuild execute OOS dispute → #751
Tier 1 auto : recovery, login, find products, promo if LOSTCART-MAP active + guardrails NO-REBUILD-EXECUTE-BOT.
bot_lostcart_handoff rebuild execute oos substitute → agents #751 payload email skus promo_code.
How to consume LOSTCART-MAP #751?
The bot reads LOSTCART-MAP #751: lostcart_program_id, recovery_steps_policy_copy, guest_recovery_policy_copy, account_recovery_policy_copy, rebuild_policy_copy, promo_recovery_policy_copy, browse_history_fallback_copy, oos_substitute_policy_copy, exclusions_copy, customer_communication_copy.
Lookup grounded
RECOVERY-CITE-BOT: recovery_steps_policy_copy cite map verbatim
LOGIN-FIRST-BOT: account_recovery_policy_copy before find products map
SKU-API-GROUNDED-BOT: browse_history cart API only do not LLM invent
NO-REBUILD-EXECUTE-BOT: no rebuild cart executed bot handoff #751 ops
PROMO-CITE-BOT: promo_recovery_policy_copy cite rebuild map
SCART437-REROUTE-BOT: save token → SCARTbot #438 distinct loss without save
LOSTCART751-HANDOFF-BOT: rebuild execute → #751 agents LC-7
Alignment anti-hallucination (#123): SKU promo variants = API browse history whitelist only.
LOSTCARTBOT-SUP policy in six rules
Six rules for responsible lost cart bot.
LOSTCART-MAP-GROUNDED-BOT: recovery rebuild promo from map only
LOGIN-FIRST-BOT: account_recovery_policy_copy before SKU lookup map
SKU-API-GROUNDED-BOT: API-only product variants no hallucination
NO-REBUILD-EXECUTE-BOT: no rebuild executed bot handoff #751 ops
PROMO-CITE-BOT: promo_recovery_policy_copy cite map only
SCART437-REROUTE-BOT: save token → SCART #437 distinct loss without save
Flow LOSTCARTbot LCB-1 to LCB-8
Eight-step cross-device lost cart bot flow.
LCB-1 Classify: bot_lostcart_* intent detect empty cart help page widget
LCB-2 Collect: email device_from device_to skus promo_code question
LCB-3 LOSTCART-MAP: recovery guest account rebuild promo oos exclusions
LCB-4 Lookup: AUTH-VERIFY cart saved_carts browse_history inventory API
LCB-5 Guardrail: RECOVERY LOGIN-FIRST SKU-API NO-REBUILD PROMO SCART437 HANDOFF
LCB-6 Respond: TPL-LOSTCARTbot grounded customer_communication_copy
LCB-7 Handoff or close: rebuild execute oos dispute #751 payload
LCB-8 Log: intent lostcart_program_id tag lostcart_bot recovery_cited handoff Y/N
Example TPL-LOSTCARTbot-FIND
“Step 1: [account_recovery_policy_copy map.] LOGIN-FIRST-BOT. Products found: [SKU-API-GROUNDED list map.] [oos_substitute_policy_copy if OOS map.] NO-REBUILD-EXECUTE-BOT.”
TPL-LOSTCARTbot and touchpoints templates
Four essential templates.
TPL-LOSTCARTbot-RECOVERY
Lost cart [device_from map] → [device_to map]: [recovery_steps_policy_copy map.] RECOVERY-CITE-BOT LOGIN-FIRST-BOT.
TPL-LOSTCARTbot-FIND
Products found: [SKU-API-GROUNDED lines map.] Variants: [inventory check map.] [oos_substitute_policy_copy if OOS map.] Add to cart link: [PDP links map.]
TPL-LOSTCARTbot-PROMO
Code [promo_code map]: [promo_recovery_policy_copy map.] PROMO-CITE-BOT. [If expired: alternative map.] LOSTCART751-HANDOFF-BOT if ops exception.
TPL-LOSTCARTbot-LOGIN
Log in [email map] on [device_to map]: [account_recovery_policy_copy map.] Account cart may reappear. AUTH-VERIFY-BOT.
Touchpoints
Empty cart page: bot_lostcart_recovery proactive
Keyword cart disappeared lost: bot_lostcart_find_products trigger
Post device switch: bot_lostcart_login_guide entry
Keyword promo code lost: bot_lostcart_promo_recover entry
Edge cases and reroutes
Five cases outside tier 1 standard lost cart bot.
Save existing token: SCART437-REROUTE-BOT #438 restore distinct link rebuild
Rebuild execute ops: bot_lostcart_handoff LOSTCART751-HANDOFF-BOT agents #751 only
Expired promo exception: LOSTCART751-HANDOFF-BOT finance ops map
Passive abandonment: #47 distinct follow-up active ticket recovery
Cross-device prevention: CROSSDEVbot #750 distinct recovery SKU
Bot guide recovery find promo tier 1. Rebuild execute oos substitute → agents #751.
Essential lostcart_bot KPIs
Five LOSTCARTbot management metrics.
lostcart_bot_recovery_deflect: login find promo resolved without agent
lostcart_bot_login_first_rate: LOGIN-FIRST-BOT / bot_lostcart recovery cart
lostcart_bot_sku_hallucination_violations: invented SKU bot audit target 0
lostcart_bot_promo_recover_rate: successful promo guide / total bot_lostcart_promo map
lostcart_bot_handoff_rate: rebuild execute oos / total lostcart bot
Target: lostcart_bot_sku_hallucination_violations 0 and lostcart_bot_recovery_deflect greater than 50%.
LOSTCARTbot Anti-patterns
Five common abandoned cart bot errors.
LLM-invented SKU: SKU-API-GROUNDED-BOT browse_history cart API only
Bot-executed rebuild: NO-REBUILD-EXECUTE-BOT handoff #751 ops
Skip login first: LOGIN-FIRST-BOT account_recovery_policy_copy map
Omitted promo rebuild: PROMO-CITE-BOT promo_recovery_policy_copy map
Confuse save #438: SCART437-REROUTE-BOT saved_carts lookup before rebuild
LOSTCARTbot with Qstomy
Qstomy on Shopify: detect bot_lostcart intent, LOSTCART-MAP RAG grounded, browse history SKU lookup, LOGIN-FIRST guardrail, handoff #751 ops tier 2.
Pipeline: #752 bot retrieve products variants promo tier 1 → #751 agents rebuild oos substitute escalate ops.
Explore AI support and request a demo.
Checklist, FAQ and going further
LOSTCARTbot Checklist (8 steps)
Sync LOSTCART-MAP #751: RAG bot empty cart help page cross-device
Policy LOSTCARTBOT-SUP: 6 rules LOGIN-FIRST SKU-API NO-REBUILD PROMO SCART437
8 intents bot_lostcart_*: flow LCB-1 to LCB-8
4 templates TPL-LOSTCARTbot-*: RECOVERY FIND PROMO LOGIN
Browse history API sync: SKU-API-GROUNDED lookup test agents
Empty cart embed chat: bot_lostcart_recovery proactive
Red team 10 prompts: Invented SKU executed rebuild login skip omitted promo
Dashboard KPI: lostcart_bot_* section 9 sku_violations recovery_deflect handoff
FAQ
Difference #751?
#751 = agents rebuild oos substitute promo escalate ops. #752 = bot tier 1 find product variants promo handoff without executed rebuild.
Does the bot rebuild the cart?
No. TPL-LOSTCARTbot-FIND guides PDP adding. NO-REBUILD-EXECUTE-BOT LOSTCART751-HANDOFF-BOT.
Are the cited products real?
LCB-4 browse_history cart API. SKU-API-GROUNDED-BOT not LLM invent.
Difference SCARTbot #438?
#438 = restore save token. #752 = loss without save login find rebuild guide.
Going Further
Support promo codes
This week: index LOSTCART-MAP RAG empty cart, red team sku_hallucination_violations audit, sync browse history API LOGIN-FIRST flow test.
Enzo
July 1, 2026
