November 6, 2026

SaaS onboarding emails: a simple sequence that works

Onboarding email has one job: get a new user to the moment your product becomes useful. You do not need a long sequence for that. You need a few emails tied to what each person has actually done.

Find your activation step first

Pick the one action that shows someone got value from your product, such as sending a first campaign or inviting a teammate. Every email in the sequence should move people toward it.

The sequence

Treat the timing as a starting point and adjust it to how long your product takes to set up.

  • Right after signup: welcome them and point to the single first step
  • Day 1: show the shortest path to the activation step
  • Day 3: a reminder for people who have not done it yet
  • Day 7: a use case or example from their kind of work
  • Day 14: ask what is in the way, and invite a reply

Use conditions, not a fixed calendar

A reminder to do something the person already did makes your emails look automated and careless. Before each email, check whether they completed the step, and skip it or move them on if they did.

For this to work, your app has to tell your email tool what happened. Send an event when someone reaches a milestone, and let the workflow react to it.

What each email should say

The welcome email is the one most people will read, so make it about their next step and not about your company. One sentence of thanks is enough, followed by one link that takes them straight to where the work starts.

The day 1 email removes friction. Show the shortest way to the activation step, with one screenshot or short list if it helps. If your product needs setup such as a DNS record or an integration, say how long it takes.

The day 3 email goes only to people who have not finished. Name the most common reason people get stuck and how to get past it.

The day 7 email shows what a good result looks like. Use a real example from someone doing similar work, because people move faster when they can picture the outcome.

The day 14 email is a question. Ask what stopped them, from a real person, and make it easy to reply. The answers are often the most useful product research you will get.

A sample welcome email

Here is the shape of a welcome email that does its job. Note what it leaves out: no feature list, no social links and no second call to action.

  • Subject: Your account is ready, here is the first step
  • First line: Thanks for signing up. The fastest way to see what this does is to send your first campaign
  • Middle: It takes about five minutes, and you only need your contact list
  • Link: Create your first campaign
  • Sign-off: A real name and an address people can reply to

What to do after activation

Reaching the activation step ends the onboarding sequence, but not the conversation. Move these people to a second track that helps them go deeper: inviting teammates, trying a second feature or connecting an integration.

People who never activate need a different ending. After the last email, stop. Mailing inactive users for months hurts your engagement numbers and your sending reputation, and it rarely brings them back.

Common mistakes

These are the patterns that make onboarding email underperform.

  • Sending every new user the same emails regardless of what they did
  • Listing all your features instead of focusing on one step
  • Using a no-reply address when replies are your best source of feedback
  • Starting the sequence days after signup, when interest has already faded
  • Never reviewing the sequence after launch

Keep each email to one action

Write a subject line that says what the email is about, keep the text short and give one clear link. An email with five buttons usually gets none of them clicked.

Measure the step, not the opens

Open rates are unreliable because of privacy features such as Apple Mail Privacy Protection. What matters is how many new users reach the activation step, and how long it takes them.

Building it in Reloops

A Reloops workflow starts from a trigger like a new contact or an event from your app, then waits, checks a condition and sends. That covers every step of this sequence.

Get started