A pre-launch waitlist on WhatsApp: collecting interest with consent, answering pre-launch questions, keeping the list warm without spamming, and converting it on launch day

A waitlist on WhatsApp beats one on email because people read it. It also comes with a rule: you may message those people on launch day because they asked to be told, and only because of that. Collect the consent explicitly, keep the list warm with real information, and the launch message lands as news rather than spam.

By Ritchie, ReplyKit · Published 5 October 2026 · 6 min read

Quick answer

Collect waitlist sign-ups by asking people to message your number (a link on your landing page and socials), record their consent in the chat ("Reply YES to be told when we launch"), answer their questions from a pre-launch knowledge note, send at most two or three useful updates before launch, and one launch message on the day with the link. Everyone who said yes is in your leads list with the stage "waitlist"; the launch message is sent by a person from quick replies, since ReplyKit's agent replies to messages and does not broadcast.

Collecting sign-ups with consent Pre-launch questions Keeping the list warm Launch day FAQ

Collecting sign-ups with consent

A click-to-chat link on the landing page and bio with a pre-filled message: "Hi, I'd like to join the {product} waitlist"; how to make one is in creating a WhatsApp link.
The agent replies: what the product is in two lines, when it launches, and "Reply YES to be told the moment it's live."
On YES, it records the consent and asks one optional question that helps you ("What would you use it for?"), which also warms the lead.
It records the contact in the leads list with stage "waitlist" and the source number, so you know which post or page produced it.
That YES is the opt-in WhatsApp's policy requires for the launch message; the rules are in consent rules for businesses.

Pre-launch questions

Write a pre-launch note: what it is, who it is for, expected price or range, launch date or window, what early sign-ups get, and the honest "not decided yet" answers. The agent answers from it in seconds, in any language, and records the questions it could not answer, which is free market research. Update the note as decisions firm up.

Keeping the list warm

Two or three updates in total, each with real information: a feature reveal, the price confirmed, the date set.
Sent by a person, by hand or from quick replies, to people who said YES, inside their daytime.
Each ends with the ability to stop: "Reply STOP if you'd rather not hear more." The agent honours STOP automatically.
No daily countdowns, no "just checking in". The per-message value rule is the same as in onboarding a new customer.

Launch day

One message: it is live, the link, the early-sign-up benefit, and a deadline if there is one. Sent in batches by a person from quick replies, in the recipients' daytime, to the YES list only. The agent then handles the flood of questions and the orders or bookings that follow, which is the day it earns its keep; load the launch-day FAQ into the knowledge note the night before. Why not a broadcast: bulk sends from a paired number are the quickest way to a restriction, as our ban guide explains, and a personal message to people who asked for it performs better anyway.

Frequently asked questions

Is it allowed to message a waitlist on launch day?

Yes, if each person explicitly opted in (replied YES to be told). That consent is what WhatsApp's policy requires.

Can the AI agent send the launch message?

No. ReplyKit's agent replies to messages and does not broadcast. A person sends the launch message from quick replies; the agent handles the replies and orders.

How many updates before launch?

Two or three, each with real news, each with a way to stop.

How do I collect sign-ups?

A click-to-chat link with a pre-filled message; the agent records the YES and the source.

Can the agent answer pre-launch questions?

Yes, from a pre-launch note you keep updated, and it records what it could not answer.

Collect the list, answer the questions, convert on the day

Consent recorded, sources tracked, launch-day questions handled. 7-day free trial, no card.

Start free

Written by Ritchie, ReplyKitPart of the small team in Malaysia that builds and runs ReplyKit. Writes about WhatsApp automation, AI customer service and small business lead response.

How we know this. Launch waitlists are a common use of ReplyKit's lead list; the consent wording and launch-day approach here follow WhatsApp's policy and what customers found worked. Product figures in this article (limits, prices, per-reply costs) are taken from ReplyKit as it runs today and are re-checked when we update the page. Where we cite outside research, the source is linked below. We sell ReplyKit, so read our product claims with that in mind; we say where a different tool or no tool is the better choice. About ReplyKit.

Sources and further reading

WhatsApp Business Messaging Policy · opt-in, opt-out and prohibited-use rules every business must follow
ReplyKit, Will WhatsApp ban my number for automation? · our own account of the risk and the limits we enforce

ReplyKit is an independent product and is not affiliated with or endorsed by Meta or WhatsApp. This article is general guidance for running a small business, not legal, financial or regulatory advice.