Template
Waitlist email
The confirmation that goes out the second somebody joins a waitlist, and the one follow-up that keeps them warm until you can let them in.
Your Product
You are on the list
Thanks for signing up. You are number 428, and we are opening accounts in small batches so we can help each one get set up properly.
When your turn comes you will get one email with a link that logs you straight in. No card, no sales call. If it is not the right time you can say so and keep your place.
See what we have shipped so far
One thing that would help: hit reply and tell us what you are trying to fix. We read every one, and it changes what we build next.
Alex, Your Product
Your Product Inc, 1 Example Street
Unsubscribe from these emails
The blueprint
Rebuild it anywhere
Subject lines (5 options)
- You are on the listshown above
- You are number 428 for Your Product
- Got you. Here is what happens next
- Your Product: you are in the queue
- Confirmed, plus what to expect
When it fires
- Trigger
- Fires when the waitlist form is submitted, from your own backend, so the email and the record are created by the same request.
- Timing
- Immediately. A confirmation that arrives four minutes later reads as a system that is unsure whether it worked.
The body, block by block
Confirmation line
Say they are in, in the first four words. This email is read in a notification preview more often than it is opened, so the confirmation cannot wait for paragraph two.
Position or batch
A number, a batch size, or a rough month. Anything concrete beats "soon". If you genuinely do not know, say that instead of guessing, because a missed date is worse than an absent one.
What happens next
Who the email will come from and what it will contain. This is the part that stops your invite landing in spam three weeks later, because they have been told to expect it.
One link, no pressure
Somewhere to go that is not a purchase: a changelog, a demo video, a short write-up of the problem. It gives an interested reader something to do with the interest.
A reply prompt
Ask one question that a person can answer in a sentence. Replies are the cheapest research you will ever run, and a reply is also the strongest deliverability signal a mailbox provider can see.
Sign-off from a person
A name, not a department. This is the first mail from a product nobody has used yet, so the only thing it can be trusted on is that a human sent it.
The rest of the sequence
Two to four weeks later, or when your batch cadence says so
Show one thing you shipped since they joined, so the list learns the product is moving.
Subject What we built while you were waiting
The day their account opens
The invite. One link, logs them in, no form to fill in again.
Subject Your account is open
When to use it
Any time there is a gap between somebody wanting the product and being able to use it. Private betas are the obvious case, but the same email covers a region you have not opened yet, a plan that is capacity limited, and an integration somebody asked to be told about.
It is worth writing properly because it is the only email most of these people will get from you for weeks. The signup was the moment of highest intent, and everything after it is decay. A confirmation that sets a real expectation slows that decay down; a bare "thanks, we will be in touch" does nothing to it at all.
SendHeron runs its own waitlist on this exact shape, which is why the blueprint has a reply prompt: the replies are where most of the roadmap came from.
What kills this email
Confirming the signup without setting an expectation
"We will be in touch soon" tells a reader nothing they did not already assume. Give them a position, a batch cadence, or a month. The point is not accuracy, it is that a stated expectation can be met, and an unstated one is met by nothing.
Then going quiet for three months
A single confirmation followed by silence means your invite lands, months later, at an address that has forgotten you exist. That is the shape of mail people mark as spam. One update in between is enough to keep the address warm and the sender recognised.
Selling to somebody who has already said yes
They joined the list. The case is made. A confirmation that spends four paragraphs on features is answering a question that was asked and settled, and it costs you the attention you will need when the invite actually arrives.
Sending it from an address that cannot receive a reply
A no-reply sender throws away the one thing this audience is unusually willing to do, which is tell you what they want. It also removes the reply signal that mailbox providers read as evidence a sender is wanted.
When not to send it
Do not send it if people can use the product immediately. A confirmation email in front of an open signup is a step between the person and the thing they came for, and the welcome email is the one that belongs there instead.
Do not send it as a marketing email. This is a transactional confirmation of an action somebody just took, so it goes out on your transactional path, and it does not carry a campaign footer or a promotion for something else.
Next
Private beta
Waitlist email, drafted from your website
SendHeron reads your website and drafts a suite like this one, in your product's own words, ready to edit. Private beta, and we onboard a few teams at a time.