Before you start
- A list with a recorded consent basis. The series is marketing, so every entrant needs a lawful basis for marketing email recorded against their record. The list building and consent guide covers how sign-up forms capture it and where it is stored; this tutorial assumes it is in place.
- Access to the sending platform's automation builder, with rights to create flows, edit templates and run test sends, and the sign-up forms connected to it so that a sign-up is an event the platform sees as it happens.
- A list of your sign-up sources. Footer form, pop-up, lead magnet download, checkout opt-in, event registration, imported partner list. Each is a reason someone joined, and the series will branch on it. The email sign-up source register template keeps that list with each source's wording, opt-in method and welcome branch.
- The newsletter template, or at least the header, footer and button styles, so that the welcome emails look like the mail that follows them.
- Something to say. The story of the business, the product range or service, the proof that it works, and the one thing you want a new subscriber to do. If these are not written down anywhere, write them before opening the builder.
- A sense of where the welcome sits in the wider customer lifecycle. The lifecycle marketing guide places onboarding among the stages that follow it, and the automation hub explains how this flow relates to the others and which to build next.
Building the series
Define the goal of the series
Write one sentence that says what a subscriber should have done or understood by the end of the series. For a shop it is usually a first purchase; for a software product, a first meaningful use; for a publisher, reading the pieces that show what the newsletter is for; for a consultancy, a reply or a booked call. Choose one primary outcome and, if needed, one supporting outcome such as setting preferences. The goal decides the metric. A series aimed at a first purchase is judged by conversion rate (CVRShare of visits or clicks that convert.) to purchase within the series window; one aimed at engagement is judged by clicks on the content it introduces. Write the goal and the metric at the top of the flow's notes, because every later decision, from the number of emails to the wording of the buttons, is a question of whether it serves that sentence.
Set the trigger and entry rules
The trigger is the sign-up event itself: a form submission, an account creation, a checkout opt-in, received by the platform at the moment it happens. A nightly import is not a trigger; it is a delay, and a welcome email that arrives the next afternoon has missed the moment. Then set the entry rules. Only people with marketing consent recorded enter, and where double opt-inA sign-up process in which the subscriber confirms through a link sent to the address given. is used, entry waits for the confirmation click. People who are already customers either skip the series or enter a branch written for customers. Each person enters once; a re-subscribe after an unsubscribe is a judgement call, and most businesses allow re-entry after a long gap and block it otherwise. Capture the sign-up source as a property at entry, because the personalisation step depends on it and it cannot be recovered later.
Write the first email
The first email is sent immediately, and it is the one most people will open. It confirms what the person signed up for, delivers anything that was promised at the point of sign-up, such as a download or a code, and says what will follow and how often. It comes from a recognisable sender name and a reply address that someone reads. It asks for one small thing: set your preferences, tell us what you are interested in, add this address to your contacts, reply with a question. It does not try to sell, beyond a single link to the obvious next place. Keep it short, because the person has just given their address and is deciding whether that was a mistake. The subject line names the thing they asked for; "Your guide is here" beats "Welcome to our newsletter" every time the guide was the reason.
Plan the sequence and spacing
Decide how many emails and the gap between each. The first goes immediately. The second follows after a day or two, while the sign-up is still remembered. Later messages spread out, with the gaps widening, and the whole series finishes within the first couple of weeks; beyond that the person should be on the regular programme, not still being welcomed. Set a sending window in the recipient's local time where the platform supports it, so that a sign-up at midnight does not produce a second email at dawn. Then decide the relationship with campaigns: either people in the series are held out of campaign sends until it ends, or they receive both, with a cap on total messages per week. Holding them out is the simpler and usually kinder choice. Write the plan as a table with the timing, the job and the action of each message before writing any copy.
Write the content for each email
Give each email one job, in an order that follows how a new subscriber's interest develops: who you are and why it matters to them; what the product or service actually does; proof that it works, from reviews, cases or results that can be shown; the offer or the specific ask; and a check-in that invites a reply or a preference. Each email carries one call to action with a label that says where it leads. Each must also stand alone, because people skip messages, so no email should depend on the reader having opened the previous one. Use the structure from the newsletter design and copy guide, so that the series looks like the mail that follows. Resist cramming: an email that introduces the range, the founder story and the referral scheme at once communicates none of them. Short, specific and in one voice.
Personalise by source
The sign-up source says what the person wanted, and the series should answer it. Someone who downloaded a guide wants the guide and then related content, and only afterwards the product. Someone who opted in at checkout is already a customer and should skip the sell, receiving the story and the proof in a lighter form. Someone who signed up for an offer wants the offer in the first email and the reasons to use it in the next. Someone from an event wants a reminder of what they saw. Build these as branches on the source property rather than as separate flows, so that the shared parts stay in one place, and always keep a default branch for sources that have no special handling. The properties that drive this, and the wider practice of grouping subscribers by what you know about them, are covered in the segmentation guide.
Set exits and suppression
List every event that should take a person out of the series, and set each as an exit evaluated before every send, not only at entry. A purchase is the main one: a new customer should leave the welcome series and, ideally, enter a short post-purchase sequenceAutomated messages that follow a customer from the order to a successful first use and towards a second order, alongside the order emails. instead. An unsubscribe exits everything. A reply can exit the series where the goal was conversation. Entry into a flow with higher priority, such as the one built in the abandoned cart flows tutorial, should pause the welcome series so that the two do not collide in the inbox. Then set suppression the other way: while someone is in the series, hold them out of campaign sends or cap their total frequency, and make sure hard bouncesAn email rejected permanently by the receiving server, usually because the address does not exist or the domain cannot receive mail. and complaints stop the flow immediately. A series without exits is the most common cause of the reply that asks why the shop is recommending something the customer bought last week.
Test the flow before it goes live
Create a test contact for each sign-up source and push each through the trigger. Check that the right branch fires, that the timing matches the plan, that every personalisation field falls back cleanly when the record is missing a name, and that every link opens the intended page with its tracking parameters. Open each email on a phone and in a desktop client, and in dark mode. Then test the exits: place a test order mid-series and confirm the next email does not arrive; unsubscribe a test contact and confirm the same. Launch with a single version of each email. Testing subject lines or content against each other is worth doing once the flow has enough volume for an A/B TestControlled comparison of two variants. to be read, and the mechanics are in the email metrics and testing guide; a test run on a trickle of new subscribers produces a winner by chance.
Launch and schedule the review
Switch the flow on for new entrants only. Do not push the existing list through it unless that is a deliberate decision with a reason, because a welcome email to someone who joined years ago reads as a mistake. Put a review date in the calendar a few weeks out, and decide now what the review will read: click-through (CTRShare of impressions that result in a click.) per email, conversion to the goal within the series window, unsubscribes and complaints per email, and where in the sequence people stop clicking. The pattern across emails is more informative than any single figure; a sharp drop at one message points at that message. Where volume allows, a small holdout group that receives only the first email gives the series an honest measure of what the rest of it adds. Document the flow as built: trigger, entry rules, branches, timing, exits and the date, so that the next person to edit it knows what they are changing. Before the switch is flipped, the email automation flow launch checklist takes the trigger, exits, branches, frequency and holdout through one list to tick.
Series template
The table is a starting point for a list whose goal is a first purchase or first use. Shorten it for a publisher, move the offer earlier for a source that signed up for one, and drop the proof email where the business has nothing it can honestly show yet. Each row names the exit check that runs before the message is sent, which is the part most templates leave out.
| Timing | Job | Call to action | Exit check before send | |
|---|---|---|---|---|
| One | Immediately | Confirm the sign-up, deliver what was promised, set expectations | Set preferences or open the promised item | Consent recorded; not already a customer |
| Two | A day or two later | Who you are and why it matters to this reader | Read the story or the about page | No purchase; no unsubscribe |
| Three | A few days later | What the product or service does, by the problems it solves | View the range or the key feature | No purchase; not in a higher-priority flow |
| Four | Several days later | Proof: reviews, cases, results that can be shown | Read a case or a review page | No purchase |
| Five | Around the end of the first fortnight | The specific ask, with the offer if one exists | Buy, trial or book | No purchase; frequency cap respected |
| Six | Shortly after | Check-in: a question, a preference, a reply | Reply or update preferences | Series complete; hand over to campaigns |
An outdoor equipment retailer's welcome series
An outdoor equipment retailer rebuilt its welcome series around two sign-up sources: a footer form and a trail-planning guide offered as a download. Both branches shared five emails over 12 days, sent at 0, 1, 4, 8 and 12 days, with the guide branch leading with the download and holding the product email back to day 4. In the first three months, 9,400 people entered the series: 6,100 from the footer form and 3,300 from the guide. The guide branch produced 410 first purchases within 30 days of sign-up against 520 from the larger footer branch, and its unsubscribe count per email was about a third lower. A holdout of 500 subscribers who received only the first email produced 21 purchases in the same window, which the team used to estimate that the rest of the series added roughly 60 purchases per thousand entrants. The weakest link was email three on the footer branch, where clicks fell by half; it was rewritten around a single product category instead of the whole range.
A welcome series is the first stage of a broader system, and the lifecycle email programme playbook shows how onboarding, retention and win-back flows are planned and run together.
Subscribers captured by a popup enter this series too, and the exit-intent popup experiment counts the revenue they bring through it when judging whether the popup is worth its interruptions.
When a live series stops sending, or sends far fewer welcomes than there are sign-ups, the diagnosis for an automated email flow that is not sending lines up events, entrants, sends and deliveries to find the stage that broke.
Verify it worked
- Push one test contact per sign-up source through the trigger. Each should receive the first email immediately and land in the branch for its source.
- Compare test arrival times with the timing table from your sequence plan. Each gap should match the plan.
- Place a test order mid-series. No further series email should arrive. Repeat with an unsubscribed test contact.
- Preview each email with no name on record. The greeting should fall back cleanly and every link should open the intended page.
- Read the flow notes. They should hold the goal, metric, entry rules, exits and review date.
If it goes wrong
- The welcome arrives the next afternoon. The trigger is probably a nightly import. Connect the form so the platform sees each sign-up as it happens.
- A new customer keeps receiving sales emails. Exits are probably checked only at entry. Set the purchase event as an exit before every send.
- Every test contact lands in the default branch. The source property was probably not captured at entry. Pass the source from each form, then rerun the tests.
- A new subscriber gets several emails in one day. Campaigns and the series are both sending. Hold series members out of campaigns, or cap their total messages.
- Long-standing subscribers receive a welcome email. The existing list was probably pushed through the flow. Restrict entry to new sign-ups only.
Next steps
- Read the abandoned cart flows tutorial to build the higher-priority flow that should pause this series.
- Read the email metrics and testing guide before your first review, to learn when a test has enough volume to be read.
- Read the segmentation guide to branch on more than the sign-up source.
- Read the lifecycle marketing guide to see which stages follow onboarding.
Common mistakes
- No written goal. A series built email by email with no outcome in mind ends up as six newsletters.
- A nightly sync as the trigger. The welcome arrives the next day, after the moment has passed.
- Selling in the first email. The person asked for a guide or a confirmation; give them that.
- Every email dependent on the last. People skip; each message has to stand alone.
- One flow for every source. A guide downloader and a checkout opt-in want different things.
- Exits checked only at entry. The series keeps selling to someone who bought on day one.
- Campaigns and the series both sending. Several emails a day in the first week is how a new subscriber becomes an unsubscribe.
- Backfilling the whole list. A welcome email to a long-standing subscriber reads as a mistake.
- Calling a test too early. A handful of new subscribers a day is not enough volume to compare subject lines.
