E-commerce
July 1, 2026
"The bot promises delivery on March 15th while the tier is TBC." "The AI says I can pre-order without a preorder map flag." "The chatbot confuses a coming soon alert with the VIP early access campaign #306." Three failures where a miscalibrated coming soon bot invents dates, promises early purchase, or mixes up waitlist SKUs and pre-launch strategy.
An AI chatbot for upcoming products does not replace COMINGSOON agents (#661). It reads COMINGSOON-MAP, cites launch_status API, collects waitlist interest, and hands off date_slipped preorder specs to humans.
This guide #662 covers bot_coming_soon_* intents, the COMINGSOONbot flow, and coming_soon_bot KPIs. Pair this bot with the COMINGSOON playbook (#661). AI use case: collecting interest and explaining timelines without false promises.
Summary
Why automate the coming soon with a bot?
"When can I buy?", "why is the button greyed out?" and "notify me at launch" return on coming soon pages. A calibrated bot quotes COMINGSOON-MAP launch_eta_tier waitlist_url without a firm date if TBC.
What the bot resolves tier 1 pre-purchase
Explain not buyable: no_purchase_copy customer_communication map
ETA tier cite: launch_status launch_date_range map
Waitlist guide: waitlist_url signup alert map
Interest collect: email capture handoff CRM map
Preorder check: preorder_available Y/N cite map
Gorgias estimates that 18 to 28% of coming soon page tickets concern dates and waitlists, which are resolvable by a grounded bot without an agent (Gorgias, Customer Support 2026).
COMINGSOONbot vs COMINGSOON #661, prelaunch #307, OOS bot and preorder #187
Five contents, five distinct availability statuses.
Quick matrix
#662 COMINGSOONbot: tier 1 bot explain ETA collect handoff
#661 COMINGSOON: agents date_slipped preorder escalate merch
Waitlist bot #307: campaign tiers VIP drop day distinct page SKU
OOS bot alternatives: out of stock post-sales distinct never launched
Preorder #187: customer paid waiting ship distinct non-sellable
Pipeline: #662 bot explain collect tier 1 → #661 agents slipped preorder specs CS-7.
Which bot_coming_soon_* intents should be configured?
Eight bot coming soon intents mapped to typologies coming_soon_* #661.
Eight bot_coming_soon intents
bot_coming_soon_explain: no_purchase_copy customer_communication map
bot_coming_soon_eta: launch_eta_tier launch_date_range cite map
bot_coming_soon_why_not_buy: sellable_flag N explain map
bot_coming_soon_waitlist: waitlist_url guide sign-up map
bot_coming_soon_interest_collect: email capture CRM waitlist map
bot_coming_soon_preorder_check: preorder_available Y/N cite map
bot_coming_soon_specs: specs price pre-launch map cite
bot_coming_soon_handoff: date_slipped preorder specs → #661
Tier 1 auto: explain, eta, why_not_buy, waitlist, interest_collect if COMINGSOON-MAP.
bot_coming_soon_handoff coming_soon_date_slipped preorder_ask → agents #661 payload sku email.
How to consume COMINGSOON-MAP #661?
The bot reads COMINGSOON-MAP #661: comingsoon_program_id, sellable_flag, launch_status, launch_eta_tier, launch_date_range, waitlist_url, preorder_available, customer_communication_copy, no_purchase_copy, update_notification_policy, alternative_sku_ids.
Lookup grounded
LAUNCH-STATUS-CITE-BOT: launch_status metafield API before respond
NO-FIRM-DATE-TBC-BOT: no firm date if tier TBC map
NO-PREORDER-PROMISE-BOT: preorder only if preorder_available Y map
INTEREST-COLLECT-BOT: email waitlist collect no order executed
PRELAUNCH307-REROUTE-BOT: VIP drop tiers → #307 waitlist bot distinct SKU campaign
OOS106-REROUTE-BOT: sold then out of stock → distinct OOS bot never launched
COMINGSOON661-HANDOFF-BOT: slipped preorder → #661 CS-7 agents
Anti-hallucination (#123) alignment: ETA waitlist = COMINGSOON-MAP whitelist only.
COMINGSOONBOT-SUP policy in six rules
Six bot rules coming soon for sure.
COMINGSOON-MAP-GROUNDED-BOT: ETA waitlist preorder from map only
LAUNCH-STATUS-CITE-BOT: launch_status launch_eta_tier API before respond
NO-FIRM-DATE-TBC-BOT: tier TBC = launch alert no promised date
NO-PREORDER-PROMISE-BOT: bot does not create preorder order without Y flag
INTEREST-COLLECT-ONLY-BOT: email waitlist collect handoff CRM map
SLIP-HANDOFF-BOT: date_slipped preorder complex → #661 CS-7 agents
Flow COMINGSOONbot CSB-1 to CSB-8
Eight-step flow coming soon product bot.
CSB-1 Classify: bot_coming_soon_* intent detect PDP coming soon
CSB-2 Collect: sku email interest preorder question
CSB-3 COMINGSOON-MAP: launch status ETA waitlist preorder alt
CSB-4 Launch lookup: launch_status metafield API map
CSB-5 Guardrail: LAUNCH-STATUS NO-FIRM-DATE NO-PREORDER INTEREST-COLLECT
CSB-6 Respond: TPL-COMINGSOONbot grounded map API
CSB-7 Handoff: slipped preorder specs exception → #661
CSB-8 Log: intent comingsoon_program_id tag coming_soon_bot interest Y/N
Example TPL-COMINGSOONbot-ETA
“Product [sku]: [customer_communication_copy map]. Tier purchase availability [launch_eta_tier map]. [confirmed: [launch_date_range map].] [TBC: no firm date, alert as soon as open.] Registration: [waitlist_url map]. NO-FIRM-DATE-TBC-BOT.”
TPL-COMINGSOONbot and touchpoints templates
Four essential templates.
TPL-COMINGSOONbot-EXPLAIN
Program [comingsoon_program_id]: [no_purchase_copy map]. [customer_communication_copy map]. sellable_flag N until launch. Alternative available: [alternative_sku_ids map links].
TPL-COMINGSOONbot-ETA
Launch tier [launch_eta_tier map]. [launch_date_range map if confirmed or estimated.] [TBC: date not confirmed, alert via waitlist.] NO-FIRM-DATE-TBC-BOT.
TPL-COMINGSOONbot-WAITLIST
Get notified: [waitlist_url map]. INTEREST-COLLECT-BOT: email [collect] → CRM waitlist map. Distinct early access VIP: PRELAUNCH307-REROUTE if tier campaign map.
TPL-COMINGSOONbot-HANDOFF
Request [report date / pre-order / detailed specs] forwarded to team. Summary [sku email question]. Agent SLA [handoff_sla map].
Touchpoints
PDP coming soon badge: proactive bot_coming_soon_explain widget
Grayed-out buy button: bot_coming_soon_why_not_buy trigger
Chat keyword "coming soon": bot_coming_soon_eta entry
Waitlist CTA click: bot_coming_soon_interest_collect assist
Edge cases and reroutes
Five cases outside tier 1 bot coming soon standard.
VIP early access campaign: PRELAUNCH307-REROUTE-BOT #307 distinct page SKU
Pre-order open: bot_coming_soon_preorder_check link #187 if preorder_available Y
SKU launched on D-day: #114 active launch reroute purchase
Post-launch out of stock: OOS106-REROUTE bot alternatives
Specs not revealed: bot_coming_soon_handoff #661 merch policy
Bot never creates pre-order: agents #661 or checkout if preorder_available Y map.
Essential coming_soon_bot KPIs
Five steering metrics for COMINGSOONbot.
coming_soon_bot_explain_deflect: explain ETA resolved without agent
coming_soon_bot_launch_cite_rate: % responses LAUNCH-STATUS-CITE map
coming_soon_bot_interest_collect_rate: waitlist emails collected / bot sessions
coming_soon_bot_handoff_rate: slipped preorder specs / total bot
coming_soon_bot_date_promise_violations: promised date tier TBC audit target 0
Target: coming_soon_bot_date_promise_violations 0 and coming_soon_bot_interest_collect_rate greater than 40%.
Anti-patterns COMINGSOONbot
Five common mistakes bot coming soon.
Invented date tier TBC: NO-FIRM-DATE-TBC-BOT launch_eta_tier map
Preorder promised bot: NO-PREORDER-PROMISE-BOT preorder_available Y only
Confusing campaign #307: PRELAUNCH307-REROUTE tiers VIP distinct waitlist SKU
Confusing OOS #106: never launched distinct after-sales out of stock
Order created bot: INTEREST-COLLECT-ONLY email waitlist no checkout
COMINGSOONbot with Qstomy
Qstomy on Shopify: detect bot_coming_soon intent, COMINGSOON-MAP RAG grounded, launch_status API lookup, interest collect CRM, handoff #661 slipped preorder payload.
Pipeline: #662 bot explain collect tier 1 → #661 agents date_slipped preorder merch.
Explore AI support and book a demo.
Checklist, FAQ and going further
COMINGSOONbot Checklist (8 steps)
Sync COMINGSOON-MAP #661: RAG bot PDP coming soon widget
Policy COMINGSOONBOT-SUP: 6 rules NO-FIRM-DATE NO-PREORDER-PROMISE
8 intents bot_coming_soon_*: flow CSB-1 to CSB-8
4 templates TPL-COMINGSOONbot-*: EXPLAIN ETA WAITLIST HANDOFF
launch_status API sync: Shopify metafield bot agents
Waitlist CRM connect: CSB-6 interest collect pipeline
Red team 10 prompts: date promised preorder bot VIP confused OOS
Dashboard KPI: coming_soon_bot_* section 9
FAQ
Difference #661?
#661 = agents date_slipped preorder specs escalate merch. #662 = bot tier 1 explain collect handoff.
Bot takes an order?
No. INTEREST-COLLECT-ONLY email waitlist. Preorder if preorder_available Y link #187 checkout.
Early access VIP?
PRELAUNCH307-REROUTE-BOT #307 distinct tier campaign SKU alert coming soon.
Date not confirmed?
TPL-COMINGSOONbot-ETA tier TBC NO-FIRM-DATE-TBC-BOT waitlist launch alert.
Going further
This week: index COMINGSOON-MAP RAG, embed PDP coming soon widget, red team date promised tier TBC bot.
Enzo
July 1, 2026
