# SaaS Onboarding Email Templates

> Nine onboarding email templates with subject lines, body copy, merge fields and trigger rules, plus separate variants for self serve and sales assisted signups.

Source: https://saas-marketing.net/templates/saas-onboarding-email-templates/
Topic: SaaS Email Marketing
Type: template
Published: 2026-09-11
Last updated: 2026-09-11
Publisher: SaaS Marketing (saas-marketing.net)
License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/templates/saas-onboarding-email-templates/

## Short answer

A working SaaS onboarding sequence is nine emails over roughly fourteen days: welcome, setup nudge, first value, invite a teammate, integration prompt, use case education, usage recap, social proof, and a human reply ask. Each needs a behavioural trigger, an exit condition so completed users stop receiving it, and the product data merged in. Send them as plain text from a named person, because branded HTML depresses replies and hurts inbox placement on onboarding sends.

## Key takeaways

- Every onboarding email needs an exit condition. Nudging someone to do what they already did is the fastest unsubscribe.
- Send onboarding as plain text from a real person's address. Branded HTML templates measurably reduce replies.
- Self serve and sales assisted signups need different sequences, because one has a human and the other does not.
- The teammate invite email is the most influential one in the set for any multi-user product.
- Merge fields that reference the user's actual account data outperform generic copy by a wide margin.
- Nine emails in fourteen days is a ceiling, not a target. Cut to six if your product activates in one session.

---

Below are nine complete templates you can paste into your ESP today, each with its trigger, delay, merge fields and exit condition. They're written for a fictional but realistic product, Northbeam Analytics, a B2B product analytics tool where first value means connecting a data source and building one chart.

Change the specifics, keep the structure. And keep them plain text.

## The nine templates

Each one is short on purpose. The merge fields in curly braces map to product data your ESP needs access to, which is listed in full further down.

**1. Welcome. Trigger: signup. Delay: immediate. Exit: none.**

> Subject: your Northbeam account
>
> Hi `{first_name}`,
>
> You're in. The fastest route to something useful is connecting a data source, which takes about four minutes: `{setup_link}`
>
> If you get stuck, reply to this email. It comes to me directly.
>
> Priya
> Northbeam

**2. Setup nudge. Trigger: 24 hours after signup, only if no data source connected. Exit: data source connected.**

> Subject: stuck on the data source step?
>
> Hi `{first_name}`,
>
> Your account is set up but there's no data flowing in yet. Most people who stall here are on `{most_common_source}`, and this walkthrough covers it: `{docs_link}`
>
> What are you trying to connect? Happy to point you at the right doc.

**3. First value. Trigger: first data source connected. Delay: 15 minutes. Exit: none.**

> Subject: data's in, here's the first chart to build
>
> Nice work, `{source_name}` is connected and we're seeing `{event_count}` events.
>
> The chart most teams build first is weekly active accounts by plan. Takes about two minutes: `{chart_link}`

**4. Invite a teammate. Trigger: day 3, only if seat count equals 1. Exit: second seat added.**

> Subject: who else needs to see this?
>
> Hi `{first_name}`,
>
> Accounts with two or more people set up in the first week are the ones still active at day 90. Usually it's whoever asks you for numbers on Mondays.
>
> Add them here: `{invite_link}`

**5. Integration prompt. Trigger: user visits the integrations page without connecting. Delay: 2 hours. Exit: any integration connected.**

> Subject: connecting `{integration_name}`
>
> Saw you were looking at the `{integration_name}` integration. It's a three-step OAuth connection and it backfills 90 days automatically.
>
> Setup: `{integration_docs}`
>
> One thing worth knowing: the backfill takes about 20 minutes, so the charts look empty for a bit.

**6. Use case education. Trigger: day 5. Delay: none. Exit: none.**

> Subject: three things teams do with Northbeam in week one
>
> Hi `{first_name}`,
>
> Not a feature list, just what people actually build first:
>
> Churn signal report. Accounts whose weekly usage dropped 40 percent or more.
> Activation funnel. Signup through to first successful action.
> Feature adoption by plan tier. Usually the one that changes the roadmap.
>
> Each takes under ten minutes: `{templates_link}`

**7. Usage recap. Trigger: day 7. Exit: none.**

> Subject: your first week
>
> `{first_name}`, here's where you got to:
>
> `{chart_count}` charts built
> `{seat_count}` people on the account
> `{event_count}` events tracked
>
> The teams who stick with us usually have a report someone checks every Monday by the end of week two. Do you have one yet?

**8. Social proof. Trigger: day 10. Exit: trial converted.**

> Subject: how `{similar_company_segment}` teams use this
>
> Hi `{first_name}`,
>
> A 60-person fintech on the same plan cut their weekly reporting time from six hours to about twenty minutes, mostly by replacing a spreadsheet nobody trusted.
>
> Short write-up here if it's useful: `{case_study_link}`

**9. Human reply ask. Trigger: day 13, trial ending. Exit: trial converted.**

> Subject: quick question before your trial ends
>
> `{first_name}`, your trial ends `{trial_end_date}`.
>
> I'm not going to pitch you. I want to know what didn't work, because that's more useful to me than a conversion.
>
> What got in the way?
>
> Priya

It asks a genuine question and expects nothing. Teams that run this email typically get more useful product feedback from it than from a quarterly survey, and a meaningful share of replies turn into saved trials because you find out the actual blocker.

## Self serve versus sales assisted variants

The nine above are the self serve set. If a rep is working the account, running all nine in parallel makes you look like two companies that haven't met.

The usage recap row is the useful trick. Same data, different recipient. A rep who opens a call with "you built four charts but nobody's connected Salesforce yet" is running a better call than one who asks how the trial is going.

## Merge fields your product needs to expose

The templates are only as good as the data behind them. If your ESP can't access these, the emails degrade to generic copy and lose most of their effect.

| Merge field | Source | Used in | Fallback if missing |
|---|---|---|---|
| first_name | Signup form | 1, 2, 4, 6, 7, 8, 9 | Drop the greeting entirely, never use "Hi there" |
| setup_complete | Product event | 2 (as trigger) | Time-based send, worse but workable |
| source_name | Product | 3 | "your data source" |
| event_count | Product | 3, 7 | Omit the line |
| seat_count | Billing or product | 4 (as trigger), 7 | Do not send email 4 |
| integration_name | Page view event | 5 | Do not send email 5 |
| chart_count | Product | 7 | Omit the line |
| trial_end_date | Billing | 9 | Do not send email 9 |

Note the fallback column. The rule is that a missing merge field means suppress the email, not send it with a placeholder. "Hi there, you've built 0 charts" is worse than silence.

Getting this data into the ESP is usually the real project. Most teams pipe product events through Segment or a direct API integration into Customer.io or Intercom, and the setup takes longer than writing all nine emails. Budget for it. [Lesson 3 of the lifecycle email course](/courses/saas-lifecycle-email/03-ship-your-first-sequence/) walks through shipping the first one end to end.

## Editing rules

Six rules that keep the set from degrading as different people edit it over two years.

**Before any onboarding email ships**

The monitored address rule gets broken constantly. Sending from priya@ and routing replies to a black hole is worse than sending from a no-reply address, because you've invited a conversation and ignored it. If nobody will read the replies, don't write email nine.

On the plain text point specifically: heavy HTML with tracking-laden image headers correlates with promotions-tab placement and depresses reply rates. For onboarding, where the goal is behaviour and conversation rather than clicks on a hero button, that trade is clearly the wrong way round. The benchmarks in [SaaS email benchmarks](/research/saas-email-benchmarks/) are worth reading before you argue about this with a designer.

Sequences without exit conditions. A user who invited four teammates on day one receives the day-three invite email anyway, and now your product looks like it isn't paying attention. Test every branch with a real account that completes the action early.

## Where to go next

Paste the nine into your ESP as drafts today, then spend the real effort on the event data behind the triggers. That's the part that determines whether these are good emails or generic ones.

Once shipped, pull them apart against real examples in [SaaS onboarding email teardowns](/guides/saas-onboarding-email-teardowns/), and if activation rather than trial conversion is your problem, the structure in [activation email sequences](/guides/activation-email-sequences/) targets it more directly. The full sequence design logic sits in [the SaaS onboarding email sequence](/playbooks/saas-onboarding-email-sequence/), the trial end of the lifecycle in [the trial expiry email sequence](/playbooks/trial-expiry-email-sequence/), and if you want to size the upside first, the [SaaS email revenue calculator](/calculators/email-revenue/) will do it. Definitions worth agreeing on internally, like [drip campaign](/glossary/drip-campaign/), are in the glossary, and the wider programme is at [SaaS email marketing](/saas-email-marketing/).

## Frequently asked questions

### How many onboarding emails should a SaaS product send?

Between six and nine over the first two weeks, depending on how many steps activation requires. A single-session product like a URL shortener needs three. A product requiring data import, integration and team invites needs nine. Count the actions required to reach first value and send roughly one email per action, plus a welcome and a recap.

### Should onboarding emails be plain text or HTML?

Plain text from a named sender for onboarding. It lands in the primary tab more reliably, it invites replies, and it reads as a person rather than a campaign. Save designed HTML for newsletters and product announcements where the visual matters and a reply is not the goal.

### What triggers should onboarding emails use?

Behavioural triggers tied to product events, with time-based fallbacks. The setup nudge fires 24 hours after signup only if setup is incomplete. The integration prompt fires when a user reaches the relevant screen without connecting. Pure time-based sequences send irrelevant emails to active users, which is the main cause of onboarding unsubscribes.

### What is an exit condition in an onboarding sequence?

A rule that removes a user from a branch once they complete the action it was nudging. If someone invites three teammates on day two, they should never receive the day-five invite email. Missing exit conditions are the single most common defect in SaaS onboarding sequences and they read as the product not knowing who you are.

### Should sales assisted trials get the same onboarding emails?

No. If a rep is already emailing them, automated nudges compete with the human and make the company look disorganised. Sales assisted trials should get a reduced set of three or four emails covering product education only, with all nudging and scheduling left to the rep.

### How long should an onboarding email be?

Between 50 and 120 words for nudges, up to 200 for the education emails. One link, one action. Emails with three competing calls to action get fewer clicks in total than emails with one, because the reader has to make a decision before acting.