E-commerce
July 1, 2026
"Where is the link to my saved cart?" "I want to change the size before paying." "My husband sent me his cart, how do I copy it?" Three messages where a client without a self-service save lookup opens a ticket even though SCART-MAP, the restore token, and the "My Carts" account already contain the TTL, content, and sharing link.
An e-commerce saved cart AI chatbot does not replace SCART-FLOW agents (#437). It reads SCART-MAP, quotes the token expires_at status, sends back the restore link within the resend limit, guides modify share fork and OOS price delta flags, then routes expired rebuild and draft B2B to #437.
This guide #438 covers intents bot_scart_*, flow SCART-BOT, and KPI scart_bot. Distinct from saved cart customer service (#437) and abandoned cart recovery (#47): here, voluntary AI save use case: resuming the purchase at the right place, not abandoned email recovery.
Summary
Why does a saved cart bot reduce retrieve tickets?
An avoidable saved cart ticket is born when the customer cannot find the restore link, expiration date, modify mode, or share fork before writing to support.
Five botifiable scart ticket triggers
Restore link: lost email, 404 token
Resend save email: resend link within limit
Modify guide: add or remove variant post-restore
Share fork: copy shared cart for oneself
Expiry TTL: how many days remain, D-7 reminder
Baymard points out that a significant portion of visitors postpone purchase after adding to cart without passive abandonment (Baymard, checkout 2026). Tidio estimates that a tier 1 cart bot reduces retrieve and modify tickets by 44-56% vs static FAQ (Tidio, chat stats 2026).
Angle #438 vs related content
Customer Service save #437: SCART-FLOW resend rebuild draft execute. #438 = bot tier 1 restore modify share TTL.
Abandonment #47: recovery email SMS post-exit. #438 = intentional token save, not abandonment marketing.
Bot abandonment #192: objections before abandonment email. #438 = deferred saved cart recovery.
Cart page #159: active cart UX. #438 = session restore from save token.
Shared cart #444: future collaborative co-buying bot. #438 = simple SCART-MAP share fork.
DTC Example
Fashion 340 saves/month, 28 baseline tickets #437. After SCART-BOT: scart_bot_resolution 87%, scart_bot_ticket_delta -49%, scart_restore_self_service 74%.
Save token gate
SCB-2 verify save token or account saved_carts exists. No token → bot_scart_route_abandon47 not SCART-BOT macros.
Sales save list building
Customers save multi-SKU before payday. T5 D-7 and bot restore chip critical conversion window.
How does SCART-BOT differ from SCART-FLOW #437 and abandonment #47?
Bot save self-service, playbook agents save and recovery abandon: three layers on SCART-MAP #437.
Bot scart → role matrix
#438 SCART-BOT: restore link, resend limit, modify guide, share fork, TTL cite, OOS price flag
#437 SCART-FLOW: expired rebuild, draft B2B, guest merge execute, resend abuse P1
#47 abandon recovery: email SMS discount post-exit without save token
#192 abandon bot: objections fee in-session pre-email
Upstream router
“Find saved cart”, “save link”, “modify saved cart”, “share cart”, “when does it expire”, “price changed restore” → SCART-BOT. “Expired cart rebuild”, “draft sales estimate”, “guest merge execute”, “resend 10x abuse” → handoff #437 SF-6. “Abandoned cart follow-up promo” without save → #47 or #192.
SCART-BOT data
SCART-MAP JSON #437, cart_token API, line items qty variant, expires_at, resend_count, share_mode, modify_allowed, inventory read-only, current_price delta.
Promise #438
Policy SCART-BOT, 12 intents bot_scart_*, flow SCB-1 to SCB-8, guardrails no rebuild bot, KPI scart_bot_*.
Save vs abandon intent
Customer says “forgotten cart”: SCB-2 lookup save token first. Abandon recovery only if zero save record.
Klaviyo save email parity
Bot SCB-5 and Klaviyo save email same API source expires_at. Weekly drift audit zero mismatch.
Which bot_scart_* intents should be configured?
Twelve saved cart bot intents cover tier 1 restore and dispute routing.
Twelve bot_scart intents
bot_scart_restore_link: token valid, restore_url, expires_at
bot_scart_resend_email: resend within resend_link_limit
bot_scart_list_account: logged-in account saved_carts list
bot_scart_modify_guide: restore then edit cart page steps
bot_scart_expiry_ttl: ttl_days, expires_at countdown
bot_scart_price_delta: saved vs current per line
bot_scart_oos_flag: SKU unavailable lines list
bot_scart_share_link: generate or cite share_url
bot_scart_fork_shared: fork_to_own_cart steps
bot_scart_guest_merge_guide: login merge_on_login explain
bot_scart_handoff_437: expired rebuild, draft, resend abuse
bot_scart_route_abandon47: no save token → abandon recovery
Session tags
scart_bot, scart_bot_restore, scart_bot_resolved, scart_bot_handoff_437, scart_bot_route47. Distinct abandon_bot, cart_page.
Triggers T1-T5
T1: save confirmation page proactive restore chip. T2: keyword saved cart/saved basket/cart link/recover cart. T3: account "My carts" widget. T4: /pages/saved-cart FAQ. T5: D-7 expiry proactive "Cart expires in 7 days".
How to apply the SCART-BOT flow in eight steps?
The SCART-BOT flow guides save grounded SCART-MAP #437 and cart token API.
Eight steps SCB-1 to SCB-8
SCB-1 Welcome: "I can find your saved cart: link, modification, sharing."
SCB-2 Auth lookup: email + cart_token or account saved_carts
SCB-3 Classifier intent: bot_scart_* section 3
SCB-4 Match SCART-MAP: scart_type, ttl, modify, share, price, oos
SCB-5 Read cart data: lines, expires_at, resend_count, inventory, prices
SCB-6 Respond: SCART-RESTORE style | resend | modify guide | share fork
SCB-7 CTA: restore_url | /pages/saved-cart | checkout if restored
SCB-8 Close/handoff: expired rebuild draft → #437 SF-6
SCB-5 restore_link
If token valid: cite N items, total current €, expires_at, restore_url. If expired → bot_scart_handoff_437 SCART-EXPIRED path.
SCB-6 resend_email
If resend_count < resend_link_limit → trigger resend API. Else handoff #437 abuse or wait 24 h cite SCART-MAP.
SCB-6 modify_guide
If modify_allowed full: step restore link → cart page → edit qty variant. If read-only share → bot_scart_fork_shared.
SCB-5 oos_flag price_delta
List OOS SKUs and price changes grounded SCB-5 JSON. No LLM invent totals.
SCB-2 no save found
Zero token account list empty → bot_scart_route_abandon47 explain difference save vs abandon recovery.
SCB-8 session log restore
Log restore_url sent_at expires_at cited. Handoff #437 pack for expired dispute.
Which SCART-BOT policy should be documented?
The SCART-BOT save cart policy governs restore site, resend limit, and handoffs.
Eight SCART-BOT Rules
SCART-MAP only: ttl, modify, share, resend from JSON #437
Cart API grounded: SCB-5 lines prices expires_at, no LLM invent
Save token gate: SCB-2 verify before SCART-BOT, else route #47
Resend within limit: resend_link_limit SCART-MAP, no unlimited bot
No rebuild execute bot: expired manual rebuild → handoff #437
Share no PII: share link no owner email address payment
Price delta explain: current_price show_delta, no locked price promise unless SCART-MAP
Max 5 turns scart admin: then restore CTA or handoff #437
RAG Corpus Sources
/pages/saved-cart, SCART-MAP #437, SCART-SUP #437, macros SCART-RESTORE SCART-SHARE from #437 section 7.
Sync Ops
TTL policy change → bot glossary + save modal copy. App outage token 404 → bot honest "save service unavailable" handoff #437 P2.
Monthly Review
Audit: wrong cart totals, expired token promise valid, abandon route miss, share PII leak.
Peak Black Friday
Nov save volume 3x: scale resend API rate limit, T5 J-7 proactive batch before TTL wave.
Bot Corpus SCART-MAP Version
RAG metadata version id. Ops TTL change reindex 24 h SLA.
Which guardrails protect restore and sharing?
The allowed vs. forbidden bot scart matrix protects token privacy and checkout integrity.
Allowed bot actions
Quote restore_url expires_at items total SCB-5
Resend email if under resend_link_limit
bot_scart_modify_guide step-by-step restore edit
bot_scart_share_link share_url share_mode quote
bot_scart_fork_shared fork CTA
bot_scart_oos_flag bot_scart_price_delta grounded list
bot_scart_list_account if logged in
Handoff #437 expired rebuild draft merge execute
Forbidden bot actions
Rebuild expired cart SKUs API bot
Edit line items on token without client restore session
Promise locked price not in SCART-MAP
Reveal owner email on share recipient view
Apply discount code bot on saved cart
Route abandon #47 discount if save token exists
Anti-hallucination cart
Template: « Cart #[id]: [N] items, [total] €, expires [date]. Link: [url]. » All from SCB-5 JSON.
Auth email match
Resend restore only if email matches cart owner. Wrong email → verify order history handoff #437.
Abandon confusion guard
bot_scart_route_abandon47: explain « saved = you clicked Save » vs « abandoned = email follow-up ». No mixed macros.
How do I connect SCART-MAP #437 and the Save Cart app?
The saved cart bot integration combines SCART-MAP, app token API, and Shopify inventory.
SCART-BOT read fields
cart_token status: valid, expired, not_found
expires_at / created_at: ISO TTL
line_items: sku variant qty price current
resend_count_24h: resend limit check
share_url share_mode: view_only fork
customer_saved_carts[]: account list if auth
Save My Cart, Cart Share apps webhook + Shopify inventory API OOS check on restore (Shopify, inventory 2026).
SCART-MAP bot layer
Import #437: scart_type, ttl_days, modify_allowed, share_mode, price_on_restore, oos_on_restore, resend_link_limit. SCB-4 per cart.
Restore session deep link
Token URL loads cart into session. Bot SCB-7 CTA same URL mobile desktop test iOS in-app browser.
Account sync scart_account_sync
Logged customer: bot_scart_list_account no token needed. Pick cart_id from list SCB-5.
Qstomy Integration
See Shopify integration + save app API for SCART-MAP RAG sync.
Inventory refresh on restore
SCB-5 re-fetch inventory at restore click not stale save snapshot. bot_scart_oos_flag accurate.
What are the save, 7-day expiry, and UX triggers for SCART-BOT?
The UX SCART-BOT deployment maximizes restore self-service and save→order conversion.
Five widget placements
Save confirmation T1: bot chip "Retrieve this cart"
My carts account T3: bot_scart_list_account per row
/pages/saved-cart T4: bot_scart_expiry_ttl FAQ
D-7 expiry T5: proactive restore before TTL
Share landing page: bot_scart_fork_shared recipient
Save modal post-click chip
After "Save cart" success: T1 bot "Link sent, expires [date]. Questions?" reduces scart_retrieve_email tickets by 40%.
D-7 proactive vs email only
T5 widget + Klaviyo D-7: scart_save_to_order_rate +15-20% vs email alone DTC cohorts. Bot quotes same expires_at as email.
Share recipient fork UX
share_url landing: bot chip "Copy cart" bot_scart_fork_shared one-shot. Track scart_share_fork_rate conversion.
A/B test T1
Save confirmation bot chip vs static: scart_bot_resolution + restore open rate 4 weeks.
Cross-device restore
Email open mobile → restore deep link. Bot bot_scart_restore_link same URL if client asks in desktop chat after mobile email.
WhatsApp share restore link
bot_scart_share_link short URL for gift list sharing. Track scart_share_fork_rate by channel.
Which KPIs should a smart bot measure?
The saved cart bot KPIs link deflection retrieve and save→order.
Eight key metrics
scart_bot_resolution_rate: resolved without handoff / scart_bot sessions
scart_bot_ticket_delta: decrease in tickets #437 vs baseline
scart_restore_self_service_rate: restore bot / retrieve questions
scart_resend_bot_rate: resend via bot / total resend
scart_fork_convert_rate: orders from fork / fork sessions
scart_bot_handoff_437_rate: expired rebuild routed agents
scart_save_to_order_bot_cohort: orders saves with bot touch / saves
scart_bot_csat: satisfaction tag scart_bot resolved
DTC Benchmark
scart_bot_resolution 84-91%, scart_bot_ticket_delta -42-52%, restore_self_service > 70%, scart_bot_csat > 4.3/5.
Monthly dashboard
Intent breakdown restore vs modify vs share, route47 count, handoff expired reasons, T5 D-7 open to order funnel.
Transcript audit
20 sessions/month: total grounded API, valid restore links, no abandon route when save exists, share PII clean.
Save vs abandon route accuracy
Track bot_scart_route_abandon47 false positive rate. Target < 3% save misrouted to abandon discount.
T1 to checkout funnel KPI
Track save confirmation bot open → restore click → checkout start. Optimize CTA copy monthly.
Modify guide completion rate
bot_scart_modify_guide sessions ending checkout / guide sessions. UX friction signal.
What anti-patterns should be avoided on cart save bots?
Ten saved cart bot anti-patterns to ban.
1. Invent cart total LLM
Rule 2 SCB-5 API only. Wrong total destroys checkout trust.
2. Rebuild expired bot
Rule 5 handoff #437. Ops SKU rebuild human or workflow.
3. Route #47 if save exists
Rule 3 token gate. Client loses save-specific restore link.
4. Unlimited resend bot
Rule 4 resend_link_limit. Spam and token abuse.
5. Skip SCART-SUP #437 prerequisite
/pages/saved-cart SCART-MAP before bot. Wrong TTL answers.
6. Modify on read-only share
share_mode view_only : fork not edit owner cart bot promise.
7. Locked price marketing bot
Rule 7 current_price unless SCART-MAP locked_price B2B.
8. Owner PII on share page bot cite
Rule 6 privacy. Never email name on share response.
9. Confusing wishlist #446
Product wishlist list ≠ checkout-ready saved cart. Router distinct.
10. 8-turn conversation
Max 5 turns rule 8. Restore URL CTA SCB-7.
11. Expired token say valid
SCB-5 expires_at check mandatory. Charge dispute if client checkout fail.
12. No T5 D-7 proactive
Expiry surprise tickets spike. T5 reduces scart_expired handoff 25-30%.
13. Discount on save bot forbidden
Recovery discount belongs #47 abandon not save restore. Mixed offer confuses save vs abandon KPI.
How does Qstomy resume the purchase at the right place?
Qstomy on Shopify: SCART-BOT token lookup, SCART-MAP modify share cite, restore link auto, resend within limit, OOS price delta flag, handoff #437 expired rebuild pre-filled fields cart timeline.
Qstomy scart bot capabilities
scart_token_lookup: SCB-5 valid expires_at
scart_map_explain: ttl modify share resend
scart_restore_template: SCART-RESTORE-01 auto
scart_resend_trigger: limit check API
scart_fork_cta: share recipient path
scart_route_abandon47: no token gate
Pipeline #438 → #437
Bot tier 1 restore modify share TTL. Agents expired rebuild draft execute. Shared SCART-MAP.
Encrypted DTC Scenario
340 saves/month, 28 tickets baseline #437.
After SCART-BOT Qstomy: scart_bot_resolution 88%, scart_bot_ticket_delta -47%, scart_save_to_order_bot_cohort +14%, scart_bot_csat 4.4/5.
Explore customer support and request a demo.
Training corpus sync
See train Shopify chatbot for SCART-MAP RAG sync.
Reduce AI tickets
See reduce AI tickets for scart_bot deflection dashboard.
What checklist is needed to deploy SCART-BOT?
SCART-BOT Checklist (12 steps)
Validate SCART-SUP #437 + SCART-MAP /pages/saved-cart
Export SCART-MAP JSON + save read-only API app token
Configure 12 flow intents bot_scart_* section 3
Implement flows SCB-1 to SCB-8 + save token gate SCB-2
Enable guardrails no rebuild + resend limit + no abandon misroute
Route scart vs #437 #47 #192
Placements save confirmation T1 + account T3 + /pages/saved-cart T4
Trigger T5 D-7 expiry proactive aligned email
Staging tests for 8 scenarios: restore valid, expired handoff, resend limit, modify guide, share fork, oos flag, price delta, route47 no token
Mobile deep link restore iOS Android validated
Monthly scart_bot KPI dashboard + save vs abandon route audit
A/B T1 save confirmation bot vs static 4 weeks
At a glance
#438 = bot save tier 1, #437 agents expired rebuild
SCART-MAP grounded: restore, TTL, modify, share
SCART-BOT: token gate → cart read → cite → CTA → handoff
Distinct abandon #47: save token required
KPI scart_bot_resolution: target > 85 %
FAQ
Difference with #437?
#437 CS expired rebuild draft resend abuse execute. #438 bot restore modify share TTL self-service.
Difference with abandon #47?
#47 recovery e-mail post-exit without save. #438 deliberate save token restore link.
Does the bot rebuild expired carts?
No. bot_scart_handoff_437 #437 SF-7 rebuild.
Modify via bot?
bot_scart_modify_guide restore link then edit cart page, not agent API edit.
Copy shared cart?
bot_scart_fork_shared if share_mode fork_to_own_cart SCART-MAP.
Going further
This week: sync SCART-MAP bot per scart_type, configure SCB-5 staging API token, test save token gate vs route47, enable T1 save confirmation chip + T5 D-7.
Share this guide #438 with support and conversion: a bot that cites "4 items, €187, expires August 12, here is your link" is worth ten recovered carts, a made-up total results in an abandoned checkout and a frustrated review.
No client save token?
bot_scart_route_abandon47 #47 recovery. Do not apply SCART-BOT macros.
Enzo
July 1, 2026
