Onboarding Email Sequences

People sign up with a goal, hit one small obstacle, and quietly leave. Onboarding email exists to find that obstacle early and remove it, wherever the person happens to be when they read it.

By Owen Hargrove · Updated 7 Oct 2026

Design around milestones, not a calendar

A fixed sequence of seven emails sent on days one through fourteen will, sooner or later, congratulate someone for a step they skipped and remind someone else about a step they finished last Tuesday. Instead, list the milestones that predict a healthy account, attach one email to each, and send it only to people who have not reached that milestone yet.

The sequence below uses a document-collaboration product as the example. Your milestones will differ; the pattern of one blocker, one email, one exit condition will not.

Best pick for B2B products with teams and companies as the unit: Userlist, whose pricing page describes lifecycle email and in-app messages with segments for both users and companies. Best pick when you need deeper branching and your developers can send events: Customer.io. For a small product that wants to launch onboarding this week: Loops. Costs follow below.

A 14-day outline with exit conditions

Timing is illustrative; set yours from how long your fastest activated users took to reach each step.

  1. Immediately after signup: confirm and name one action. Say the account is ready and link to the single step that produces a first result, such as creating a document from a template. Nothing else. Exit: first document created.
  2. Four hours later, only if the first step is undone: remove the blocker. Offer a template, a two-minute video, or a reply address. The blocker is usually blank-page anxiety or a missing integration, and a template solves both.
  3. Day 2, people who finished step one: build on it. Congratulate in one line and introduce the next capability that successful accounts use early, such as sharing a document with a colleague. Exit: share action taken.
  4. Day 3, people who have not shared: show the payoff of collaboration. One short story about a team that changed how it works, with an invite link prefilled.
  5. Day 5, integration-fit plans only: connect the tool they already use. Send it to accounts whose plan includes integrations and who have not connected one.
  6. Day 8, no meaningful result yet: a human note. Plain text from a named person, offering a ten-minute session. This is the last educational push before a sales assist for qualifying accounts.
  7. Day 14: ask for feedback. A two-question survey about what was clear and what was missing. Replies go to product as well as support.

Splitting tracks by who the person is

The founder who created the workspace

Needs orientation: what to set up first, how to bring colleagues in, how billing works. This is the track outlined above.

The teammate who was invited

Skip the orientation entirely. They arrive because someone asked them to look at something, so the first email should link to that thing and explain how to comment or edit. Routing invitees through the creator's track wastes their attention and delays team activation.

The person already moving fast

Someone who has reached three milestones in two days needs no nudges. Move them to advanced tips and pricing information earlier, and flag the account for a sales or success conversation if the plan allows.

The person who signed up and vanished

After the first-step email and one check-in, move them to the re-engagement program rather than continuing to send onboarding to an inbox that does not read it.

Finding the milestones in the first place

Look at your accounts that are still active after six months and ask what they did in week one that churned accounts did not. Candidates include creating something, inviting someone, connecting a data source, and returning on three separate days. Choose the two or three that you can influence with a message. Do not pick "opened onboarding emails", because that measures the emails, not the product.

Reply mining adds what analytics misses. Read the first two weeks of support questions and cancellation notes, group them by the step where people got stuck, and write the next email about the biggest group. Often a single confusing screen accounts for most of the drop-off.

Writing rules for onboarding messages

  • One purpose, one link. If an email holds two calls to action, the stronger one wins and the other goes unread.
  • Use their data. "You have created two documents and invited nobody" is more useful than any general tip, provided your tool can read product events.
  • Plain format early. The first emails often read better as short, nearly text-only messages from a person than as designed newsletters.
  • Reveal in order. An advanced feature in email two overwhelms; the same feature in email six rewards someone who has earned it.
  • Respect transactional boundaries. Verification and password messages belong outside the marketing flow and should never wait behind a queue of promotional sends.

What to measure

Track completion of each milestone, median time from signup to each one, and how many people reach the final milestone with and without receiving the email attached to it. Withhold that email from a small random group so you can see its effect, and report unsubscribes and complaints per email so you can spot a message that is hurting more than helping. Graduates leave the program when they reach habitual use, defined by the usage pattern that correlates with retention in your own data, and enter ordinary lifecycle messaging.

Costs at 5,000 and 10,000 contacts

Tool Around 5,000 Around 10,000 What the vendor's page says
Loops $48 at 4,788 subscribers $99 at 9,998 subscribers Free plan sends 4,000 emails a month to the 1,000 newest contacts; no seat fees
Customer.io $100 at 5,000 profiles $145 at 10,000 profiles Essentials billed monthly; visual workflow builder; email, push and in-app messages
Userlist Priced per tracked user Basic $149; Professional $349 $10 or $12 per extra 1,000 users; conversion goals on Professional
Encharge Growth $179 Growth $249 Monthly billing; its site describes user onboarding and behavior emails

Counting matters: Customer.io counts every profile that exists during the billing month, including ones you later delete, so clean out test accounts before the cycle starts rather than after. Loops sets its free-plan limits by recent contacts, so a growing product will cross into the paid plan sooner than the headline of unlimited contacts suggests.

Verdict and related pages

Write the milestones first, then pick the tool that can test for "has not done X". Userlist suits B2B accounts with several users, Customer.io suits teams that need conditions on event data, and Loops suits small products with simple paths. The onboarding sequence hands over to trial conversion when the account has a deadline, and the earlier welcome step is covered in welcome sequences. For shortlists by situation, see nurturing tools for user onboarding.

Onboarding FAQ

How many onboarding emails should I send?

As many as there are unfinished milestones worth a message, commonly four to seven. People who complete a milestone should leave its email behind immediately.

Should onboarding emails sell?

Teach first. An upgrade pitch to someone who has not yet seen the product work earns nothing and trains them to ignore later messages.

When does onboarding end?

When the person reaches the usage pattern you have linked to retention, not when the last scheduled email goes out. Those who never reach it move to re-engagement after a month.

How do I find where people drop off?

Count how many reach each milestone in order, then read support and cancellation replies for the step with the biggest gap. Fix that one before polishing anything else.