By Mehdi HassanWhat should a SaaS onboarding email sequence include?
A SaaS onboarding email sequence should include a welcome email, a few behavior-triggered nudges that help stalled users reach their first result, a short message when they get there, and clear emails around the end of a trial. That's usually five to eight emails, but the number matters less than the triggers.
The difference between a sequence that pulls users back and one that gets ignored is whether it knows what the user did. "Day 3: check out our integrations" goes to everyone, including people who already connected three. "You created a project but haven't added data yet; here's the fastest way" goes only to people stuck at that step. Emails are one part of activation, alongside the product itself; our SaaS onboarding UX guide covers the rest.
Which activation emails should you send, and when?
Send activation emails based on progress toward your activation event, with one email for each point where users commonly stall. The table is a starting template for a self-serve product with a trial. Replace the triggers with the steps of your own path to value.
Trigger | Goal | One link to | |
|---|---|---|---|
Welcome | Account created | Start the first step | The first setup screen, already open |
Setup nudge | No key setup step within a day or so | Remove the blocker | The step, with a shortcut or template |
Value nudge | Setup done, no first result yet | Reach first value | A template or example that gets them there |
First-win confirmation | Activation event reached | Reinforce and suggest the next step | The next valuable action |
Team nudge | Activated, still solo, in a team product | Invite a collaborator | The invite flow |
Trial ending | A few days before trial end | Decide clearly | Billing, with plan summary |
Win-back | No activity for a while after signup | Return or tell you why | The last thing they worked on, or a one-click reply |
Exit rules matter as much as triggers. When a user completes the step a nudge was about, cancel that nudge. When they convert, stop trial emails. Most email and product analytics tools can do this with event-based conditions, but someone has to design the logic deliberately.
How do you tie onboarding emails to in-app events?
Tie onboarding emails to in-app events by sending product events to your email tool and building each email around one event or the absence of one. That requires agreeing on event names early and tracking the few that define the path to value. The setup is mostly a product decision, not a marketing one.
Define the activation event
Agree on the action that marks a user reaching value. Our guide to finding your SaaS aha moment explains how to choose it.
List the steps before it
Write down the two to four actions between signup and activation, such as connecting data and creating the first project.
Track each as an event
Instrument those actions in your product and send them to your email or customer messaging tool, with useful properties like project name.
Write one email per stall point
For each step, write an email that triggers when a user hasn't done it after a reasonable delay, and exits when they do.
Deep-link every button
Each email opens the exact screen for the next step, with the user logged in where security allows.
Review the logic as a flow
Map the full sequence on one page so you can see overlaps, gaps and the maximum number of emails one person could get.
How should a welcome email sequence be written?
A welcome email sequence should read like a helpful person explaining the next step, not like a brand announcement. Each email has one point, a subject line that says what it's about and a single button. The copy should use the user's words for their goal, which you can learn from your onboarding survey, sales calls or support tickets.
- Subject lines say the benefit or the next step. "Your first report is two clicks away" beats "Welcome to the family".
- One idea per email. If you want to mention three features, you have three emails or none.
- Personalize from data you have. Use the project name, the template they chose or the integration they connected.
- Send from a person where it fits. A founder or product lead's name, with a real reply-to address, invites answers you can learn from.
- Keep the design simple. Plain or lightly formatted emails often read as more personal and render reliably across email clients.
For example, suppose a hypothetical reporting tool writes its value nudge
For example, suppose a hypothetical client-reporting tool sees that a user connected their analytics account but hasn't created a report. A weak email would say: "Did you know our reports are fully customizable? Explore templates, scheduling and white-labeling."
A copywriter would write something closer to this. Subject: "Your Acme Analytics data is ready for its first report." Body: "You've connected Acme Analytics. The quickest way to see it in a client-ready format is the monthly overview template, which fills itself in from your data. It takes about a minute." Button: "Create the monthly overview." The button opens the template with their data loaded. This is an illustration, not a real product's email or results.
What should trial emails say?
Trial emails should tell users plainly what happens when the trial ends, what they've done so far and what they'll keep or lose. Surprises around billing are the fastest way to lose trust and invite chargebacks. Clarity also converts better than pressure, because users who understand the decision make it.
- Before the end: send a reminder a few days ahead with the end date, the plan they'd move to and how to cancel.
- Show their progress: summarize what they've set up or created, so the value is concrete.
- Be honest about limits: if data is kept or deleted after expiry, say so and when.
- For users who didn't activate: offer help or an extension instead of a hard sell. A short reply-to question often surfaces the real blocker.
- After conversion: stop trial messaging immediately and switch to a short confirmation with receipts and next steps.
If the trial requires a card, the reminder before the first charge is especially important. Treat it as a customer-service email, not a marketing one.
How do you measure onboarding emails?
Measure onboarding emails by whether recipients complete the step the email was about, compared with similar users who didn't get it. Open rates are unreliable because privacy features in some email clients load images automatically, which inflates opens. Clicks are better, and the target event is best.
Metric | What it tells you | Reliability |
|---|---|---|
Open rate | Rough interest in the subject line | Low, affected by privacy features |
Click rate | Whether the email made people act | Medium |
Step completion | Whether recipients did the thing the email was about | High, this is the main metric |
Activation lift vs holdout | Whether the email changed behavior at all | Highest, needs enough volume |
Unsubscribes and replies | Tone, frequency and relevance | Qualitative but useful |
If your volume allows it, keep a small holdout group that doesn't receive a given email. It's the only clean way to know whether the email caused the behavior or just accompanied it. Emails also work best when the in-app experience matches, so look at the screen each email links to, including any empty states users land on.
What technical basics does an onboarding email sequence need?
An onboarding email sequence needs authenticated sending, a clear split between transactional and marketing email, and an easy way to unsubscribe from non-essential messages. Without these, emails land in spam and the sequence does nothing, however good the copy is.
Set up SPF, DKIM and DMARC for your sending domain; our guide to email deliverability for website forms explains each one. Major mailbox providers have tightened requirements for bulk senders, including authentication and one-click unsubscribe, so check the current rules for your volume. Keep password resets and invites on a transactional stream, separate from onboarding nudges, so a spam complaint about marketing doesn't block logins. And make sure the product moments the emails point to are fast; see our guide to time to value in SaaS.
