E-commerce
July 1, 2026
"The chatbot says out of stock, the product page says web exclusive." "The AI suggests in-store pickup for a web-only product." "Why doesn't the bot suggest any in-store alternatives?" Three bot failures where the AI confuses web exclusivity, out-of-stock items, and cross-channel availability.
A web-exclusive e-commerce AI chatbot does not replace WEBEX-FLOW agents (#457). It reads WEBEX-MAP, explains online-only, converts to web PDP, proposes in-store alternative_sku, blocks in-store BOPIS promises, and hands off to an agent if there is a store window dispute.
This guide #458 covers bot_webex_* intents, WEBEX-BOT flow, and webex_bot KPIs. Distinct from Exclusives Customer Service (#457) and the out-of-stock bot (#245): here, the AI use case is to explain web-only, channel stock, and conversion alternatives.
Summary
Why automate web-exclusive questions with a bot?
A bot that replies "out of stock" on a permanent web-only SKU or suggests in-store BOPIS on store_eligible N reproduces customer service anti-patterns and causes a loss of pre-purchase conversions.
Webex volume and cost poorly handled in chat
On DTC brands with physical stores and online-only collaborations, "available in store" chat sessions on web-exclusive PDPs represent 8% to 14% of exclusivity traffic. Without a grounded WEBEX-MAP bot, 35% to 50% of bot responses confuse OOS and web-only.
Three risks of an unstructured webex bot
False OOS: "out of stock" instead of web-exclusive
False store promise: BOPIS or store reservation impossible
Zero alternative: abrupt refusal without WEBEX-ALT
Digital Applied estimates that clear channel messaging reduces cart abandonment by 15% to 25% on hybrid journeys (Digital Applied, omnichannel 2026). Zipchat points out that a well-configured assistant can recover 35% to 50% of lost sales by recommending substitutes with a clear reason (Zipchat, alternatives 2026).
Angle #458 vs neighboring content
CS #457: WEBEX-FLOW agents. #458 = AI automation layer.
Bot OOS #245: temporary out-of-stock substitute. #458 = web-only policy, not OOS.
AVAIL #271: cross-channel stock for the same SKU. #458 = SKU never in-store.
Omnichannel Bot #272: POS online routing. #458 = specific webex intent.
LE #221: limited edition customer service. #458 = pre-purchase web channel.
DTC fashion scale
3 physical stores, 38 webex bot sessions/month, 47% false OOS or false BOPIS baseline. After WEBEX-BOT + guardrails: webex_bot_auto_resolve 64%, webex_bot_convert_rate 46%, webex_bot_false_store_promise 0, CSAT webex bot 4.5/5.
Bot converts, does not gatekeep
WEBEX-BOT-SUP: explain web-only, then WEBEX-CONVERT PDP link, not a dry "not in store".
Collab drop day bot scale
Pre-scale WEBEX-BOT capacity and NO-FALSE-OOS review before collab online-only launch week traffic spike.
Fashion collab vertical density
Highest webex_bot_session_rate on collab drops: preload variant_online alt templates.
How does WEBEX-BOT differ from OOS #245 and SAV #457?
Temporary out-of-stock, web exclusivity and agent playbook: three distinct merchandising bot layers.
Intention u2192 bot flow matrix
#458 WEBEX-BOT: web-only explain, convert, store alt
#245 OOS bot: temporary out-of-stock SKU substitute
#457 WEBEX-FLOW: WX-1 to WX-8 agents execute dispute
#271 AVAIL: dual-channel stock lookup
#167 RESTOCK: restock ETA if temporary webex_oos
Shared WEBEX-MAP corpus
#457 publishes WEBEX-MAP JSON. #458 bot consumes the same source: webex_type, store_eligible, alternative_sku[], return_channel. Version synchronization mandatory.
Four BOT-WEBEX-TYPE flows
bot_webex_explain_convert: TPL-WEBEX-EXPLAIN + PDP link
bot_webex_alternative: alternative_sku store recommendation
bot_webex_future_store: store_future_date temporary drop
bot_webex_escalate: dispute showcase, gift blocked, hostile
Promise #458
Policy WEBEX-BOT-SUP, 12 intents bot_webex_*, flow WEBEX-BOT WB-1 to WB-8, guardrails, handoff payload, KPI webex_bot_*.
Pre-purchase chat pipeline
PDP chip u2192 WEBEX-BOT u2192 convert or alt u2192 handoff #457 if showcase dispute. Temporary OOS on web-exclusive u2192 #245 parallel if restock.
Webex bot stack
Shopify PDP context inject, WEBEX-MAP JSON RAG, Qstomy intents bot_webex_*, guardrails NO-BOPIS, inventory API alt check, convert UTM tracking, handoff Gorgias #457.
Which bot_webex_* intents should be classified?
Twelve web exclusivity bot intents aligned with webex_* typologies #457.
Twelve bot_webex intents
bot_webex_store_availability : store availability [City] ?
bot_webex_why_online_only : why not in boutique ?
bot_webex_restock_store : will arrive in store ?
bot_webex_try_in_store : showroom fitting ?
bot_webex_window_display : window display vs web-only dispute
bot_webex_alternative : similar product in store
bot_webex_oos_online : web exclusive out of stock online
bot_webex_gift_urgency : gift needed in store today
bot_webex_confusion_oos : thinks out of stock, but it's permanent
bot_webex_return_channel : return web purchase to store ?
bot_webex_pre_purchase : who guarantees web-exclusive purchase
bot_webex_variant_online : web-only color vs store range
Required bot session fields
sku_id, webex_type_map, store_city_cited, gift_urgency Y/N, confusion_oos Y/N, plv_litige Y/N, alternative_offered[], convert_link_clicked Y/N.
Bot OOS distinction #245
Inventory qty 0 + webex_permanent → explain web-only not OOS waitlist primary. qty 0 + webex_temporary or LE → route #245 or #167 restock.
Bot chat logs mining
Export 90 days of "store", "boutique", "web only", "exclusive", "window display". Prioritize intents 80% volume PDP web-exclusive badge.
Intent confidence threshold
Intent confidence below 0.75 : clarifying question store or web before WB-4 map lookup.
How does the bot consume WEBEX-MAP #457?
The bot does not reinvent exclusivity: it reads the WEBEX-MAP matrix documented in #457.
Lookup WB-4 bot
sku → webex_type: permanent, temporary_drop, collab_online, variant_online
store_eligible: N block BOPIS, Y route #271 AVAIL
store_future_date: TPL-WEBEX-FUTURE if temporary
try_in_store: showroom RDV link if Y
alternative_sku[]: bot recommend with stock check
return_channel: cite before in-store return answer
plv_store_allowed: window display empathy template if dispute
restock_policy: none vs web_only vs both
RAG corpus WEBEX-MAP
Chunks SKU + /pages/online-exclusives FAQ. Bot cites chunk_id. Hallucination store_eligible = P1 incident. See anti-hallucination (#208).
PDP badge context inject
Chat widget on web-exclusive PDP auto-inject sku_id WEBEX-MAP. Chip « Available in store? » triggers bot_webex_store_availability without repeat SKU ask.
Shopify catalog channel
Online Store only catalog flag sync store_eligible N. MB fallback if RAG timeout under 2 s.
Alternative stock live check
WB-7 alternative_sku: verify inventory before recommend. Never alt also OOS. Kn8 pattern live inventory query.
Chunk_id citation audit
Weekly sample 20 bot_webex transcripts verify WEBEX-MAP chunk match store_eligible. Zero hallucination tolerance.
Metafield webex_type Shopify
SKU metafield webex_type mirror WEBEX-MAP WB-4 fallback if RAG timeout under 2 s SLA.
How to write the WEBEX-BOT-SUP policy in eight rules?
The WEBEX-BOT-SUP web exclusivity bot policy governs AI conversion without making false store promises.
Eight WEBEX-BOT-SUP Rules
WEBEX-MAP only: exclusive alternative dates from JSON zero invent
Explain before decline: TPL-WEBEX-EXPLAIN before "non magasin"
Convert web first: PDP link UTM webex_bot every store request path
Alternative if map: alternative_sku[] mandatory recommend if non empty
NO-BOPIS guard: block pickup store if store_eligible N
Dual channel WB-2: store_eligible Y → handoff AVAIL #271 not webex bot
Escalate window dispute: bot_webex_window_display → agent #457 supervisor
Handoff payload WX-1: sku city gift dispute flags prefill agent
False OOS ban
webex_permanent in stock online: never "épuisé". TPL-WEBEX-EXPLAIN web exclusivity + convert link.
Gift urgency path
bot_webex_gift_urgency: express shipping cite if eligible + WEBEX-ALT immediate store mandatory branch.
Return channel grounded
bot_webex_return_channel: return_channel map cite. No instore return promise if web_return_only.
Merch sign-off bot templates
Marketing approve TPL-WEBEX-EXPLAIN and FUTURE before prod. PLV alignment plv_store_allowed quarterly audit.
How to apply the WEBEX-BOT flow in eight steps?
The WEBEX-BOT WB-1 to WB-8 flow structures the bot qualification exclusively grounded in WEBEX-MAP.
Eight steps WB-1 to WB-8
WB-1 Intent classify: bot_webex_* typology section 3
WB-2 Dual canal gate: store_eligible Y ? route AVAIL #271 stop WEBEX-BOT
WB-3 PDP context: sku_id from page inject or order history
WB-4 WEBEX-MAP lookup: type eligible alternatives future date
WB-5 Explain respond: TPL-WEBEX-EXPLAIN grounded map
WB-6 Branch: convert | alternative | future store | try showroom | escalate window | OOS restock
WB-7 Execute: PDP link | alt SKU cards | RDV | handoff agent | #245 #167
WB-8 Log: intent, branch, convert_click, alt_click, handoff Y/N, map_version
WB-6 convert branch
TPL-WEBEX-CONVERT: PDP link UTM webex_bot, delivery ETA, return_channel, size guide link if hesitation.
WB-6 alternative branch
alternative_sku[] with live stock: 2 cards max reason "available in store [city]" or "same range". Click track alt_click.
WB-6 confusion_oos branch
bot_webex_confusion_oos: clarify permanent web-only vs temporary OOS. Permanent → convert. Temporary → #167 ETA or #245 alt.
WB-6 window escalate
bot_webex_window_display: TPL-WEBEX-EMPATHY + convert offer + handoff agent plv_litige merchandise alert flag.
WB-7 oos_online branch
webex_oos online qty 0: restock_policy web_only → #167. LE none → #221. Alt SKU if available.
WB-5 before WB-6 sequence
Compliance audit: TPL-WEBEX-EXPLAIN always before convert or alt branch. Violations hotfix 24 h.
SLA bot response webex
WB-5 explain target under 8 s. Window handoff agent escalate path under 60 s.
Which bot templates and guardrails should be configured?
Eight WEBEX bot templates and NO-BOPIS NO-FALSE-OOS guardrails.
TPL-WEBEX-EXPLAIN (why online-only)
"[SKU] is a web exclusive [webex_type grounded]. [Reason map]. Available to order: [PDP link]."
TPL-WEBEX-CONVERT (convert web)
"Exclusive web order: [PDP link]. Delivery [ETA]. Returns: [return_channel]. Size guide: [link]."
TPL-WEBEX-ALT (alternative)
"Not in store. Alternative: [alt SKU] available [channel]. Compare: [link]."
TPL-WEBEX-FUTURE (temporary drop)
"Web exclusive until [store_future_date], then stores. Today: [PDP link] or [alt]."
TPL-WEBEX-GIFT (urgent gift)
"Express delivery [ETA cutoff]. Immediate store alternative: [alt] [store]."
Guardrail NO-BOPIS-01
Block pickup BOPIS template if store_eligible N. Force TPL-WEBEX-CONVERT or TPL-WEBEX-ALT.
Guardrail NO-FALSE-OOS-01
Block "out of stock" if webex_permanent + qty online > 0. Force TPL-WEBEX-EXPLAIN.
Bot touchpoints
PDP chip "Available in store?" web-exclusive badge pages
Store locator "Online Exclusive" filter message
Help center /pages/online-exclusives bot RAG
Post-view Klaviyo browse abandon webex SKU
TPL-WEBEX-EMPATHY window display
"I understand the window display confusion. Web exclusive, order [link] or alternative [alt]. Team notification sent."
Which showcase, variant, and OOS overlap cases should be processed?
Special webex bot cases require guardrail override or agent handoff #457.
Dispute window display
bot_webex_window_display: empathy TPL-WEBEX-EMPATHY, never blame client. Escalation to supervisor if hostile review threat.
Web-only color variant
bot_webex_variant_online: same model other colors store_eligible Y. WB-7 alt cards store color + web color PDP compare.
Overlap OOS bot #245
Temporary OOS web-exclusive SKU: WB-6 route #245 online substitute or #167 restock ETA. Not permanent web-only messaging.
Overlap AVAIL #271 mis-route
Client asks wrong SKU dual channel: WB-2 detect store_eligible Y, handoff AVAIL lookup not WEBEX explain.
Try in store showroom
try_in_store Y: RDV link location. N: convert or alt, no false fitting promise.
LE + web exclusive overlap #221
restock none: bot cites LE policy. No false store future date.
Express shipping gift
express_eligible map flag required before same-day ETA cite. No invent cutoff.
Omnichannel bot #272 disambiguation
General omnichannel intent on webex PDP: priority bot_webex_* over generic avail. Intent classifier SKU badge weight.
Browse abandon trigger
Klaviyo browse abandon webex SKU: proactive bot TPL-WEBEX-CONVERT if session viewed PDP badge no purchase 24 h.
Which Webex bot KPIs should be measured?
The web exclusivity bot KPIs link conversion, auto-resolve, and zero false store promise.
Eight key metrics
webex_bot_session_rate: bot_webex sessions / 100 PDP web-exclusive views
webex_bot_auto_resolve: resolved without agent / sessions
webex_bot_convert_rate: purchases 48 h post convert link click / sessions
webex_bot_alt_click_rate: alt SKU click / store request sessions
webex_bot_false_store_promise: BOPIS reserve promise / sessions (target 0)
webex_bot_false_oos: out of stock on permanent in stock / sessions (target 0)
webex_bot_handoff_rate: agent escalation / sessions
webex_bot_csat: satisfaction post bot_webex session
DTC bot webex Benchmark
webex_bot_auto_resolve 55-68%, webex_bot_convert_rate 40-50%, webex_bot_false_store_promise 0, webex_bot_csat > 4.3/5.
Weekly bot ops Dashboard
Intent breakdown, WB-6 branch, convert vs alt path, false OOS incidents, vitrine handoff rate by store.
A/B TPL-WEBEX-CONVERT
4 weeks structured convert template vs ad hoc: measure webex_bot_convert_rate lift.
webex_bot_convert click attribution
UTM webex_bot on PDP link correlate 48 h purchase webex_bot_convert_rate dashboard.
Segmentation by webex_type bot
Dashboard webex_bot_convert_rate per permanent vs collab vs variant optimize TPL per branch.
Which Webex bot anti-patterns should be avoided?
Twelve web-exclusive bot anti-patterns to ban from production.
1. "Out of stock" on web-only in stock
NO-FALSE-OOS-01 guardrail. TPL-WEBEX-EXPLAIN mandatory.
2. BOPIS offer store_eligible N
NO-BOPIS-01 block. Rule 5 WEBEX-BOT-SUP.
3. Decline without alternative
Rule 4 alternative_sku[] if map populated.
4. Skip WB-2 dual channel
store_eligible Y → AVAIL #271 not webex.
5. Inventory store_future_date
Rule 1 WEBEX-MAP only dates.
6. Alt SKU OOS recommend
WB-7 live stock check before card.
7. In-store return without return_channel
bot_webex_return_channel map cite.
8. Dispute window loop
Escalate to agent after empathy once.
9. Mix OOS #245 on permanent
webex_permanent ≠ waitlist primary path.
10. Stale WEBEX-MAP corpus
Deploy bot without #457 sync = contradict PDP badge.
11. Empty handoff payload
Rule 8 WX-1 fields agent prefill.
12. Denigrate store tone
Convert to web professional, not "store has nothing".
13. Wholesale catalog mix
B2B SKU separate catalog: route wholesale not bot_webex consumer messaging.
How does Qstomy implement WEBEX-BOT?
Qstomy on Shopify runs WEBEX-BOT: WB-2 dual-channel gate, WEBEX-MAP RAG lookup, TPL-WEBEX-EXPLAIN auto, NO-BOPIS NO-FALSE-OOS guardrails, alternative live stock cards, convert PDP link UTM webex_bot, handoff #457 storefront payload.
Qstomy webex bot capabilities
webex_map_rag_bot: type eligible alternatives grounded
webex_explain_template_bot: TPL-WEBEX-EXPLAIN auto
webex_no_bopis_guard: block pickup store_eligible N
webex_no_false_oos: block out-of-stock permanent in stock
webex_alt_stock_live: alternative_sku inventory check
webex_convert_link: PDP UTM prefill
Pipeline #457 #458 #245 #271
#457 WEBEX-MAP source. #458 bot automation. #245 temporary OOS. #271 AVAIL dual channel. Shared PDP badge corpus.
Quantified DTC Scenario
3 stores mode, 38 webex bot sessions/month, 47 % false OOS or BOPIS baseline generic bot.
After WEBEX-BOT-SUP + Qstomy PDP chip: webex_bot_auto_resolve 66 %, webex_bot_convert_rate 47 %, webex_bot_false_store_promise 0, webex_bot_csat 4.6/5.
Explore customer support and request a demo.
AI Merchandising Governance
WB-8 logs feed AI governance (#124) review webex_bot_false_oos monthly zero tolerance.
Weekly webex bot compliance
Audit WB-5 explain sequence 100 % sample. Zero false BOPIS false OOS transcripts.
What checklist is needed to deploy WEBEX-BOT?
WEBEX-BOT Checklist (12 steps)
Validate WEBEX-MAP #457 complete web-exclusive SKU
Index RAG /pages/online-exclusives + PDP badges
Draft policy WEBEX-BOT-SUP 8 rules
Configure 12 intents bot_webex_* classifier
Implement WB-1 to WB-8 + guardrails NO-BOPIS NO-FALSE-OOS
Templates TPL-WEBEX-* grounded map
PDP chip "Store availability?" deploy
WB-2 dual channel handoff AVAIL #271
Alternative live stock check WB-7
Handoff payload #457 storefront test 8 scenarios
Dashboard KPI webex_bot section 9
Sync WEBEX-MAP bot version deploy pipeline
In brief
#458 = bot webex, not CS execute #457
WEBEX-MAP shared: same JSON #457
NO-BOPIS guard: store_eligible N
Convert not decline: TPL-WEBEX-CONVERT every path
KPI webex_bot_convert_rate: target > 42 %
FAQ
Can the bot confirm store stock for web-only?
No if store_eligible N. TPL-WEBEX-EXPLAIN + convert or alt.
Difference with #245 OOS?
#245 target temporary out of stock substitute. #458 target web-only permanent policy or channel.
Difference with #457?
#457 storefront dispute agents. #458 bot explain convert handoff.
Product out of stock online web exclusive?
WB-6 restock #167 or alt #245, not permanent web-only message.
Storefront dispute?
TPL-WEBEX-EMPATHY + handoff agent #457 P1.
Go further
This week: sync WEBEX-MAP #457 into bot RAG, deploy intents bot_webex_*, activate NO-BOPIS guardrail, PDP chip web-exclusive pages, test convert link tracking, connect handoff #457 storefront, launch dashboard webex_bot_convert_rate.
Share this guide #458 with bot ops and merchandising: a NO-FALSE-OOS guardrail is worth ten lost customers who believe in a stockout, a TPL-WEBEX-ALT with live stock is worth a frustrated store visit turned into an alternative purchase or web conversion.
Go-live bot test matrix
8 scenarios: permanent explain convert, NO-BOPIS block, alt live stock, confusion OOS clarify, future date temporary, storefront empathy handoff, dual channel 271 route, gift express alt.
Enzo
July 1, 2026
