E-commerce
July 1, 2026
A "coming soon" product generates interest, but also a lot of questions. The customer wants to know when they can buy it, if they can reserve it, if the price is confirmed, or if there is an alternative.
The chatbot can capture this interest without overpromising. It must explain the product status, collect useful requests, offer an alert or pre-order if available, and remain clear about uncertain lead times.
This guide explains how to manage "coming soon" products with an AI chatbot, to transform waiting into a useful relationship.
Summary
Why do coming soon products generate so many questions?
The customer sees a product they are interested in, but cannot buy it immediately. This situation creates a tension: they want to wait, but they do not want to miss the launch or waste time if the date remains vague.
The chatbot must therefore provide a reference point without making up a date. It must state what is confirmed, what remains estimated, and how the customer can be notified.
A product that will soon be available must be explained as a promise in preparation, not as stock that is already guaranteed.
Convert over 2,000 customers on average per month with Qstomy.
The world’s 1st Shopify AI dedicated to customer conversion
Empowering 200+ e-commerce merchants
What information should be checked?
The bot must know the product status, estimated date, level of certainty, pre-order availability, price, planned variants, expected quantities, and available alternatives.
It must also know if the product is a launch, a restock, a limited edition, or a test. The level of expectation and the response are not the same.
How to explain an estimated delay?
The response must distinguish between a confirmed date and an estimate. The bot can say: "The launch is planned around [period], but the exact date is not yet confirmed."
This honesty avoids creating disappointment if production, supplier delivery, or quality validation is delayed.
How do you collect interest?
The chatbot can offer an email, SMS, or customer account alert. It can also ask which variant interests the customer: size, color, model, use, or quantity.
This information helps the brand estimate actual demand. However, it must be collected without turning the conversation into a survey that is too long.
For the customer, this collection must have a visible value: being notified earlier, receiving the right variant, or obtaining a relevant alternative if the launch is delayed.
What if the customer wants to buy now?
If the pre-order exists, the bot must explain the conditions: payment, lead time, cancellation, limited quantity, and estimated shipping date. If it does not exist, it can offer an alert or a close alternative.
It must not lead customers to believe a product can be reserved if the shop does not allow it. A clear expectation is better than a vague promise.
Which flow to follow?
The flow must transform interest into the next action.
Identify the product and the variant that interest the customer.
Read the status: launch, restock, pre-order, or limited edition.
Explain the delay along with its level of certainty.
Propose an alert, pre-order, or alternative according to the available rules.
Transfer if the request concerns a volume, a partnership, or an urgency.
Which messages should be used?
For an alert: "This product is not yet available. I can notify you as soon as it is launched if you wish."
For an estimated date: "Arrival is scheduled around [period], but the exact date may still change."
For an alternative: "If you do not want to wait, I can offer you a similar product that is already available."
When to transfer?
The transfer is useful for B2B requests, large volumes, partnerships, press inquiries, non-standard bookings, or customers who have received contradictory information.
The bot must transmit the product, the variant, the desired quantity, the expected timeframe, and the source of the cited information.
Which KPIs should be monitored?
Track alert sign-ups, requested variants, clicked alternatives, pre-order requests, questions about lead times, and conversion at launch.
This data helps adjust quantities, communication scheduling, and restocking priorities.
Which mistakes should be avoided?
Avoid promising an unconfirmed date, talking about pre-ordering if it doesn’t exist, or collecting contact details without explaining the use.
The chatbot must nurture interest without turning expectation into frustration.
How can Qstomy help?
Qstomy can gather interest in upcoming products, explain estimated lead times, and offer alerts or alternatives based on the catalog.
The bot transforms a page without immediate purchase into an opportunity for engagement and qualified leads.
Explore the AI sales agent or request a demo.
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
