Playbook

Welcome Email Sequence: What to Send, When to Send It, and Example Copy

The moment someone subscribes is the best attention you will get from them. Here is the welcome email sequence email by email, with timing, example copy, and the exit rules that keep it from colliding with your other flows.

By Sangeeth · June 2026 · 16 min read

Someone just typed their email address into your form. They know who you are, they chose to hear from you, and they are probably still on your site. You will rarely have their attention this cleanly again, and most stores and SaaS products spend it on a single "Thanks for subscribing!" email that nobody remembers.

A welcome email sequence is a short automated series that turns that signup into a first purchase, a first login, or a first booked call. This guide walks through the sequence email by email, with timing anchored to the signup event, example copy for each message, the variants that change for ecommerce, SaaS and service businesses, and the exit rules that keep it from colliding with your abandoned cart and post-purchase flows.

The example copy uses a fictional coffee roaster, Kettle & Crow, which sells beans online and offers 10% off a first order for signing up. Swap in your own product, voice and incentive.

What a welcome email sequence has to do

A welcome sequence has four jobs, and each email should own one of them. It delivers what the signup form promised. It tells the subscriber who you are and why you exist, so the next email from you is recognised rather than deleted. It shows proof that other people bought and were happy. And it removes the specific reasons a new subscriber hesitates before a first purchase.

A fifth job is easy to forget: letting the subscriber tell you what they want. Preference choices made in the welcome window are the cheapest segmentation data you will ever collect, because the subscriber is still paying attention.

The sequence is not a newsletter. It runs once per subscriber, is triggered by an event rather than a calendar, and should end the moment it has done its job.

Double opt-in: the confirmation email comes first

If you use double opt-in, the first email a subscriber receives is not your welcome email. It is a confirmation request, and the welcome sequence should only start once they click it. That ordering matters: if your automation fires on "form submitted" instead of "subscription confirmed", unconfirmed addresses receive marketing they never verified, which defeats the point of double opt-in.

Keep the confirmation email plain and functional. Shopify's own documentation for its built-in double opt-in says that, for legal reasons, the confirmation email should not contain any marketing, and that the confirmation is sent automatically when someone subscribes through the online store (Shopify Help Center). The same principle applies on any platform.

Example: confirmation email

Subject: Confirm your email for Kettle & Crow

Hi,

Please confirm you want emails from Kettle & Crow:

[Confirm my subscription]

Your 10% welcome code will arrive as soon as you confirm.
If you didn't sign up, ignore this email and you won't hear from us.

It names the brand, has one button, and tells the subscriber the incentive is waiting on the other side of the click, which gives a reason to confirm now rather than later. Update the on-site success message too ("Check your inbox to confirm and get your code"), as Shopify also recommends when double opt-in is on.

The welcome email sequence, email by email

Five emails over about ten days is a sensible default for ecommerce. SaaS and service variants follow later; the structure is the same, the content of each slot changes.

Email 1: deliver the incentive and set expectations

Sends: immediately after confirmation (or after signup, with single opt-in).
Job: hand over exactly what the form promised, then tell them what comes next.

The code, guide or download goes above the fold, not under three paragraphs of brand introduction. Put the expiry date in plain words and say what you will send and how often. Subscribers who know what to expect are less likely to hit the spam button when your next email arrives.

Example copy

Subject: Your 10% code is inside
Preheader: WELCOME10, good for 14 days on any bag

Hi Priya,

Here's your code: WELCOME10
It takes 10% off your first order, any bag, until 24 October.

[Shop the beans]

What happens next: over the next week we'll send a few short
emails, including how we pick our coffee and which bags people
reorder most. After that, expect one email a week, usually new
roasts. You can change that any time.

Sam, head roaster at Kettle & Crow

Email 2: the brand story

Sends: day 2.
Job: make the brand recognisable and give a reason to choose you over a cheaper alternative.

The brand story fails when it reads like an About page. Tell one specific story that explains a product decision: why you roast to order, why you only stock four origins, why your onboarding asks three questions. Specifics are believable; adjectives are not. A plain, personal format often suits this email better than a designed layout, because it reads like a person writing rather than a campaign.

Example copy

Subject: Why we only roast on Mondays

Hi Priya,

Most coffee you buy online was roasted weeks before it shipped.
We started Kettle & Crow because we kept buying "fresh" beans
that tasted flat.

So we roast every Monday, ship Tuesday to Thursday, and print
the roast date on every bag. If a bag is more than three weeks
from its roast date, we don't send it.

That's the whole idea. If you want to taste the difference,
your code WELCOME10 is still good until 24 October.

[See this week's roast]

Sam

Email 3: best sellers and social proof

Sends: day 4.
Job: shorten the decision by showing what other people buy and what they said.

New subscribers face a choice problem as much as a trust problem. Narrow the catalogue to three products, explain who each is for, and attach a real review to each one. Use reviews you actually have, quoted accurately with permission; do not invent star counts or "thousands of happy customers" figures. If you have few reviews, a single detailed one beats five generic ones.

Example copy

Subject: The three bags people reorder

Hi Priya,

If you're not sure where to start, these are the bags customers
come back for:

1. Morning Crow (medium, chocolatey) - for milk drinks
   "Finally a coffee that doesn't disappear under oat milk." - Dana

2. Kenya Kiambu (light, bright) - for filter and pour-over

3. Decaf Night Shift (Swiss Water process) - for after 3pm

[Pick your first bag]

WELCOME10 still takes 10% off until 24 October.

Email 4: objection handling

Sends: day 6 or 7.
Job: answer the questions that stop people buying.

Look at your support inbox, chat logs and returns reasons, and pick the three objections that come up most often before a first order. For coffee it is usually grind, shipping cost and "what if I don't like it". For SaaS it is setup effort, data migration and price. Answer each in two or three sentences and link to the full policy.

Example copy

Subject: Quick answers before you order

Hi Priya,

Three questions we get from almost everyone before a first order:

Which grind do I need?
Pick your brewer at checkout and we grind for it. Or choose whole
bean if you have a grinder.

How much is shipping?
Shipping costs are shown in the cart before you pay.

What if I don't like it?
Email us within 30 days and we'll swap it for a different roast.

[Order with WELCOME10]

Your code expires in 4 days.

The shipping and returns lines in your version must match your real policy word for word. An objection-handling email that promises something your returns page does not is a support ticket waiting to happen.

Email 5: preferences and the next step

Sends: day 9 or 10, ideally one day before the incentive expires.
Job: last reminder for the incentive, and a handoff into your regular program on the subscriber's terms.

Combine the final reminder with a preference choice: frequency, product interest, or content type. Each option is a tracked link that tags the contact, so the click is the answer. Subscribers who would otherwise unsubscribe often pick "monthly" instead, which keeps them on the list and out of the complaint statistics.

Example copy

Subject: Last day for WELCOME10 (and a quick question)

Hi Priya,

Your 10% code expires tomorrow night.
[Use WELCOME10]

One question so we only send what you want. What should we email
you about?

[New roasts every week]
[Brewing guides and recipes]
[Just the monthly roundup]

Click one and we'll adjust. No forms.

Sam

Welcome email timing, anchored to signup

Every delay in the sequence should be measured from the signup or confirmation event, not from the previous email's send time and not from a campaign calendar. Anchoring to signup keeps the incentive expiry and the reminder email consistent: if the code is valid for 14 days from signup, the "last day" email must be scheduled from that same anchor.

Send emails 2 to 5 at a sensible local hour for the subscriber, or for your main market. Email 1 always goes immediately, even at 11pm: the incentive is what they are waiting for. And do not stretch the sequence to fill time; a "welcome" email a week after the code has expired is a regular campaign wearing the wrong label.

Ecommerce vs SaaS vs service businesses

The five-slot structure holds across business models. What changes is the conversion event, the incentive and what each slot contains.

SaaS: trigger on behaviour, not just time

For a SaaS product the welcome sequence and onboarding are the same thing, and onboarding is behavioural. If a user signed up but never completed the first action, email 2 should help them do that action, not tell the founder story. A fictional invoicing tool, Ledgerly, might send this on day 1 to users who have not created an invoice yet:

Subject: Your first invoice takes about two minutes

Hi Marco,

You signed up for Ledgerly yesterday but haven't sent an invoice
yet. The fastest way in: duplicate the sample invoice, change the
client name and amount, and hit send.

[Open the sample invoice]

If you're moving from spreadsheets, reply with a CSV and we'll
tell you how to import it.

Elena, Ledgerly

Users who already sent an invoice skip this email and get the next step instead, such as setting up payment reminders. That branching on product events is what separates SaaS onboarding from a timed drip.

Service businesses: shorter, with a human reply path

Service businesses sell through a conversation, so three or four emails are often enough. Send from a real person's name, invite replies, and route them to someone who answers within a working day.

Stop the sequence when someone buys

The most common welcome sequence bug is not bad copy. It is a customer who ordered on day 2 and still receives "Your code expires tomorrow!" on day 9, which tells a new customer your systems do not know who they are.

Every email after the first should check a goal condition before sending: has this contact placed an order (or activated, or booked) since entering the sequence? If yes, exit the sequence. Check at send time, not just at entry, because the purchase can happen at any point during the ten days.

How the welcome flow hands off to abandoned cart and post-purchase

New subscribers are often still evaluating you, so many start a checkout and abandon it. If both flows run independently, the same person can get a welcome email and an abandoned cart email on the same afternoon. Decide priorities in advance:

• Abandoned cart takes priority over welcome. A cart is a stronger intent signal than a signup. Pause the welcome sequence while the contact is in the abandoned cart flow, and resume it, or end it, depending on whether they buy.
• Do not stack incentives. If the welcome code already gives 10% off, the abandoned cart email should remind them of that code, not offer a second, larger one. Otherwise subscribers learn that abandoning carts pays.
• A first purchase ends the welcome flow and starts post-purchase. Once an order is placed, the customer belongs in your post-purchase sequence: order confirmation, shipping, product education and a review request later on.
• Set a frequency cap across automations. One automated marketing email per contact per day is a reasonable ceiling. Transactional messages such as order confirmations sit outside the cap.

Existing customers who subscribe to the newsletter are the other edge case. Someone who has ordered three times does not need a "here's how we roast" introduction or a first-order code they cannot use. Check order history at entry and send customers a shorter variant, or skip the sequence entirely.

Measure clicks and revenue, not opens

Open rates are a weak signal for a welcome sequence. Apple's Mail Privacy Protection downloads remote content privately in the background, which includes tracking pixels, and Apple says it prevents senders from seeing whether a message was opened (Apple Support). An "open" recorded for an Apple Mail user may not mean a human read anything. Plain-text emails without a tracking pixel record no opens at all.

Measure the sequence on what it is supposed to cause:

• Conversion rate of the cohort. Of everyone who entered the sequence in a given week, what share placed a first order (or activated, or booked) within the sequence window? This is the number that tells you whether the sequence works.
• Revenue per subscriber. First-order revenue from the cohort divided by the number of subscribers who entered. This lets you compare a 10% code against free shipping fairly.
• Click rate per email. Useful for spotting a weak email in the sequence, since clicks require deliberate action.
• Unsubscribes and spam complaints per email, plus confirmation rate if you use double opt-in.

To know whether the sequence causes purchases rather than just being present when they happen, hold out a small random group of new subscribers who receive only email 1. Compare their first-purchase rate over the same window with the full-sequence group. Without a holdout, attribution reports will credit the sequence with orders that would have happened anyway.

Common mistakes

• Triggering on form submit with double opt-in enabled. Unconfirmed addresses get marketing, and the confirmation email and welcome email arrive at the same moment.
• No purchase exit. Buyers receive "last chance" discount reminders for a code they already used.
• Burying the incentive. The code sits under a hero image and a brand paragraph. Subscribers scroll, do not find it, and email support.
• Incentive stacking with abandoned cart. Two different discounts in one week train subscribers to wait for the bigger one.
• Invented social proof. Fabricated reviews or inflated customer counts create legal and trust problems. Use what you can document.
• Optimising subject lines on open rate. With privacy-protected opens, the "winner" of an open-rate test can be noise.
• Sending a welcome sequence from an unauthenticated domain. Gmail requires SPF or DKIM from every sender, and SPF, DKIM and DMARC from anyone sending more than 5,000 messages a day to Gmail accounts (Google sender guidelines). A welcome email that never reaches the inbox converts nobody.

Troubleshooting

Subscribers say the welcome email never arrived

Check whether the contact entered the automation at all. If the form tool and your email platform are connected through an integration, look for failed syncs or a missing list/tag mapping. If the contact entered and the email was sent, look at the delivery event: a bounce means a bad address, while a delivered message the subscriber cannot find usually means spam or a Promotions tab. Send yourself a test at a Gmail address and inspect the headers; our guide to improving email deliverability shows how to read Authentication-Results.

Confirmation rate dropped suddenly

Click the confirm link yourself from a fresh subscriber. Broken redirects after a site migration and link-tracking domains that fail TLS are common causes. If the link works, check whether the confirmation email is landing in spam.

Customers got the welcome sequence after already buying

Your exit condition is evaluated only at entry, or the order event is not reaching the email platform. Place a test order with a new subscriber and watch whether the contact leaves the sequence. Also check that the order and the subscription use the same email address; a customer who checks out with a different address will not match.

Clicks are healthy but first orders are low

The problem is usually on the landing page, not in the email. Check that the code auto-applies or is easy to enter, that the products linked are in stock, and that shipping costs are not a surprise at checkout.

One email has a high unsubscribe rate

Read it as a subscriber would. A founder-centric story, a hard sell on day 2 or daily sends push people out. Move or rewrite the email before cutting it.

Best practices

• Trigger on confirmation (double opt-in) or signup (single opt-in), and anchor every delay to that event.
• Deliver the promised incentive in email 1, above the fold, with a plain-language expiry date.
• Give each email one job and one primary call to action.
• Check a purchase or activation goal before every email after the first.
• Pause the welcome flow while a contact is in abandoned cart, and hand buyers to post-purchase.
• Never offer two different first-order discounts in the same week.
• Send from a recognisable person or brand name, from an authenticated domain, with a reply address someone reads.
• Collect preferences with one-click tagged links rather than a form.
• Measure cohort conversion and revenue per subscriber; use a holdout group to check the sequence causes the lift.

On format: the brand story and the founder-style emails often work well as plain text, while best sellers and product grids need images. Mixing formats within one sequence is fine. SendDoggie supports both true plain-text campaigns and a drag-and-drop designer with starter templates, so each email can use whichever format suits its job. For the trade-offs, see plain text vs HTML email.

Key takeaways

• A welcome email sequence has distinct jobs: deliver the incentive, tell the brand story, show best sellers and proof, handle objections, then collect preferences and make the last ask.
• With double opt-in, the confirmation email comes first, contains no marketing, and the sequence starts only after the click.
• Anchor every delay to the signup or confirmation event so incentive expiry and reminders line up.
• Exit the sequence on purchase, pause it during abandoned cart, and hand buyers to the post-purchase flow. Do not stack discounts across flows.
• Ecommerce, SaaS and service businesses share the structure but differ in conversion event, incentive and content; SaaS onboarding should branch on product behaviour.
• Judge the sequence by cohort conversion, revenue per subscriber and clicks, not open rates, and use a holdout group to confirm it is causing the result.

Sources

1. Shopify Help Center: Collecting customer contact information (double opt-in)
2. Apple Support: Use Mail Privacy Protection on iPhone
3. Google: Email sender guidelines