E-commerce
June 30, 2026
An email form on a coming soon page captures addresses. It does not distinguish the customer ready to buy on launch day from the curious one who will forget your brand in two weeks. Result: same email for everyone, same access window, disappointing waitlist conversion.
Alhena describes the waitlist chatbot as an active system: confirming registration, capturing size/color preferences, segmenting demand before go-live (Alhena, waitlist IA 2026). D2C Times measures 34.7% conversion with a segmented waitlist vs 6.2% for first-come, first-served (D2C Times 2026).
This guide #307 covers the product waitlist AI chatbot: qualification, priority, follow-up. It complements pre-launch support (#306) from the angle of conversational automation and scoring.
Summary
Why does a passive waitlist form underutilize pre-launch demand?
The customer leaves their email and departs. You know neither their size, nor their urgency, nor whether they will purchase at 10 AM or ignore the email drop.
Limitations of capture alone
Zero context: no variant, budget, or usage information
Identical treatment: a potential VIP is treated the same as a cold window shopper
Unanswered questions: the customer either opens the chat or leaves for a competitor
What the waitlist bot changes
TailorTalk reminds us that the value of e-commerce AI chat is primarily pre-purchase: resolving hesitation, capturing intent, and retargeting (TailorTalk, chatbot 2026). On the waitlist, the bot qualifies, scores, assigns a tier, and triggers targeted follow-ups.
Principle #307
Waitlist = conversational funnel. Each interaction enriches the profile, not just the email list.
How does it differ from support #306, out of stock #106, and guided selling #150?
Five neighboring pieces of content, five roles.
Pre-launch support (#306)
Waitlist support (#306): WAITLIST-POLICY, PRELAUNCH macros, human drop day protocol. The #307 automates qualification, scoring, and follow-ups via bot.
Out of stock (#106)
Out of stock (#106): product already launched, restock. The #307: product not yet sellable, anticipated demand.
Launch plan (#114)
Launch (#114): full cycle D-30 to D+30. The #307 zooms in on the waitlist bot module pre-drop.
Guided selling (#150)
Guided selling (#150) directs to a purchasable SKU. The #307 qualifies for future access, not immediate purchase.
Lead generation (#306 neighbor Heeya)
Heeya path distinguishes qualification (full context) and scoring (processing priority) (Heeya, chatbot leads 2026). The #307 applies this logic to the product waitlist case.
Promise #307
Intents wl_*, WAIT-SCORE model, qualification flow, bot tier, follow-ups, WAITLIST-BOT-01 prompt, conversion KPI.
Which WL-BOT-INTENT mapping for the waitlist chatbot?
The WL-BOT-INTENT taxonomy separates signup, status, qualification, and drop day.
14 bot waitlist intents
wl_signup: waitlist registration from chatwl_confirm: am I registered? (email lookup)wl_when_launch: launch date and timewl_early_access: early access ruleswl_qualify_start: qualification flow startwl_preference: size, color, variationwl_referral: referral link, tier upgradewl_tier_status: my priority levelwl_unsubscribe: unregistrationwl_specs_teaser: product info already publishedwl_drop_link: D-Day early access linkwl_sold_out_next: drop missed, next opportunitywl_alternative: similar product in stockwl_handoff: tier dispute, influencer, B2B
Routing
PDP coming soon: wl_signup + proactive wl_qualify_start after 20 s dwell. Incoming chat: Klaviyo/Shopify metafield lookup prior to tier response.
How to build the WAIT-SCORE model to prioritize registrants?
The WAIT-SCORE model scores each subscriber for Klaviyo tier and early access window.
E-commerce criteria (BANT adaptation)
ChatSpark offers Budget, Authority, Need, Timeline for B2B (ChatSpark, qualification 2026). In DTC waitlist:
Need: declared usage, product fit (+0-25 pts)
Urgency: Day-0 purchase vs curiosity (+0-25 pts)
Fit: confirmed variant, aligned budget (+0-20 pts)
Engagement: referral, quiz, email opens (+0-20 pts)
History: existing LTV customer (+0-10 pts)
Score segments
Hot 75-100: tier T0/T1, early access -48 h. Warm 40-74: T2, nurturing follow-up. Cold <40: T3, generic emails only. Heeya: A-leads called back within 1 h, C-leads in D+3 D+7 sequence (Heeya, qualifier leads 2026).
CRM Sync
Bot webhook → Klaviyo: wait_score, wait_tier, variant_pref, urgency. Identical Shopify customer metafield tag.
What five-question conversational qualification flow?
The qualification waitlist flow enriches the beneficiary profile in less than 90 seconds, without a B2B interrogation.
Typical DTC mode sequence
Usage: "For whom or for what use?" (gift, personal, professional)
Variant: "Which size / color are you interested in?"
Urgency: "Are you planning to buy as soon as it opens or are you just looking?"
Channel: "Would you prefer to be alerted by email or SMS?"
Referral opt-in: "Would you like a link to skip the line by inviting friends?"
Flow rules
Skip question if answer is already in session (PDP variant selected). Max 5 questions. End: calculated score + tier confirmation + referral CTA if Warm/Hot.
Flow end copy example
"Thank you {{name}}. You are registered in tier {{tier}} for {{product}}. Launch {{launch_date}}. Early access: {{early_window}}. Your preference {{variant}} has been saved."
How does the bot assign priority tiers and early access?
The bot tier assignment maps WAIT-SCORE to WAITLIST-POLICY rules from guide #306.
Score → tier matrix
Score ≥85 or VIP LTV customer → T0 (-48 h)
Score 65-84 or 2+ referrals → T1 (-24 h)
Score 40-64 → T2 (-6 h or H-0 code)
Score <40 → T3 (public only)
Dynamic upgrade
Validated referral: +15 pts, tier recalculation if cutoff has not passed. Completed quiz: +10 pts. D2C Times: behavioral scoring +67% conversion vs FCFS.
Bot prohibitions
Promising T0 without a score. Creating an undocumented exceptional tier. Giving an early access link before the policy window.
Which automated follow-ups to set up based on the waitlist score?
The waitlist bot follow-ups complement Klaviyo, they do not duplicate spam.
Sequences by segment
Hot (chat + email): D-7 teaser specs, D-1 personalized countdown, H-15 min early access link via SMS if opt-in.
Warm: D+3 reminder for incomplete qualification, D+7 product BTS, D-2 "only 48 hours left".
Cold: public launch email only, no proactive chat follow-ups.
Conversational triggers
Qualification abandoned at Q3 → wl_qualify_resume 24h
Hot with no email open at D-3 → chat nudge "still interested?"
Missed drop → wl_sold_out_next + wl_alternative stock SKU
PeppyDuck
Drop automation: "Available Now" email per waitlist SKU, early access preorder window, 24h post-drop reminder (PeppyDuck 2026). Bot triggers handoff if customer says "link doesn't work" on D-0.
How should the WAITLIST-BOT-01 prompt and the corpus be structured?
Extension system prompt #163, block WAITLIST-BOT-01 200-300 words.
Prompt blocks
Role: guide waitlist {{product}}, not a pushy salesperson
Corpus: WAITLIST-POLICY #306, teaser specs, tier dates
Qualification: flow 5 questions section 4 if wl_signup
Scoring: apply WAIT-SCORE, do not display raw score to customer
Prohibited: unpublished price, exact stock, unconfirmed date
Handoff: wl_handoff if tier dispute, influencer, >3 link failures
Corpus sources
Index: WAITLIST-POLICY Notion, page /pages/lancement, product teaser metafields, Klaviyo JSON calendar. Alhena: bot confirms registration, captures preferences, explains early access (Alhena 2026).
Which bot mode should be activated on drop day?
The drop day bot mode prioritizes wl_drop_link, wl_confirm, and wl_sold_out_next.
D-Day Behaviors
Email lookup → tier → early access link if window is open
Shopify API live stock: wl_alternative if preferred SKU is OOS
Virtual queue: queue ETA message if enabled
Cap of 1 link regeneration / customer / drop
Drop day bot SLA
wl_drop_link response < 10 s. Human handoff if 2 consecutive link failures. Disable qualification wl_qualify_start (registration closed).
Post-drop D+1 to D+7
Activate wl_sold_out_next for non-converted users. Offer restock alert or waitlist for the next drop. Cross-reference out of stock (#106) if the product remains OOS.
Which KPIs should be measured for the waitlist bot?
Measure qualification and conversion, not just raw sign-ups.
Monthly KPIs / per drop
wl_signup_via_bot_rate: chat sign-ups / coming soon PDP sessions
qualification_completion_rate: completed flows / wl_signup
waitlist_to_order_rate: orders / registrants (target 10-15%)
hot_share: % registrants with score ≥75
tier_upgrade_rate: referral/quiz upgrades
relance_conversion: purchases post-Warm chat nudge
wl_bot_deflection: intents resolved without human intervention
W+2 post-drop review
Compare waitlist_to_order Hot vs Cold. Adjust WAIT-SCORE weight if Hot under-converts (threshold too low) or Cold is over-represented.
How does Qstomy qualify, prioritize, and follow up with the waitlist?
Qstomy executes WL-BOT-INTENT, calculates WAIT-SCORE, syncs Klaviyo, and activates the drop day mode.
Capabilities
5-question qualification flow + variant capture
Real-time WAIT-SCORE + tier assignment
Klaviyo wl_confirm / wl_tier_status lookup
Warm chat follow-ups (qualification resume, countdown)
Drop mode: early access link + live stock wl_alternative
Handoff wl_handoff payload score + tier + prefs
Encrypted DTC Scenario
Sneaker brand, 3,800 waitlist sign-ups, 62% via bot. Before Qstomy: 12% qualification, 7.1% waitlist_to_order. After WAIT-SCORE + Warm follow-ups: 58% qualification, 22% Hot share, 13.6% waitlist_to_order, 74% wl_bot_deflection over 6 weeks pre-drop.
See sales agent, Shopify, demo.
Which playbooks should be used to deploy the waitlist bot in four weeks?
Playbook 1: WAITLIST-POLICY + corpus (3 h)
Resume #306 section 4. Index in bot. Validate dates and tiers with marketing.
Playbook 2: WAIT-SCORE + tiers (2 h)
Define section 4 criteria. Configure Klaviyo webhook. Test 10 fictional profiles.
Playbook 3: qualification flow (1 d)
Implement 5 questions from section 4. PDP coming soon triggers. Mobile QA.
Playbook 4: Warm follow-ups (4 h)
Activate section 7 sequences. Link chat nudge + Klaviyo email. No duplicate messages at the same hour.
Playbook 5: dry run drop bot (2 h)
Simulate wl_drop_link, OOS pref, handoff. Activate drop day mode section 8.
Useful linking
This week: open your coming soon page in private browsing. Does the bot offer qualification after registration? If not, playbook 3 is the priority before the next teaser.
Enzo
June 30, 2026
