Onboarding Emails for SaaS: Templates and Examples
How to structure SaaS onboarding emails, six templates to send this week, and why a blocker-triggered email beats any welcome sequence.
Photo by Greta Hoffman on Pexels
Onboarding emails are the most-sent messages in SaaS and among the least useful when they focus on telling the user about the product. The user has not asked to hear about features; they are deciding whether the product can solve their current problem. This guide covers both a set of templates you can send this week and the principle underneath them: an onboarding email works when it lowers the effort of the next step.
What makes an onboarding email work
Four properties, in order of importance:
- It arrives when the user’s current task is at a decision point. Not “Day 2”, but “after signup but before first project” — right when progress stops progressing.
- It names something specific. “Your first report is empty” beats “Get more out of Acme”. Vagueness is why identical emails get identical no-reply treatment.
- It asks one thing. Two CTAs is the same as none. If one action can be done in email, do it in the email (e.g. “reply ‘yes’ and we’ll set it up”).
- It is reply-able. Every onboarding message should be written as if it would be read and answered, because the best ones are.
A bare-bones structure for self-serve SaaS
| Timing | Message | What to say | Action |
|---|---|---|---|
| Immediately after signup | Welcome | What the product does to their problem, in their situation, in two sentences. | One action: do the first useful thing. |
| Day 1 (if no activation) | Setup help | The step users most often get stuck on. | Reply and we’ll set it up for you. |
| Day 3 (if stuck) | Blocker email | Acknowledge the blocker explicitly, suggest a path around it. | One action: do the next useful thing. |
| Day 6 (if quiet) | Value reminder | Show what a “good” account looks like as a sample. | Open the sample in one click. |
| Any time (event-triggered) | Help | A reply to a concrete stuck event. | Personalized help. |
That last row is where the compounding happens. A time-based sequence is a guess; an event-based email is an answer.
Six templates to copy
1. The welcome with one task. Subject: “Welcome — one task before you leave the tab.” Body: one sentence on the value, one bullet with the first action, one line: “Reply if anything is confusing — I read every answer.”
2. The setup unblocker. (triggered: activation event not completed after 24h) Subject: “Stuck at the {step} step?” Body: name the step, give the two most common mistakes, offer to do it for them. One reply counts as “we’re here to help” activation.
3. The sample result. (triggered: account has no data after 2 days) Subject: “Here’s what your dashboard looks like with real data.” Body: a screenshot with real (anonymized) data, one line of how to get there. The cheapest way to make a rough product feel finished is a good example.
4. The extension offer. (triggered: trial almost over and no value yet) Subject: “Want another week to finish {task}?” Body: offer the extension with 1 click, keep the rest of the message to 4 lines total. Extensions without context are only goodwill; extensions paired with a blocker message note something to remember.
5. The first-value nudge. (triggered: user reached value but stopped 7+ days) Subject: “Your {report} is already set up — here’s how to use it weekly.” Body: frame the power of the existing value they built, one action to repeat it. This email converts a past “done it once” user to a repeating user.
6. The human handoff. (any reply, unresolved after 1 message) Body: acknowledge the reply personally, ask one clarifying question, state what you’ll do next and when. Never re-send a template after a reply.
Measurement to set up first
- Reply rate per email — your most honest indicator.
- Activation rate of email recipients vs non-recipients, but hold it to a real comparison (experiment design here covers it).
- Time-to-value for recipients — not just counts.
- Unsubscribe per email, for the long-term cost.
One note on deliverability: onboarding from your own domain with proper SPF/DKIM/DMARC, and keep A/B test lists small. A domain’s reputation is worth more than a campaign’s open rate.
Where we come in
Writing and sending these emails by hand is fine at 50 trials a month and they stop working at 300. magicsales does the event-triggered part: it watches your events, notices stuck users in your trial cohort, writes a personal reply from your domain in your voice, and proposes one useful action — like setting a step up or extending the trial — for you to approve. If sending Gen-em-formula onboarding at proper volume, apply for a pilot.
Related reading
Frequently asked questions
How many emails should an onboarding sequence have?
Three to five beats ten. Dates (Day 0, Day 1, Day 3, Day 7) carry the early trial period; after that, email should be triggered by behavior, not time.
Should onboarding emails come from the CEO or the product?
From a real person with a real reply address. Replies to onboarding email are the single most valuable signal in early trial conversion — a no-reply inbox throws that signal away.
What makes a good onboarding email for B2B SaaS?
One action sized to the next useful step, a concrete benefit in the first line, and personalization that reflects what the user has already done — not mail-merge tokens.
Do onboarding emails work for trials without a credit card?
Yes, and they matter more: without card commitment, the trial ends when motivation runs out, so speed and relevance carry more weight.
