Waitlist Email Templates That Get Opened: 12 Copy-Paste Examples (2026)

TL;DR: Waitlist emails get opened when the subject line is under 40 characters, the sender is a real person, there is one call to action, and the first line is about the reader. The 12 copy-paste templates below cover every stage of a pre-launch campaign, from the signup confirmation to the post-launch check-in. If you run your waitlist on LaunchList, pre-launch waitlist software with email built in, most of them map onto a ready-made email in the library, a starter automation or a lifecycle email you only have to reword. The open-rate ranges are rough industry guides, not promises: test with your own list.

Want to see these emails designed? The waitlist email examples show six of them as they land in an inbox, in five looks, ready to send from LaunchList.

A great waitlist is worthless without a great email strategy. The average waitlist subscriber opens your emails for exactly three reasons:

1. To confirm they're on the list (signup confirmation)
2. To get something they want (early access, exclusive content, rewards)
3. Because you just made a big announcement (launch, feature drop, price change)

Miss these, and a big share of your list will forget who you are before launch day.

Below are 12 copy-paste templates for each stage of a pre-launch campaign. Expected engagement ranges are provided per template, but your actual numbers will vary based on audience warmth, sending domain reputation, and subject-line fit.

The 7 principles of great waitlist emails

Before the templates, here's the pattern that makes them work:

1. Subject line under 40 characters. Mobile inboxes truncate after ~40. Short = opened.
2. Send from a real person, not a brand. A founder's name at [email protected] reads like a person; [email protected] reads like a system, and gets treated like one. Set a reply-to address you actually read, because the best templates below ask for a reply.
3. One CTA per email. Multiple links dilute clicks. Pick one action you want taken.
4. First line addresses their benefit, not yours. "Here's how to move up the queue" not "We're excited to announce…"
5. Plain text beats fancy HTML. Matches personal emails. Higher deliverability. Save designed emails for the launch announcement, if at all.
6. Send time = subscriber time zone, 9–11 AM local. Use your email tool's timezone-delivery feature if it has one.
7. Always include an unsubscribe. Deliverability depends on low spam complaints.

Now, the templates.

Template 1: Signup confirmation (send immediately)

When: Automatically triggered the moment someone joins your waitlist. Goal: Confirm they're in, explain what happens next, plant the referral seed. Expected open rate: 75–90% (transactional emails have the highest open rates)

Subject: You're on the list

Body:

Hey [First Name],

You're officially on the [Product] waitlist. You're #[N] in line.

Here's what happens next:
• We're launching [Month Year]
• Members on the list get first access, before everyone else
• The first 100 to join also get [specific offer]

Want to move up the queue?
Share your invite link. Every friend who joins moves you up by 5 spots:
→ [referral link]

I'll send updates as we get closer to launch. Reply to this email with any questions. It goes straight to me.

[Founder name]
Founder, [Product]

P.S. If you'd rather not receive updates, you can [unsubscribe here]. No hard feelings.

Why it works:

• Confirms the action (you're in)
• Sets expectations (when you'll hear next)
• Introduces the referral mechanic naturally
• Feels personal (signed by founder, reply encouraged)

In LaunchList: you do not build this one. The Verification email goes out the moment someone joins a form with double opt-in on (the default for Waitlist forms), and the optional Welcome email is a single first hello you switch on and reword in Emails, Library. Both send on every plan, the Free plan included, and never count toward your email allowance. Point people at their status page with {{status_link}}: it already shows their position, their referral link and one-tap share buttons.

See it designed: the waitlist welcome email shows this email as it lands in an inbox, in five looks, with who it is for and what to change.

Template 2: Referral invite (send 2 days after signup)

When: 48 hours after signup: long enough to not feel spammy, short enough to stay fresh. Goal: Maximize referrals while interest is high. Expected open rate: 45–55%

Subject: Move up the [Product] list

Body:

Hey [First Name],

Quick one: right now you're #[N] on the [Product] waitlist.

Want to jump the line?

Every friend who joins with your invite link moves you up 5 spots:
→ [referral link]

Your stats so far:
• Referrals: [count]
• Current position: #[N]
• Spots to #1: [N]

The top 100 at launch get [specific reward]. You're [N] spots away.

[Founder name]

Why it works:

• Concrete number (your position)
• Clear math (5 spots per referral)
• Visible progress
• Single CTA

In LaunchList: start from the Referral nudge email in the library, and fill the stats with merge tags: {{position|soon}}, {{referral_count}} and {{referral_link}}. The Keep signups engaged starter automation already has this shape: on Signup confirmed it waits 2 days, sends What to expect, waits 4 more days, then branches on whether the person has referred anyone and sends the nudge only to those who have not. You can build and simulate it on any plan; switching it on needs the Launch plan or above.

See it designed: the referral nudge email, with the reader's place and own link filled in, in five looks.

Template 3: "We're building" update (send weekly or biweekly)

When: Every 1–2 weeks during pre-launch. Goal: Keep the list warm. Build trust. Validate ideas. Expected open rate: 35–45%

Subject: [Specific update, <40 chars]

Good examples:

• This week: we killed a feature
• Feedback from 12 beta testers
• Pricing decision we made yesterday

Body:

Hey [First Name],

Quick update from [Product] this week.

[One specific thing you built, killed, or learned, 3–5 sentences]

[Optional: question for the reader]

That's all. Back to building.

[Founder name]

P.S. Refer friends to move up the queue: [referral link]

Why it works:

• Specific (not generic "we're making progress")
• Feels like an inside look
• Builds a relationship over time
• No heavy CTA, just trust-building

Avoid:

• Generic "we've been busy" updates
• Marketing speak ("we're revolutionizing…")
• Weekly emails if you have nothing specific to say

In LaunchList: use the Founder update library email, written as plain text so it reads like a note. If you build in public, post the update in Updates first: it lands on a public changelog with an RSS feed, and Email this update turns it into a broadcast draft. Sending broadcasts starts on the Collect plan.

See it designed: the founder update email lays out the same three parts as a reader sees them.

Template 4: Feedback request (send 2–3 weeks before launch)

When: 14–21 days before launch day. Goal: Get qualitative feedback + make subscribers feel like insiders. Expected open rate: 40–50%

Subject: Can I ask you something?

Body:

Hey [First Name],

We're launching [Product] in [N] weeks. Before we do, I want to make sure we're solving the right problem.

Quick question: when you signed up, what specific thing were you hoping [Product] would solve for you?

Just hit reply and tell me in one sentence. No survey, no form, just a reply.

Every response goes straight to me and shapes what we build next.

Thanks for being on the list.

[Founder name]

Why it works:

• Low effort for reader (one sentence reply)
• Makes them feel heard
• Produces priceless qualitative data
• 10–15% will actually reply, and those are your highest-intent users

In LaunchList: the Ask for feedback library email has no button on purpose, because the ask is a reply. Set a reply-to address in Project settings, Email so the answers reach you. If you would rather collect structured answers, publish a Survey form instead: answers become filterable contact attributes, and the Survey answered trigger can start an automation.

See it designed: the feedback request email, a one-question note with no button, in the Plain look and four others.

Template 5: Launch-date announcement (send 1 week before launch)

When: Exactly 7 days before launch. Goal: Build launch-day anticipation. Trigger calendar adds. Expected open rate: 50–60%

Subject: [Product] launches [Date]: here's what you'll get

Body:

Hey [First Name],

It's happening.

We're launching [Product] on **[Date]** at [Time] [Timezone].

As a waitlist member, you'll get:
• **[Benefit 1]** (e.g. 48 hours of early access before the public launch)
• **[Benefit 2]** (e.g. 50% off your first year, only for waitlist members)
• **[Benefit 3]** (e.g. First access to [feature])

Add it to your calendar: [calendar link]

Watch your inbox at [Time] [Timezone] on [Date]. Your early-access link will arrive the minute we go live.

[Founder name]

Why it works:

• Specific date + time
• Calendar add = commitment
• Clear benefits of being a waitlist member
• Builds FOMO for non-members

In LaunchList: set your launch date in Project settings, General, then either schedule this as a broadcast (the Collect plan and up) or put it on an automation with the Launch day trigger set to 7 days before (the Launch plan and up). A launch-day flow enrolls your whole mailable audience at once and fires only once.

See the email it leads up to: the launch day email, designed and ready to send.

Template 6: 24-hour warning (send 1 day before launch)

When: 24 hours before launch. Goal: Re-engage the list. Get final referrals. Expected open rate: 55–65%

Subject: Tomorrow.

Body:

Hey [First Name],

[Product] goes live tomorrow at [Time] [Timezone].

Your current position: #[N]
Spots ahead of you: [N-1]

Last chance to refer friends before we open access. The top 100 still get [specific reward]:
→ [referral link]

See you tomorrow.

[Founder name]

Why it works:

• Urgency (last chance)
• Personalization (your position)
• Single CTA

In LaunchList: the same Launch day trigger, set to 1 day before. Give the position tag a fallback, such as {{position|near the front}}, so nobody reads an empty number; the pre-send check stops the email if a tag that can be empty has no fallback.

See the email that follows it: the launch day email, as it lands in an inbox the next day.

Template 7: Launch-day announcement (send at go-live)

When: The exact minute your product launches. Goal: Immediate conversion: send them to the product. Expected open rate: 60–75% (peak of the entire campaign)

Subject: [Product] is live: your access is inside

Body:

Hey [First Name],

[Product] is live.

Your early-access link (active for 48 hours before we open to the public):
→ [product link]

Your waitlist perks:
• **[Perk 1]**: use code `WAITLIST[X]`
• **[Perk 2]**: already applied to your account
• **[Perk 3]**: claim within 48h

Jump in and let me know what you think.

[Founder name]
Founder, [Product]

P.S. If you loved it, share with a friend: [share link]

Why it works:

• Direct, no fluff
• Links above the fold
• Specific perks
• Final share CTA for viral pickup

In LaunchList: start from We're live in the library. The Launch day starter automation sends it on the day and follows with Last call a day later. For the early-access link, invite people from Audience, Invites: each person gets their own code in the Invitation email, batches hold up to 1,000 people (most referrals first, then earliest signup), and you can see who used their code. In your own email, {{invite_link}} and {{invite_code}} resolve per person, and the email is skipped for anyone without a live code rather than sent with a dead link. Personal invites are on every plan (the Free plan covers your first 100); shared codes with a seat limit and open links need the Launch plan.

See it designed: the launch day email, in five looks, with when to send it and what to change.

Template 8: Product Hunt launch request (send launch day)

When: The day you launch on Product Hunt. Goal: Drive waitlist members to your PH page to comment and engage. Expected open rate: 40–50%

Subject: We're launching on Product Hunt today

Body:

Hey [First Name],

We're live on Product Hunt right now.

Would mean the world if you'd check it out and leave a comment:
→ [Product Hunt link]

As a waitlist member, I'm also unlocking [specific PH-exclusive deal]: code `PHLAUNCH` at checkout.

Thanks for being part of this from the beginning.

[Founder name]

Important: Never say "please upvote": Product Hunt penalizes this. Say "check it out" or "leave a comment."

In LaunchList: a broadcast. The Launch Day screen (the Launch and Grow plans) gives you the link to share and one-tap share buttons that open a prefilled post for you to send yourself; nothing posts on its own.

More waitlist emails, designed: the waitlist email examples show the six emails most waitlists send, from the welcome to launch day.

Template 9: Launch-day stats recap (send +1 day after launch)

When: 24 hours after launch. Goal: Share momentum with your list. Convert stragglers. Expected open rate: 35–45%

Subject: 24 hours in: what happened

Body:

Hey [First Name],

24 hours ago we launched [Product]. Here's what happened:

• [Metric 1] (e.g. 1,847 signups)
• [Metric 2] (e.g. #3 on Product Hunt)
• [Metric 3] (e.g. featured on [publication])

Your waitlist perks are still active for another [N] hours:
→ [product link]

If you haven't claimed yet, now's the moment.

Thanks for being here.

[Founder name]

Why it works:

• Social proof (the numbers)
• Urgency (perks expiring)
• Re-engages people who missed launch

In LaunchList: a broadcast. Pull the numbers from Analytics, where every figure is shown against the previous period, and only quote numbers that are true.

Planning the launch itself? See the launch day email designed, with the three things to list on day one.

Template 10: Re-engagement (send 30 days after launch, to non-converters)

When: 30 days post-launch, only to waitlist members who haven't converted. Goal: Recover lost interest. Learn why they didn't buy. Expected open rate: 30–40%

Subject: Did [Product] not work out?

Body:

Hey [First Name],

You joined the [Product] waitlist a while back but haven't checked it out since launch.

Totally fine. I just want to make sure it's not because of something I can fix.

If you have 30 seconds, reply with one of:

1. Timing wasn't right
2. Price/pricing concern
3. Missing a specific feature
4. Not sure what it is exactly
5. Other (please share)

No "come back" discount, no pressure. Just trying to learn.

[Founder name]

Why it works:

• Low-pressure
• Gives real feedback
• No aggressive discount
• Founder-signed

In LaunchList: move people through your pipeline stages (waitlist, invited, joined, converted) as they act, then send this to everyone not yet in your converted stage. Build that audience in Audience, Signups, Segments (saving a segment needs the Launch plan) or address it to a tag on the Collect plan, and use Don't send to to skip anyone who got an earlier broadcast.

Fewer people drift if you write before launch: the founder update email keeps a list warm while you build.

Template 11: Unlock notification (milestone-based)

When: When a subscriber hits a referral milestone. Goal: Reward + re-engage + encourage more referrals. Expected open rate: 55–65%

Subject: You just unlocked [reward]

Body:

Hey [First Name],

You've referred **[N] friends** to [Product], which just unlocked **[reward]**.

We'll apply it automatically when you create your account at launch.

You're now #[N] on the waitlist, just [M] referrals from hitting #1.

→ [referral link]

[Founder name]

Why it works:

• Real reward
• Specific progress
• Natural next step (keep referring)

In LaunchList: nothing to build. Set up your reward ladder in Audience, Referrals & rewards (up to 20 rungs, the Collect plan and up) and each unlock sends its own announcement automatically, once per unlock. The Reward unlocked email uses {{reward}}, which resolves to the highest rung that person reached, in your own words, and the email does not go out at all if there is nothing real to congratulate.

When the reward is early access: the early access invite email shows the invite with its link and access code, designed.

Template 12: Price-anchoring email (send 2 days before launch)

When: 48 hours before launch, to justify your price and anchor expectations. Goal: Reduce launch-day price objections. Expected open rate: 40–50%

Subject: What [Product] will cost (and why)

Body:

Hey [First Name],

[Product] launches in 48 hours. I want to be upfront about pricing before you see the page.

At launch:
• **Free tier:** [what's included]
• **[Plan 1]:** [price]: [who it's for]
• **[Plan 2]:** [price]: [who it's for]

For context, comparable tools charge:
• [Competitor 1]: [price]
• [Competitor 2]: [price]

Why we priced it here: [one sentence reason, e.g. "Most of our users are indie hackers, and $12 a month is a fair price for people shipping projects on weekends."]

Waitlist members get [specific discount]. The code arrives in your launch email.

[Founder name]

Why it works:

• Transparent
• Anchors against competitors
• Reduces sticker shock
• Builds trust

In LaunchList: a scheduled broadcast. If you are also sending invites at launch, send the pricing note to the same segment first, then the invite batch.

See the emails around it, designed: the waitlist email examples cover the welcome, the nudge, the update, the feedback question, the invite and launch day.

Email cadence: how often should you email your waitlist?

For a 4-week pre-launch campaign, here's a proven cadence:

Total emails: 11 over ~5 weeks. Any less = list goes cold. Any more = unsubscribes spike.

What to put in the "from" field

This single variable has an outsized effect on whether your email gets opened at all.

Best: Firstname Lastname <[email protected]>: personal name, brand domain. Good: Firstname at [Product]: familiar but branded. Avoid: noreply@[domain], marketing@, hello@.

Running these templates in LaunchList

Most waitlist tools stop at the confirmation email and leave everything else to a separate email provider, which means exporting your list, rebuilding segments and losing the referral data on the way. LaunchList is pre-launch waitlist software with email built in, so every template above can go out from the same place your signups, referral counts and invite codes live. Here is how the pieces fit.

The four kinds of email LaunchList sends

The nine ready-made emails in the library

Every new project gets a library of nine starter emails under Emails, Library. They are written to be sent as they are, and each one is fully editable. This is how they line up with the templates in this post:

Save your own versions to the library too. A saved email carries your project's brand settings, so changing your logo or colors updates every saved email at once. The editor writes in blocks, Markdown or raw HTML, and a broadcast can also be plain text: no images, no HTML and no tracking, so it reads like a note from a person, which is what principle 5 asks for.

Merge tags: the placeholders in these templates

The square-bracket placeholders above become merge tags. Write a fallback after a pipe for anything that can be empty:

Hey {{first_name|there}},

You're #{{position|near the front}} on the {{project_name}} waitlist.
Friends you've brought in so far: {{referral_count}}

Your link: {{referral_link}}
Your page: {{status_link}}

The tags you will use most are first_name, name, email, project_name, position, referral_count, referral_link, status_link, reward, invite_code, invite_link, product_link and unsubscribe_url. Two safety rails matter for these templates. The pre-send check stops a broadcast whose name or position tag has no fallback, so nobody gets "Hi ,". And a name that looks fake, such as "test" or a placeholder someone typed into a form, is greeted with your fallback instead of being repeated back. The invite and reward tags work the other way round: if someone has no live code or no reward, the email is skipped for them rather than sent with a dead link.

The three starter automations

Under Emails, Automations you can start from three ready-made flows, each built from the library emails and each a draft until you switch it on:

• Keep signups engaged (Templates 1 and 2): on Signup confirmed, wait 2 days, send What to expect, wait 4 days, then send the Referral nudge only to people who have not referred anyone yet.
• Invite reminder (the follow-up to Template 7): two days after someone is invited, if they are still in your invited stage, send the reminder with their own claim link.
• Launch day (Templates 7 and 9): on your launch date, send We're live, wait a day, send Last call.

Triggers you can build your own flows on: signup confirmed, new signup, referral credited (optionally only at N referrals), stage changed, survey answered, and launch day (on the day, or 1, 3, 7, 14 or 21 days before). Branches can test whether someone is verified, has a tag, is in a stage, has referred at least N people, where they stand on their invite, whether an email to them bounced, or whether they received a given broadcast. A built-in simulator walks a test contact through the flow before you turn it on. Start email flows from Signup confirmed: with double opt-in on, an unconfirmed signup is not yet mailable and an email step skips them.

Sending a broadcast, step by step

1. Open Emails, Broadcasts and press New broadcast, or pick a library email.
2. Choose the audience: everyone, a saved segment, or a tag. Under Don't send to, leave out segments, tags, or anyone who received an earlier broadcast.
3. Write it, with merge tags, and send a test to yourself or a teammate.
4. Choose delivery: all at once, or in batches of a set number per hour or per day, oldest signups first.
5. Send now or schedule. The pre-send check covers the subject, the content, your postal address in the footer, every merge tag, the audience size and whether the recipients look deliverable. If the send is bigger than what is left of your monthly allowance, it shows how many extra emails it needs at $3 per 1,000 and waits for you to approve; nothing is charged on its own.

A batched broadcast never reaches anyone twice, and LaunchList pauses it before the next batch if too many addresses bounce or complain. You can pause, resume or cancel any broadcast yourself.

Sending from your own domain

Principle 2 and the "from" field advice above depend on the address your mail comes from. On the Free and Collect plans, LaunchList sends from a shared sending domain with nothing to set up. On the Launch and Grow plans, open Project settings, Email, enter a subdomain such as mails.yourproduct.com, and add the three CNAME records shown: a return path for bounces and two DKIM signing keys. There is no TXT record to edit, so your existing SPF and DMARC records stay as they are, and there is no certificate to buy. Use a subdomain so your marketing sends never affect the reputation of the mail your team sends by hand. Set the from name and reply-to address on the same screen.

Deliverability is handled where it can be

• Every broadcast and automation email carries a working unsubscribe link and the one-click unsubscribe headers Gmail and Yahoo require, plus your postal address in the footer.
• Anyone who unsubscribed, hard-bounced or marked an earlier email as spam is skipped at send time, even if they match your audience.
• Before a broadcast reaches an address LaunchList has never checked, it runs a deliverability check at no cost to you, and undeliverable or disposable addresses are skipped.
• Bad lists are caught early: sending is paused for review if a workspace's bounce rate reaches 2% over 30 days (after its first 500 sends).
• Importing a list never emails anyone. Send the Quick hello deliberately, after you have checked what you imported.

How you will know a template worked

LaunchList reports sent, delivered, bounced, unsubscribed and spam complaints for every broadcast and automation, each against the previous period, on Analytics, Emails, and every single email is listed in Emails, Activity. It does not track opens or clicks. That is deliberate for templates like these: plain-text founder emails read better without tracking pixels, and the real outcomes are visible anyway. Judge Templates 2 and 6 by whether referral counts move on Analytics, Referrals, Template 4 by replies, and Template 7 by how many invite codes are used on Analytics, Invites. If you want to test two versions of an email, the automation A/B split step sends contacts down two paths at random, and giving each path its own tag lets you compare what each group did next.

Sending from code or an AI agent

Everything above is also reachable without the dashboard. The REST API (53 operations, documented in a public OpenAPI 3.1 spec) can create, test, prepare and send broadcasts with a key scoped to broadcasts:send. The MCP server, on every plan, lets an assistant such as Claude, ChatGPT or Cursor draft a broadcast with save_broadcast, check the audience and counts with prepare_broadcast_send, and only then send with the confirmation token that step returns; an agent cannot skip the check. Webhooks fire on email.sent, email.bounced, email.complained, email.unsubscribed and campaign.sent, among 27 signed event types, if you want delivery events in your own tools.

What it costs

The Free plan is $0 for 100 contacts and sends every lifecycle email, but no broadcasts. The Collect plan, from $9 a month, adds broadcasts and reward announcements with a monthly allowance of one campaign email per contact in your plan size (up to 5,000). The Launch plan, from $19 a month, adds automations, your own sending domain and saved segments, with two campaign emails a month per contact in your plan size. The Grow plan, from $39 a month, adds where-signups-come-from analytics. Extra campaign emails are $3 per 1,000, approved by you first. Prices are beta prices, monthly or yearly (12 months for the price of 10); see pricing.

Start your waitlist free →

Frequently asked questions

What is a good open rate for waitlist emails?

As a rough industry guide, confirmation emails tend to see the highest open rates, launch-day emails come next, and regular updates sit lower. Open tracking has become unreliable because many mail apps load images automatically, so replies, referral counts and invite redemptions are better signals; LaunchList reports delivered, bounced, unsubscribed and spam complaints rather than opens.

How often should I email my waitlist?

Every one to two weeks is enough for most pre-launch campaigns, with more emails in the final week before launch. More than one email a week only works if each one has something specific to say.

Should I use plain text or HTML for waitlist emails?

Plain text, or very light HTML that looks like plain text, usually works better for founder updates and feedback asks because it reads like a personal note. LaunchList broadcasts can be written as plain text, which still carries the unsubscribe line and your postal address.

How do I keep my waitlist emails out of spam?

Only email people who opted in, authenticate the domain you send from, send from a real person's name, include a working unsubscribe link, and do not go silent for months before a launch blast. On LaunchList's Launch and Grow plans you can send from your own subdomain with three CNAME records, and suppression, one-click unsubscribe and bounce handling are automatic on every plan.

Can I send waitlist emails from my waitlist tool instead of Mailchimp?

Yes, with LaunchList. Confirmation, welcome and invitation emails send on every plan, broadcasts start on the Collect plan at $9 a month, and automations and your own sending domain are on the Launch plan from $19 a month, so you do not need a separate email provider.

Do confirmation emails count toward my email allowance?

No. On LaunchList, verification, welcome and invitation emails never count toward your monthly allowance. Broadcasts, automation emails and reward announcements do.

When is the best time to send waitlist emails?

Mid-morning on a weekday in the reader's time zone is a sensible default; avoid Monday mornings and Friday afternoons. For a list spread across time zones, split the send by region, for example with a segment on country (saving segments needs LaunchList's Launch plan).

Should I personalize waitlist emails with a first name?

Only if you collected names you trust. Always write a fallback, such as {{first_name|there}}, so an empty or fake name never shows; LaunchList blocks a broadcast whose name tag has no fallback and replaces names that look fake.

Related reading:

• 5 Proven Strategies to Boost Waitlist Engagement
• How to Use Milestones and Rewards
• LaunchList features: broadcasts, automations and your own sending domain