E-commerce
1 juillet 2026
« Où est ma liste de favoris ? » « Mon article favori est de retour, comment l'acheter ? » « Que me conseillez-vous parmi mes envies ? » Trois messages où un client wishlist sans self-service ouvre un ticket alors que WISH-MAP, le lien liste et le statut stock contiennent déjà la réponse conversion.
Un chatbot IA wishlist e-commerce ne remplace pas WISH-FLOW agents (#445). Il lit WISH-MAP, cite liste et items grounded, guide add to cart et alerte stock, relance retour disponible et conseille alternatives catalogue, puis route registry migration et guest merge complex vers #445.
Ce guide #446 couvre intents bot_wish_*, flow WISH-BOT et KPI wish_bot. Distinct du SAV wishlist (#445) et de relance abandon (#47) : ici, cas d'usage IA fidélisation : relancer, conseiller et convertir l'envie wishlist en commande.
Sommaire
Pourquoi un bot wishlist réduit-il les tickets fidélisation ?
Un ticket wishlist évitable naît quand le client ne trouve pas liste, partage, add to cart ou alerte stock avant d'écrire au support fidélisation.
Cinq déclencheurs tickets wish botifiables
Retrieve list : liste compte ou invité perdue
Share link : partager famille registry
Add to cart howto : bouton favori panier
OOS notify : activer alerte retour stock
Relance conversion : favori dispo, conseil achat
Klaviyo estime que les clients wishlist relancés convertissent 2 à 3 fois plus (Klaviyo, wishlist 2026). Tidio note qu'un bot tier 1 wishlist réduit tickets retrieve et share de 48 à 58 % vs FAQ statique (Tidio, chat stats 2026). Gorgias documente assistants post-achat et favoris multi-intent (Gorgias, assistant 2026).
Angle #446 vs contenus voisins
SAV wish #445 : WISH-FLOW registry merge migration execute. Le #446 = bot tier 1 retrieve share add notify relance.
Abandon #47 : recovery panier sorti checkout promo. Le #446 = favori volontaire intent différé.
Bot save #438 : restore panier save #437. Le #446 = liste produits heart pas cart token.
Back in stock : alertes retour stock générales. Le #446 = notify depuis favori wish context.
Reco contextuelles : setup moteur conversion. Le #446 = conseil grounded items wishlist client.
Exemple DTC
Mode 2 400 wishlists actives, 52 tickets/mois baseline #445. Après 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 relance
Nov-Dec wish volume 3x : scale T5 reengage and T1 widget capacity pre-holiday.
En quoi WISH-BOT diffère-t-il de WISH-FLOW #445 et abandon #47 ?
Bot wishlist, playbook agents wish et recovery abandon : trois couches intent achat différé distinct.
Matrice bot wish → rôle
#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
Router upstream
« Ma wishlist », « liste favoris », « partager liste », « ajouter favori panier », « alerte stock favori », « mon envie disponible » → WISH-BOT. « Registry migration app », « merge invité échoué ops », « share regen 10x » → handoff #445 WB-7. « Relance panier abandonné promo » sans wish → #47.
Données WISH-BOT
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.
Promesse #446
Policy WISH-BOT, 12 intents bot_wish_*, flow WB-1 à WB-8, guardrails no checkout impersonation, KPI wish_bot_*.
Relance vs abandon
bot_wish_reengage_nudge : item wish back in stock or price drop event API. Distinct abandon discount recovery tone fidélisation not urgency sortie checkout.
Shared cart #444 boundary
Co-achat panier live → SHCART-BOT #444. WISH-BOT heart favori list only.
Quels intents bot_wish_* configurer ?
Douze intents bot wishlist couvrent tier 1 retrieve conversion et routing.
Douze intents bot_wish
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 ligne 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
Tags session
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 « Aide liste ». T2 : keyword wishlist favoris liste souhaits cœur. 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. Conseil grounded 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.
Comment appliquer le flow WISH-BOT en huit étapes ?
Le flow WISH-BOT guide wishlist grounded WISH-MAP #445 et app API.
Huit étapes WB-1 à WB-8
WB-1 Accueil : « Je vous aide sur votre liste de favoris : retrouver, partager, acheter. »
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 Clore/handoff : registry migration → #445 WF-6
WB-5 list_cite flow
Items found → bot_wish_list_cite N favoris 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] de votre liste est disponible » + add cart deep link. No discount invent unless WISH-MAP promo event API.
WB-6 advise_similar
Client asks conseil 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.
Quelle policy WISH-BOT documenter ?
La policy bot wishlist WISH-BOT reprend WISH-SUP #445 avec garde-fous IA conversion.
Huit règles WISH-BOT
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 règle 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
Relance no abandon tone : fidélisation not panic discount unless policy API
Max 8 turns wish flow : puis CTA wishlist or handoff #445
Corpus RAG sources
/pages/wishlist, WISH-MAP #445, WISH-SUP #445, macros WISH-LIST WISH-SHARE from #445 section 7.
Relance vs spam
bot_wish_reengage_nudge max 1 proactive per SKU per 7 j same customer. Opt-out link marketing cite CNIL.
Revue mensuelle bot wish
Audit : wrong list count, share PII leak, advise hallucination SKU, abandon misroute, discount invent.
Sync ops app migration
Wishlist app switch window : bot honest « service liste maintenance » handoff #445 not invent items.
Quels guardrails protègent conversion et catalogue ?
La matrice bot wish autorisé vs interdit protège confiance fidélisation et exactitude produit.
Actions autorisées bot
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
Relance in-stock wish item deep link
Advise 1-2 SKU catalog API wish or similar collection
Guest merge guide merge_on_login steps
Actions interdites bot
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 : « Parmi vos favoris disponibles : [SKU name] [price] » or « Alternative : [SKU] » from catalog JSON. Voir prévention hallucinations.
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 relance opt-in
T5 proactive requires marketing consent flag customer. No nudge without opt-in wish alerts.
Comment brancher WISH-MAP #445 et app wishlist Shopify ?
L'intégration bot wishlist combine WISH-MAP, wishlist API et catalog lookup.
Champs read WISH-BOT
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
Apps Swym Wishlist Plus exposent API items et 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.
Integration Qstomy
Voir intégration Shopify + 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 + rupture (#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.
Quels triggers relance, UX et disambiguation configurer ?
Le déploiement UX WISH-BOT maximise retrieve conversion et relance fidélisation.
Cinq placements widget
/account/wishlist T1 : « Aide ma liste » chip WB-1
/pages/wishlist T3 : bot embed FAQ + lookup
PDP post-heart T2 : « Voir ma liste » 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 « Favori cœur ou panier enregistré ? » routes WISH-BOT vs SCART-BOT #438. Reduces misroute 40 %.
Add all inline helper
Wishlist page « Tout ajouter » 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.
Conseil chip on list page
« Que choisir parmi mes favoris ? » → 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 relance copy WB-6
Variant A « disponible » vs B « de retour » : measure wish_bot_reengage_convert 4 semaines.
Quels KPI wish bot mesurer ?
Les KPI bot wishlist lient deflection, conversion favori → panier et relance quality.
Huit métriques clés
wish_bot_resolution_rate : résolu sans handoff / sessions wish_bot
wish_bot_ticket_delta : baisse tickets #445 vs baseline
wish_bot_add_cart_rate : add cart click post bot / convert sessions
wish_bot_reengage_convert : order within 7 j 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
Benchmark DTC
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.
Dashboard mensuel
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.
Fidélisation cohort
LTV wish_bot engaged vs non-bot wish users. Target +10 % repeat purchase 90 j post bot session.
T4 email to bot conversion
Track back-in-stock email deep link → bot session → add cart. Target T4 convert > 15 %.
Quels anti-patterns éviter sur bot wishlist ?
Douze anti-patterns bot wishlist à bannir.
1. Abandon discount on wish
Règle 7 relance fidélisation not #47 panic promo.
2. Confondre save #438
WB-2 wish gate. SCART restore wrong object.
3. Agent add to cart API
Règle 4 guide UI only WISH-SUP.
4. Invent list items
Règle 2 WB-5 API grounded.
5. Public share private list
share_mode private WISH-MAP uphold.
6. Advise random catalog
Règle 6 max 2 wish context or similar collection.
7. Skip WISH-SUP #445 prérequis
/pages/wishlist WISH-MAP before bot deploy.
8. Relance spam same SKU
Max 1 proactive per SKU per 7 j.
9. Registry ops on bot
wish_registry_event complex → handoff #445.
10. Locked price promise
bot_wish_price_delta current price WISH-SUP règle 6.
11. Ignore guest merge
bot_wish_guest_merge_guide T1 post-login empty list.
12. Shared cart #444 confusion
Co-achat panier ≠ wishlist heart. Disambiguate WB-2.
13. Bot replaces Klaviyo entirely
Erreur : bot T5 only no email back-in-stock. Multi-canal complement not replace.
Comment Qstomy automatise la wishlist et la conversion ?
Qstomy sur Shopify exécute 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 champs pré-remplis.
Capacités bot_wish Qstomy
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 prérequis. #446 bot tier 1 deflect 85 %+ retrieve share convert. Shared policy human registry migration.
Scénario DTC chiffré
2 400 wishlists actives, 52 tickets/mois baseline #445.
Après WISH-BOT Qstomy : wish_bot_resolution 87 %, wish_bot_ticket_delta -52 %, wish_bot_add_cart_rate 36 %, wish_bot_csat 4,5/5.
Explorez support client et demander une démo.
Continuity post-add-cart
After add cart success → optional route checkout bot #292 if client asks paiement same session.
Corpus entraînement wish
Feed WISH-MAP + 35 transcripts WB-8 anonymisés pour intent bot_wish tuning. Revue trimestrielle #445 ops.
Quelle checklist pour déployer WISH-BOT ?
Checklist WISH-BOT (12 étapes)
Valider WISH-SUP #445 + WISH-MAP /pages/wishlist
Export WISH-MAP JSON + wishlist app API read-only
Configurer 12 intents bot_wish_* section 3
Implémenter flow WB-1 à WB-8 + wish gate WB-2
Activer guardrails no checkout impersonation + advise catalog only
Router 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 j
Tests staging 8 scénarios : list cite, share, add guide, add all partial, notify, reengage, advise, handoff registry
Heart vs save disambiguation copy validated
Dashboard KPI wish_bot mensuel
RAG sync WISH-MAP on policy change
En bref
#446 = bot wishlist, pas SAV agents #445
WISH-BOT : retrieve share add notify relance conseil
Distinct abandon #47 : favori intent pas recovery promo
Advise grounded : max 2 SKU wish ou similar catalog
KPI wish_bot_add_cart_rate : cible > 30 %
FAQ
Bot vs agents #445 ?
#445 registry migration merge execute. #446 bot tier 1 retrieve convert relance.
Différence abandon #47 ?
#47 panier sorti checkout promo. #446 favori wishlist fidélisation.
Bot conseille quoi ?
bot_wish_advise_similar in-stock favoris ou 1 alternative catalogue API.
Relance proactive ?
bot_wish_reengage_nudge in-stock T4 T5 max 1/SKU/7j opt-out CNIL.
Panier save #437 ?
bot_wish_route_scart437 WB-2 no wish record heart vs save ask.
Aller plus loin
Cette semaine : validez WISH-MAP #445, configurez intents bot_wish_*, déployez widget T1 /account/wishlist, testez WB-2 heart vs save disambiguation, connectez webhook in-stock T5, lancez dashboard wish_bot_add_cart_rate.
Partagez ce guide #446 avec fidélisation et product : un bot qui cite vos favoris disponibles vaut dix relances e-mail génériques, un conseil SKU inventé vaut une plainte tromperie et cinq désabonnements.
Go-live test matrix
8 scénarios sign-off : list empty guest merge, share private, add all 2/5 OOS, notify toggle, reengage click, advise 2 SKU, route437, handoff registry.
Enzo
1 juillet 2026
