SaaS Onboarding Email Sequence: 6 Emails With Templates

By Hasan · November 11, 2026 · 8 min read

SaaS onboarding email sequence: 6 emails with templates

A good SaaS onboarding email sequence has six emails over about two weeks. Each one has a single job: welcome, first action, help, a second feature, a nudge for people who stalled, and a check-in. Send each email only to people who have not yet done the thing it asks for. Pair it with an in-app step, because the email only gets someone back. The app is where they get value.

This guide gives the sequence, the timing, a template for each email, and the events that decide who gets what. I build JustOneCX (disclosure), which handles the in-app side (tours, checklists, surveys) but does not send email. The sequence works with any email tool.

What should an onboarding email sequence do?

It should move a new signup to your activation event, the one action that shows they got value. Everything else in the sequence is secondary.

That gives you a simple rule: every email asks for one action, and that action is a step toward the activation event. An email with three links and four ideas gets none of them done.

What are the 6 emails and when do you send them?

# Email Send when Goal Stop sending if
1 Welcome Right after signup Confirm they are in. Point to the first step. Never stop. Always send.
2 First action Day 1, if they have not done it Get them to do the first key step They did the first step
3 Help Day 3 Offer a person or a guide They did the activation event
4 Second feature Day 5, after activation Show the next useful thing They already use it
5 Stalled Day 8, if still not activated Ask what is in the way They activated
6 Check-in Day 14 Ask for a short reply or survey They replied

The key idea is the right-hand column. Sequences that send all six emails to everyone feel like spam. A person who activated on day 1 does not need the stalled email on day 8.

Template 1: Welcome

Subject: You are in. Do this first.

Hi {first_name},

Thanks for signing up for {product}. The fastest way to see what it does is to {first_step}. It takes about {time}.

{button: Start now}

If you get stuck, reply to this email. A person reads it.

{sender_name}

Why it works: it has one button, a time estimate and a real reply address. Do not list every feature here. The welcome email has the highest open rate in the sequence, so spend it on one action.

Template 2: First action

Subject: One step left to {outcome}

Hi {first_name},

You set up your account yesterday. The next step is to {first_step}, and then {product} starts showing you {outcome}.

Here is a short guide: {link}

{button: Do it now}

Send this only to people who have not done the first step. Name the outcome, not the feature. "Start seeing which users drop off" is clearer than "Create a funnel".

Template 3: Help

Subject: Stuck? Here is the quickest way through

Hi {first_name},

Most people get stuck at one of two places: {common_blocker_1} or {common_blocker_2}. Here is how to fix each one:

  • {blocker 1 fix, one line, link}
  • {blocker 2 fix, one line, link}

Want me to walk you through it? Reply with a good time, or book a short call: {link}

Fill in the blockers with real ones from your support inbox and your drop-off data. If you do not know your blockers yet, this email is a reason to find out.

Template 4: Second feature

Subject: Now that {activation_result} works, try this

Hi {first_name},

You have {activation_result}. People who go one step further and {second_feature_action} tend to {benefit, from your own data or leave out}.

{button: Try it}

Send this only after the activation event. Do not make claims you cannot back with your own numbers. If you have no data yet, leave the benefit out and just describe what the feature does.

Template 5: Stalled

Subject: What got in the way?

Hi {first_name},

You signed up a week ago but have not {activation_action} yet. I am trying to learn what gets in the way.

Could you reply with one line? For example: "not the right time", "could not figure out X", "missing Y". Every answer goes straight to the team, and I will answer you.

{sender_name}

This is the most valuable email in the sequence. It costs nothing and it tells you what is wrong with your first-run experience. Read every reply.

Template 6: Check-in

Subject: Quick question about {product}

Hi {first_name},

Two weeks in. One question: how easy was it to get started? {link to one-question survey}

It takes ten seconds, and I read every answer.

A one-question survey here works well, for example a customer effort question. See customer effort score questions for wording.

How do you decide who gets which email?

You need three facts per person, and each one is an event or a trait:

  • When they signed up. That is the first time you identified them.
  • Whether they did the first key step. Send this event from your app.
  • Whether they hit the activation event.

In JustOneCX you send these with identify() and track(), from the analytics definitions. Your email tool then reads the same events (through its own integration or your backend) to decide who stays in the sequence. The key point is that the app and the email tool use the same event names, so "did the thing" means the same in both.

How do you pair each email with an in-app step?

Email gets people back. The in-app step makes the action easy once they arrive.

  • Email 1 and 2: show a product tour or a short checklist the next time the person opens the app, so the first step is one click away. The post on the onboarding checklist shows how to build one that completes when your code sends the event.
  • Email 3: point to a help article. See chat and help center for choosing between them.
  • Email 4: show a short in-app announcement about the second feature instead of a long tour.
  • Email 6: show the survey in the app as well as in the email. People who ignore the email may answer in the app.

For the wider picture, read user onboarding best practices.

How do you know the sequence works?

Do not judge it by open rate. Judge it by activation.

  1. Activation rate of new signups. Compare people who got the sequence with the period before it, as a share of new users who reached the activation event.
  2. Which email people act on. If email 2 gets clicks but email 3 gets none, cut email 3.
  3. The replies to email 5. Group them. The top three reasons are your onboarding to-do list.
  4. Unsubscribes. A high unsubscribe rate on one email means the timing or the ask is wrong.

Change one email at a time and wait for enough signups to compare. A handful of people tells you nothing.

What mistakes should you avoid?

  • Sending the same sequence to everyone. Split by what they did.
  • Putting several asks in one email.
  • Writing like a newsletter. Short and plain beats designed.
  • Sending from a no-reply address. Replies are the best research you will get.
  • Never ending the sequence. Stop when the person has activated.

Frequently asked questions

How many emails should a SaaS onboarding sequence have?

Five to seven over the first two weeks is a good start. The count matters less than sending each email only to people who need it.

When should the first onboarding email go out?

Right after signup. The person is in your product at that moment, so the welcome email arrives while they are still paying attention.

Should onboarding emails be plain text or designed?

Plain, short emails from a named person usually read as more personal. Use a designed email if your brand needs it, but keep one clear button.

Do I need an email tool that reads product events?

It helps a great deal. Without product events you can only send by time since signup, which means everyone gets every email. Even a basic setup that stops the sequence when the activation event happens is better than none.

Can I send onboarding emails from JustOneCX?

No. JustOneCX covers the in-app side: tours, checklists, announcements, surveys, chat and analytics. Use your email tool for the emails and use the shared event names to keep both in step.

See it working in 2 minutes

Try the live demo

Related