Onboarding Email Sequence Template With Six Emails, Timing and Metrics

An onboarding email sequence template should contain six emails, sent from Day 0 to Day 21 or later, each written to the same four-part spec: a trigger that sends it, one job, an exit condition that stops it and one metric. Stop setup nudges once a user activates. To judge the sequence, compare goal completion against a holdout group of about 10% of entrants who get no emails.

What an onboarding email sequence template should contain

The short answer: six emails, each written to the same four-part spec. A trigger that sends it, one job it has to do, an exit condition that stops it, and one metric that tells you whether it worked. Write those four lines for every email before you write any copy.

The job of the whole sequence is narrow. Loops defines an onboarding email as "an automated message sent after signup to help a user complete the first action that makes the product useful" (Loops). That first action is your activation event, and every email below either moves a user toward it or builds on it.

Automation is worth the setup time. MailerLite says its data shows automated emails have open rates 15% higher and click rates 152% higher than regular campaigns (MailerLite). Those figures compare against regular campaigns, so they are not targets for any single email. Our lifecycle email benchmarks cover that.

The six-email spec

The send days follow the starting schedule Loops publishes, which runs from Day 0 to Day 21+ (Loops). Adjust the delays to how long your setup usually takes.

Email	Trigger	One job	Exit condition	Metric (our reading)
1. Welcome + first action	Signup, Day 0	Confirm the account and give one next step	First action completed	Share of signups who click through to the first action
2. Finish the first task	Day 1	Get the activation event done	Activated is true	Activation rate for the cohort
3. Remove a blocker	Day 3, not activated only	Address the most common stall reason	Activated is true	Share of stalled users who activate after this email
4. Try the next task	Day 7, activated only	Introduce one feature that fits their role	Feature used	Adoption of that feature
5. Relevant use case	Day 14	Show a customer example or a paid or team feature	Upgrade or teammate invite	Upgrades or invites from this email
6. Re-engage or wrap up	Day 21+, inactive only	Invite the user back, then end the sequence	User returns or sequence ends	Share of inactive users who return

Two rules hold the spec together. First, stop setup nudges at activation: Loops advises you "Map one email to each required onboarding step, then stop setup nudges when the user activates" (Loops). Mirror the activation event to a contact property and check it before every remaining send.

Second, give each email its own goal, not just the sequence.

If you run a time-limited trial, adapt email 6. Intercom suggests that "2 days before their trial ends, unconverted customers should get a message with an incentive" (Intercom). Our guide on freemium vs free trial covers which model fits your product.

When should onboarding emails be sent

Timing has two parts: when the first email goes out, and how long each later delay runs. The first is fixed by signup. The rest should come from your own product data, not from a template's calendar.

Start the clock at signup, end it at day 30

Intercom's help guide says that on day 1 customers should receive a warm welcome message, gated by the rule "Web sessions is greater than 1". A few days later comes a check-in, for example to users who "Entered your series 4 days ago", offering help.

The same guide bounds the audience as users who "Signed up less than 30 days ago" and "Paid is false." That gives the sequence a hard edge. Anyone who pays or ages past day 30 leaves.

Some sends should fire on behavior instead of a delay.

Moment	Trigger rule	Purpose (our reading)
Day 1	Web sessions is greater than 1	Greet, give one next step
Day 4	Entered your series 4 days ago	Offer help before users stall
Third use	Created project count is 3	Teach depth once the habit forms
Whole window	Signed up less than 30 days ago	Keep the audience to new, unpaid users

Set delays from your own time-to-value data

Loops advises: adjust the delays to the time your setup usually takes, and skip reminders for steps the user has completed. It also suggests you use product data to set a Timer for the normal completion window for that first action.

Here is a method you can run this week:

1. Pick the single event that marks activation.
2. Pull signup and activation timestamps for one recent cohort.
3. For users who activated, measure the gap between the two. This is your time-to-value.
4. Place the blocker reminder just after the point where most activators have already finished.

A worked example, with round numbers that are not a benchmark: say 100 of 1000 signups activated within 30 days. If 50 of those 100 activated after day 3, a day 3 reminder lands while half of your eventual activators are still mid-setup. In our reading, that reminder is too early. Push it out until the share still in progress is small, and re-run the check each quarter as the product changes.

Compare your results against our activation rate benchmarks. Treat any delay change as a test, using the steps in how to run a growth experiment.

How to trigger emails on behavior and suppress people who already did the thing

Build each automation around a single behavior you want to see. Customer.io's onboarding recipe puts it plainly: each automation should be focused on nudging them towards a particular goal. If you need three behaviors, build three automations. Do not cram them into one.

Step 1: Pick the trigger

A segment trigger fires when someone joins a group. In Customer.io you click Choose trigger on your workflow then select Segment change from the panel. The default audience is a segment called "Signed up," which is composed of anyone whose created_at attribute is a timestamp. Narrow it with a new segment when the series targets one plan or role.

Decide whether the series reaches people already in the segment. By default, automations are forward-looking, so existing users get nothing unless you opt them in.

Step 2: Set exit conditions so finishers stop getting nudged

By default, a person continues through an automation until they stop matching the automation’s trigger or filter conditions. You can add your own, and exit criteria are OR statements; people exit when they meet any condition in your exit criteria. Any one match removes them.

Condition type	What it checks	Onboarding example (our reading)
Profile attribute	A field on the profile	Profile marked complete
Event	Whether an event has or has not performed	Created first project
Segment	Membership or non-membership	Joined the Activated segment

Here is an example, not a benchmark. If 1000 people enter and 100 finish their profile before the second email, the exit condition holds the second send to 900. Without it, 100 people get a reminder for something they already did. In our reading, that kind of mismatch is how a sequence loses trust.

One exception: if people should always finish the automation, remove all exit conditions. That fits a fixed course, not a nudge series.

Step 3: Measure the behavior, not the email

Define the conversion as the goal behavior itself. Customer.io notes that conversions can be a more reliable way to track success than opens and clicks.

Where onboarding hands off

Onboarding is the first stop. Customer.io groups the lifecycle into five general stages: acquisition and onboarding, activation, retention, monetization, and churn prevention or win-back. Its next flow starts on Trigger: User completes first milestone. So the event that exits someone from onboarding is the one that enters them into activation. We think using the same event for both keeps people from falling between flows. Later flows feed retention.

What is a good open rate for a welcome email

Published benchmarks give you a range for opens and clicks. Before you use them, check two things: who is in the dataset, and what an "open" measures.

Klaviyo's average automated flow click rate is 5.58%, compared with 1.69% for campaigns.

Email click rates, campaigns vs automated flowsPer cent

1. Campaign average1.69%
2. Campaign top 10%3.38%
3. Automated flow average5.58%
4. Automated flow top 10%10.5%

Email click rates, campaigns vs automated flows

Item	Value, %
Campaign average	1.69%
Campaign top 10%	3.38%
Automated flow average	5.58%
Automated flow top 10%	10.5%

Klaviyo analyzed data from over 205,000 brands, and its automated flows category covers moments like welcoming new subscribers, recovering abandoned carts. Omnisend covered 470 million automated sends across 27,000+ brands. Neither figure is specific to a SaaS onboarding sequence. Treat them as a rough reference, not a target.

Klaviyo, all industries	Campaigns	Automated flows
Average open rate	31%	32.2%
Top 10% open rate	45.1%	45.8%
Average click rate	1.69%	5.58%
Top 10% click rate	3.38%	10.48%

Opens barely separate the two types. Clicks do. Klaviyo's average flow click rate of 5.58% sits 3.89 points above its campaign average of 1.69% (Klaviyo). For comparison, Omnisend's 2025 average open rate across industries was 30.22%.

Why open rate misleads

Apple Mail Privacy Protection (MPP) inflates opens. Klaviyo notes that Apple opens each email for any user with MPP enabled, whether or not they actually read it. Omnisend adds that since 2021, Mail Privacy Protection has been able to preload tracking pixels. If your list skews toward Apple Mail users, a welcome email can show a high open rate even when few people read it.

A high open rate can also sit next to weak results. In Omnisend's data, wedding brands had the highest open rate at 52.43%, yet a conversion rate of only 0.04%.

What to measure instead

Track two numbers for each email in the sequence:

1. Click-through rate: the share of delivered emails that produced a click on the main call to action.
2. Goal-completion rate: the share of recipients who completed the one task that email asks for, such as creating a first project. Count it in your product analytics, not in your email tool.

Here is a worked example with round numbers, not a benchmark. Your Day 1 email goes to 1,000 new signups and 100 of them click, a 10% click-through rate. If 20 of those 100 clickers finish the first task, that is a 20% completion rate among clickers. The completion rate tells you whether the email moves people toward activation. The open rate does not.

We use open rate only as a deliverability check. In our reading, a sudden drop usually points to a spam-folder problem. To judge whether the sequence works, compare goal completion against your activation rate benchmarks. For wider lifecycle figures, see our lifecycle email benchmarks.

How to measure an onboarding sequence with a holdout group

A holdout answers one question: would these people have taken the action without the email. Open and click rates cannot answer it. In a Customer.io holdout test, the unsent variant is never opened or clicked, so the message you send always wins those metrics. Compare goal conversion instead.

The method in five steps

1. Set a goal for the series and one goal per email. The series goal is usually activation. Each email gets the goal tied to the action it asks for, such as inviting a teammate. Customer.io measures a conversion as an attribute change or an event that occurs after a person receives a message in the workflow.
2. Hold out a random share of entrants. Rejoiner builds control groups from a random set of customers that represents 10% of the sample size it sends to.
3. Keep non-marketing mail flowing. Klaviyo lets you select flows that override the holdout group, such as transactional messages. Password resets and receipts should reach everyone.
4. Pick the measurement window before launch. Rejoiner compares the groups after 90 days or so, and Klaviyo recommends 3 months for a global test. For a single onboarding email, we think a window that matches your trial or setup period fits better.
5. Compare goal conversion between the groups. In Customer.io, people in the holdout group register conversions when they perform the goal action within the conversion time window, even though they got no message.

A worked example

These are example inputs, not a benchmark. 1000 people enter the sequence and you hold out 100 of them, so 900 get the emails (1000 minus 100).

Within a 14-day window, 20 of the 100 held-out people activate, a 20% rate. In the emailed group, 40 of every 100 activate, a 40% rate. The difference, 40% minus 20%, is 20 percentage points of lift you can credit to the sequence.

Check your group sizes with the sample size calculator first. If Customer.io shows "Not significant, need more data", let the test run longer. Our growth experiment guide covers writing the hypothesis down beforehand.

When you are below a profile threshold

Klaviyo's Global Holdout Groups are available to customers who have over 400,000 profiles. If your list is smaller, two options work:

• Per-email holdout inside the automation. Customer.io notes it is easier to set up an A/B test where one variant is the holdout. The held-out send goes to an internal message trap and does not affect deliverability ratings.
• Manual split in any email service provider. Rejoiner suggests holding out every customer with a Customer ID that ends in ‘3’. Tag that cohort at signup and exclude it from the sequence.

A worked example for a self-serve project tool

This is our own example. The numbers are round example inputs, not benchmarks. Swap in your own figures before you act on any of them.

The setup

A self-serve project tool gets 1,000 signups a month. The team holds out 10 percent, so 100 people get no onboarding emails and 900 get the full six-email sequence.

The sequence chases that single event. Customer.io's onboarding recipe puts it plainly: each automation "should be focused on nudging them towards a particular goal." The holdout should also contain only new signups. Customer.io notes that by default, automations are forward-looking, which keeps people who signed up before the test out of both groups.

Each email's goal and goal rate

Every email has one job. Its goal rate is the share of people who received it and then completed that job before the next email was due. Anyone who already completed it is suppressed, as covered earlier.

Email	Sent to	Goal	Example goal rate
Welcome	Every new signup	Create first project	40%
Project nudge	No project yet	Create first project	20%
Invite prompt	Project, no invite	Invite one teammate	20%
Template tip	No project yet	Create first project	10%
Invite reminder	Project, no invite	Invite one teammate	14%
Last call	Not yet activated	Full activation event	10%

A low goal rate on one email tells you which email to rewrite first. It does not tell you whether the sequence works. Only the holdout comparison answers that.

The lift calculation, step by step

1. Count activations at day 14 in each group.
2. Treatment: of the 900 people who got emails, 50 percent activated, which is 450 people.
3. Holdout: of the 100 people who got nothing, 40 percent activated, which is 40 people.
4. Absolute lift: 50 percent minus 40 percent is 10 percentage points.
5. Relative lift: 10 points on a holdout base of 40 percent is a 25 percent relative lift.
6. Incremental activations: 10 percent of 900 treated people is 90 activations the emails added this month.

Report the 90, not the 450. Without the holdout, the team would credit the emails with all 450 activations, and 360 of those people would have activated anyway.

In our reading, a holdout of 100 people is too small to trust after a single month. Pool several monthly cohorts before you call the result, and follow the decision rules in how to run a growth experiment. To see what 90 extra activations a month are worth in revenue, put the figure into the growth model template.

The traps and the steps to ship this week

Three traps undo most of the work in the earlier sections. Each one has a fix you can make inside your current tool, without a rebuild.

Trap	What it looks like	Fix this week (our reading)
Time-only drip	Every signup gets email 3 on the same day	Gate each nudge on the step still being incomplete
Competing links	3+ competing links in one email	One primary button, secondary links moved to a footer line
No holdout	Success judged on opens and clicks	One email tested against a group that gets nothing

Trap one: the same day for everyone

Loops lists "Same fixed day for everyone" as the common failure for send timing. It sets that against messages triggered by signup or behavior. Its rule for reminders is short: send a setup reminder only to people who have not completed that step. A fixed day is fine as a delay. It should never be the only condition.

Trap two: too many links

The same Loops table puts the good version as one button, one outcome, and the failure as 3+ competing links. In our reading, most of the time the extra links are a docs link, a blog link and a social row. Move them under the sign-off as plain text, or cut them.

Trap three: no holdout

The holdout section above covers the setup. The part teams skip is acting on the result. In Customer.io, if your winner is the holdout, the message action is removed from your workflow entirely. We think that is the right default: an email that does not beat silence should go.

A checklist for this week

1. Tuesday. Name one primary action per email. Rewrite the subject line to match it.
2. Wednesday. If you branch by role, add a default path. Loops advises making the right-most filter empty so contacts with no role still get emails. Then test both incomplete and completed setup states.
3. Thursday. Send a preview to a phone and follow the main link. Confirm it opens the exact task the email names.

Pick one email for the holdout, not the whole sequence. The method in how to run a growth experiment applies here unchanged.

What this page does not cover

This page does not give SaaS-specific open or click benchmarks, write the copy for each email, or choose an email tool for you. It also leaves out which pricing model fits your product and any rules on email consent or privacy, and nothing here is legal advice.

Related on Race to Scale: What is a good activation rate? Benchmarks by product type and how to define yours; A/B test sample size and duration calculator, with the formula; Growth experiment template with ICE scoring, a weekly cadence and a backlog you can copy.