E-commerce
July 1, 2026
"Where is my wishlist?" "My favorite item is back in stock, how do I buy it?" "What do you recommend from my wishlist?" Three messages where a wishlist customer without self-service opens a ticket, even though WISH-MAP, the list link, and the stock status already contain the conversion answer.
An e-commerce wishlist AI chatbot does not replace WISH-FLOW agents (#445). It reads WISH-MAP, cites grounded lists and items, guides add to cart and stock alerts, prompts back-in-stock alerts, suggests catalog alternatives, and then routes registry migration and complex guest merges to #445.
This guide #446 covers intents bot_wish_*, flow WISH-BOT, and KPI wish_bot. Distinct from wishlist customer support (#445) and abandonment recovery (#47): here, loyalty AI use case: target, advise, and convert wishlist desire into an order.
Summary
Why does a wishlist bot reduce loyalty-related support tickets?
An avoidable wishlist ticket is born when the customer cannot find their list, share, add to cart, or stock alert before writing to loyalty support.
Five botifiable wish ticket triggers
Retrieve list: lost account or guest list
Share link: share family registry
Add to cart howto: favorite button to cart
OOS notify: activate back-in-stock alert
Conversion follow-up: available favorite, buying advice
Klaviyo estimates that re-engaged wishlist customers convert 2 to 3 times more (Klaviyo, wishlist 2026). Tidio notes that a tier 1 wishlist bot reduces retrieve and share tickets by 48% to 58% vs. static FAQ (Tidio, chat stats 2026). Gorgias documents post-purchase assistants and multi-intent favorites (Gorgias, assistant 2026).
Angle #446 vs neighboring content
Customer Service wish #445: WISH-FLOW registry merge migration execute. #446 = tier 1 retrieve share add notify follow-up bot.
Abandonment #47: checkout exit cart recovery promo. #446 = voluntary favorite deferred intent.
Bot save #438: restore cart save #437. #446 = heart product list, not cart token.
Back in stock: general back-in-stock alerts. #446 = notify from favorite wish context.
Contextual recommendations: conversion engine setup. #446 = shopping advice grounded on customer wishlist items.
DTC Example
Fashion store with 2,400 active wishlists, 52 tickets/month baseline #445. After WISH-BOT: wish_bot_resolution 86%, wish_bot_ticket_delta -51%, wish_bot_add_cart_rate 34%, wish_bot_csat 4.4/5.
Wish gate WB-2
Verify wishlist_id or account wish before WISH-BOT macros. No wish record → bot_wish_route_scart437 or abandon #47 disambiguation.
Peak Q4 registry re-engagement
Nov-Dec wish volume 3x: scale T5 reengage and T1 widget capacity pre-holiday.
How does WISH-BOT differ from WISH-FLOW #445 and abandonment #47?
Bot wishlist, playbook agents wish, and recovery abandon: three distinct deferred purchase intent layers.
Bot wish matrix → role
#446 WISH-BOT: list cite, share link, add cart guide, notify OOS, relance in-stock, advise grounded wish items
#445 WISH-FLOW: registry complex, app migration, guest merge execute, share regen abuse
#47 abandon: cart exit recovery discount marketing
#438 SCART-BOT: save cart restore token
Upstream Router
"My wishlist", "favorites list", "share list", "add favorite to cart", "favorite stock alert", "my wish available" → WISH-BOT. "Registry migration app", "guest merge failed ops", "share regen 10x" → handoff #445 WB-7. "Abandoned cart promo follow-up" without wish → #47.
WISH-BOT Data
WISH-MAP JSON #445, wishlist app API items SKU variant inventory price, share_url, guest_merge status, back_in_stock subscribed flag, catalog API alternatives exclude wish owned.
Promise #446
Policy WISH-BOT, 12 intents bot_wish_*, flow WB-1 to WB-8, guardrails no checkout impersonation, KPI wish_bot_*.
Follow-up vs abandon
bot_wish_reengage_nudge: item wish back in stock or price drop event API. Distinct from abandon discount recovery loyalty tone, not checkout exit urgency.
Shared cart #444 boundary
Co-shopping live cart → SHCART-BOT #444. WISH-BOT heart favorite list only.
Which bot_wish_* intents should be configured?
Twelve wishlist bot intents cover tier 1 retrieve conversion and routing.
Twelve bot_wish intents
bot_wish_lookup : email customer_id wishlist verify WB-2
bot_wish_list_cite : N items link /account/wishlist
bot_wish_guest_merge_guide : merge_on_login steps WISH-GUEST style
bot_wish_share_link : share_url share_mode cite regen limit
bot_wish_add_cart_guide : add to cart line steps UI
bot_wish_add_all_partial : X/N addable OOS list grounded
bot_wish_oos_notify : back_in_stock setup from wish item
bot_wish_price_delta : current vs saved price API cite
bot_wish_reengage_nudge : in-stock or promo item wish proactive
bot_wish_advise_similar : 1-2 SKU grounded same collection wish context
bot_wish_handoff_445 : registry migration merge fail complex
bot_wish_route_scart437 : save cart intent no wish
Session tags
wish_bot, wish_bot_retrieve, wish_bot_convert, wish_bot_resolved, wish_bot_handoff_445, wish_bot_route437. Distinct abandon_bot, scart_bot.
Triggers T1-T5
T1: /account/wishlist page widget "List help". T2: keyword wishlist favorites wishlist heart. T3: /pages/wishlist FAQ embed. T4: back-in-stock email deep link ?intent=bot_wish_reengage_nudge. T5: proactive item wish in stock Klaviyo segment.
Intent priority
bot_wish_lookup before bot_wish_advise_similar. Grounded advice wish items only not random catalog.
Intent routing P1 P2 P3
P1: bot_wish_list_cite, bot_wish_reengage_nudge. P2: bot_wish_add_cart_guide, bot_wish_share_link. P3: bot_wish_advise_similar, bot_wish_guest_merge_guide.
How to apply the WISH-BOT flow in eight steps?
The WISH-BOT flow guides wishlist grounded WISH-MAP #445 and app API.
Eight steps WB-1 to WB-8
WB-1 Welcome: "I help you on your wishlist: find, share, buy."
WB-2 Auth lookup: email + customer_id or wishlist_id
WB-3 Classifier intent: bot_wish_* section 3
WB-4 Match WISH-MAP: persistence share merge oos notify
WB-5 Read list data: items inventory prices share_url merge status
WB-6 Respond: list cite | share | add guide | notify | relance | advise
WB-7 CTA: /account/wishlist | share_url | add to cart deep link | notify toggle
WB-8 Close/handoff: registry migration → #445 WF-6
WB-5 list_cite flow
Items found → bot_wish_list_cite N favorites top 3 SKU names in-stock flag link account wishlist.
WB-6 add_all_partial
WB-5 inventory per line → bot_wish_add_all_partial X/N addable cite OOS SKUs WISH-ADDALL style. CTA add all button URL.
WB-6 reengage_nudge T4 T5
Webhook in_stock on wish SKU → bot_wish_reengage_nudge "[SKU] from your list is available" + add cart deep link. No discount invent unless WISH-MAP promo event API.
WB-6 advise_similar
Client asks advice among wish → bot_wish_advise_similar max 2 in-stock wish items or 1 alternative same need catalog API. No LLM invent SKU.
WB-2 no wish found
Zero wishlist → bot_wish_route_scart437 or #47 disambiguation heart vs save vs abandon.
WB-8 conversion log
Log add_cart_click share_sent notify_subscribed advise_sku cited. Dashboard wish_bot_add_cart_rate.
WB-7 share regen limit
Track wish_share_regen_count per list 24 h. Over limit → handoff #445 not bot regen.
Which WISH-BOT policy should be documented?
The WISH-BOT wishlist policy incorporates WISH-SUP #445 with AI conversion safeguards.
Eight WISH-BOT rules
WISH-MAP only: share merge notify from JSON #445
List API grounded: WB-5 items prices inventory not LLM invent
Wish gate WB-2: verify wish before bot macros else route #437 #47
Add to cart guide only: no agent checkout impersonation rule 4 WISH-SUP
Share regen within limit: 3x per list per 24 h WISH-SUP
Advise max 2 SKU: bot_wish_advise_similar catalog API wish context
Follow-up no abandon tone: loyalty building not panic discount unless policy API
Max 8 turns wish flow: then CTA wishlist or handoff #445
RAG sources corpus
/pages/wishlist, WISH-MAP #445, WISH-SUP #445, macros WISH-LIST WISH-SHARE from #445 section 7.
Follow-up vs spam
bot_wish_reengage_nudge max 1 proactive per SKU per 7 days same customer. Opt-out marketing link cites CNIL.
Monthly wish bot review
Audit: wrong list count, share PII leak, advise hallucination SKU, abandon misroute, discount invent.
Sync ops app migration
Wishlist app switch window: bot honest "list service maintenance" handoff #445 not invent items.
Which guardrails protect conversion and catalog?
The authorized vs prohibited bot wish matrix protects trust, loyalty, and product accuracy.
Authorized bot actions
Lookup wishlist WB-2 verify
Cite list items in-stock OOS grounded
Share link regen within limit
Guide add to cart add all UI steps
Notify setup back_in_stock from wish
Follow-up on in-stock wish item deep link
Advise 1-2 SKU catalog API wish or similar collection
Guest merge guide merge_on_login steps
Prohibited bot actions
Checkout or add to cart API for client
Invent wish items or prices hallucination
Public share URL on private list
Abandon recovery discount macro on wish
Advise SKU outside catalog API
Registry owner PII to share recipient
Anti-hallucination advise
Template: "Among your available favorites: [SKU name] [price]" or "Alternative: [SKU]" from catalog JSON. See hallucination prevention.
Reco vs wish advise boundary
bot_wish_advise_similar limited wish items + 1 substitute. Full PDP reco engine → contextual reco article not WISH-BOT scope.
CNIL follow-up opt-in
T5 proactive requires marketing consent flag customer. No nudge without opt-in wish alerts.
How to connect WISH-MAP #445 and Shopify wishlist app?
The wishlist bot integration combines WISH-MAP, wishlist API, and catalog lookup.
WISH-BOT read fields
wishlist_id: app list identifier
items[]: sku variant_id in_stock price saved_price
share_url: unlisted or public per share_mode
guest_merge_pending: boolean post-login
notify_subscribed[]: SKUs back-in-stock active
wish_type: account registry guest
Swym Wishlist Plus apps expose API items and share (Shopify App Store, wishlist 2026).
In-stock webhook T5
Inventory restock on wish SKU → trigger bot_wish_reengage_nudge proactive if customer opted marketing wish alerts.
Add cart deep link WB-7
/cart/add?id=variant_id from wish line enables one-click CTA post relance. Track wish_bot_add_cart_rate click.
Qstomy Integration
See Shopify integration + WISH-MAP RAG sync #445 policy update.
Klaviyo event parity
WB-5 same item source as Klaviyo wishlist flow. Bot cite consistent prices not stale marketing email.
Route OOS substitute
Wish item OOS advise → catalog similar + out of stock (#87) notify path bot_wish_oos_notify.
Swym API item sync
WB-5 poll wishlist API every session start. Stale cache max 5 min inventory price drift.
Which follow-up, UX, and disambiguation triggers should be configured?
The UX WISH-BOT deployment maximizes retrieve conversion and loyalty reactivation.
Five widget placements
/account/wishlist T1: "Help my list" chip WB-1
/pages/wishlist T3: bot embed FAQ + lookup
PDP post-heart T2: "See my list" opens bot list cite
Back-in-stock email T4: deep link bot reengage add cart
Proactive T5 in-stock: wish segment restock nudge
Heart vs save disambiguation WB-2
Opening question "Favorite heart or saved cart?" routes WISH-BOT vs SCART-BOT #438. Reduces misroute 40%.
Add all inline helper
Wishlist page "Add all" fail OOS → auto bot_wish_add_all_partial explain partial.
Registry season T5 batch
Nov-Dec registry: proactive bot_wish_share_link reminder owners share family not bot registry ops handoff.
Advice chip on list page
"What to choose from my favorites?" → bot_wish_advise_similar in-stock priority.
Guest merge post-login T1
First login empty wish detect guest_merge_pending → auto bot_wish_guest_merge_guide before ticket.
A/B reactivation copy WB-6
Variant A "available" vs B "back in stock" : measure wish_bot_reengage_convert 4 weeks.
Which KPIs should the bot measure?
Wishlist bot KPIs link deflection, favorites → cart conversion, and quality follow-ups.
Eight key metrics
wish_bot_resolution_rate: resolved without handoff / wish_bot sessions
wish_bot_ticket_delta: decrease in #445 tickets vs baseline
wish_bot_add_cart_rate: add-to-cart click post bot / convert sessions
wish_bot_reengage_convert: order within 7 days post T4 T5 nudge / nudges
wish_bot_share_sent_rate: share link cited / share intents
wish_bot_notify_setup_rate: notify subscribed post bot / OOS intents
wish_bot_handoff_445_rate: registry migration complex routed
wish_bot_csat: satisfaction tag wish_bot resolved
DTC Benchmark
wish_bot_resolution 84-90%, wish_bot_ticket_delta -45-55%, wish_bot_add_cart_rate 28-38%, reengage_convert 12-18%, wish_bot_csat > 4.2/5.
Monthly dashboard
Intent breakdown, T1-T5 trigger performance, advise_similar click, misroute scart437 rate, registry handoff count.
Audit advise hallucination
Transcript scan invent SKU count zero. Violation P2 retrain corpus.
Cohort retention
LTV wish_bot engaged vs non-bot wish users. Target +10% repeat purchase 90 days post bot session.
T4 email to bot conversion
Track back-in-stock email deep link → bot session → add cart. Target T4 convert > 15%.
What anti-patterns should be avoided on a wishlist bot?
Twelve wishlist bot anti-patterns to banish.
1. Abandon discount on wish
Rule 7 loyalty follow-up not #47 panic promo.
2. Confusing save #438
WB-2 wish gate. SCART restore wrong object.
3. Agent add to cart API
Rule 4 UI guide only WISH-SUP.
4. Invent list items
Rule 2 WB-5 API grounded.
5. Public share private list
share_mode private WISH-MAP uphold.
6. Advise random catalog
Rule 6 max 2 wish context or similar collection.
7. Skip WISH-SUP #445 prerequisite
/pages/wishlist WISH-MAP before bot deploy.
8. Spam follow-up same SKU
Max 1 proactive per SKU per 7 d.
9. Registry ops on bot
wish_registry_event complex → handoff #445.
10. Locked price promise
bot_wish_price_delta current price WISH-SUP rule 6.
11. Ignore guest merge
bot_wish_guest_merge_guide T1 post-login empty list.
12. Shared cart #444 confusion
Co-purchase cart ≠ wishlist heart. Disambiguate WB-2.
13. Bot replaces Klaviyo entirely
Error: bot T5 only no email back-in-stock. Multi-channel complement not replace.
How does Qstomy automate the wishlist and conversion?
Qstomy on Shopify runs WISH-BOT: WB-2 wish lookup, bot_wish_list_cite items API, share link regen limit, add cart guide deep link, oos notify steps, reengage in-stock nudge, advise_similar catalog grounded, handoff #445 registry pre-filled fields.
Qstomy bot_wish Capabilities
bot_wish_lookup: WB-2 customer wishlist verify
bot_wish_list_read: items inventory price API
bot_wish_share_template: WISH-SHARE style auto
bot_wish_add_cart_deeplink: variant add URL WB-7
bot_wish_reengage_trigger: in-stock webhook T5
bot_wish_handoff_ticket: #445 ops pre-fill
Pipeline #445 → #446
#445 WISH-SUP WISH-MAP prerequisites. #446 bot tier 1 deflect 85 %+ retrieve share convert. Shared policy human registry migration.
Encrypted DTC Scenario
2,400 active wishlists, 52 tickets/month baseline #445.
After Qstomy WISH-BOT: wish_bot_resolution 87%, wish_bot_ticket_delta -52%, wish_bot_add_cart_rate 36%, wish_bot_csat 4.5/5.
Explore customer support and request a demo.
Post-add-cart Continuity
After add cart success → optional route checkout bot #292 if client asks payment same session.
Wish Training Corpus
Feed WISH-MAP + 35 anonymized WB-8 transcripts for intent bot_wish tuning. Quarterly review #445 ops.
What is the checklist for deploying WISH-BOT?
WISH-BOT Checklist (12 steps)
Validate WISH-SUP #445 + WISH-MAP /pages/wishlist
Export WISH-MAP JSON + wishlist app API read-only
Configure 12 intents bot_wish_* section 3
Implement flow WB-1 to WB-8 + wish gate WB-2
Activate guardrails no checkout impersonation + advise catalog only
Route wish vs #445 #437 #47 disambiguation
Placements T1 account wishlist + T3 FAQ + T4 back-in-stock deep link
Webhook in-stock T5 proactive reengage limit 7 d
Tests staging 8 scenarios: list cite, share, add guide, add all partial, notify, reengage, advise, handoff registry
Heart vs save disambiguation copy validated
Dashboard KPI wish_bot monthly
RAG sync WISH-MAP on policy change
At a glance
#446 = bot wishlist, not customer service agents #445
WISH-BOT: retrieve share add notify remind advice
Distinct abandonment #47: favorite intent not recovery promo
Advise grounded: max 2 SKU wish or similar catalog
KPI wish_bot_add_cart_rate: target > 30 %
FAQ
Bot vs agents #445?
#445 registry migration merge execute. #446 bot tier 1 retrieve convert remind.
Difference abandonment #47?
#47 basket exited checkout promo. #446 favorite wishlist loyalty.
What does the bot advise?
bot_wish_advise_similar in-stock favorites or 1 alternative catalog API.
Proactive reminder?
bot_wish_reengage_nudge in-stock T4 T5 max 1/SKU/7d opt-out CNIL.
Save basket #437?
bot_wish_route_scart437 WB-2 no wish record heart vs save ask.
Going further
This week: validate WISH-MAP #445, configure intents bot_wish_*, deploy widget T1 /account/wishlist, test WB-2 heart vs save disambiguation, connect webhook in-stock T5, launch dashboard wish_bot_add_cart_rate.
Share this guide #446 with loyalty and product: a bot that cites your available favorites is worth ten generic email reminders, an invented SKU recommendation is worth a deception complaint and five unsubscribes.
Go-live test matrix
8 scenarios sign-off: list empty guest merge, share private, add all 2/5 OOS, notify toggle, reengage click, advise 2 SKU, route437, handoff registry.
Enzo
July 1, 2026
