Best React Email Templates for SaaS Onboarding (Welcome, Verification, Trial)

If you're shipping a SaaS product, your onboarding emails are part of the product. If users miss the welcome email, don't verify their email, or forget about their trial, they churn before they ever see real value.

If you're building a SaaS in React/Next.js and using React Email (with providers like Resend, Postmark, SendGrid, etc.), you don't need to hand-code every HTML email from scratch. You can use a small set of reusable React email templates and wire them into your flows.

This guide walks through the core onboarding emails most SaaS products need:

1. Welcome email
2. Email verification
3. Trial started
4. Trial reminder / trial ending soon
5. Trial extended / trial converted

For each one:

• When to send it
• What to include
• Example subject lines
• A React Email JSX template you can adapt

Tech stack assumptions

The examples below assume:

• You're using React Email for authoring templates
• You're sending through a provider like Resend, Postmark, SendGrid, Mailgun, or Nodemailer
• You're in a typical Next.js / Node.js environment

The JSX templates are provider-agnostic. You render with React Email and pass the HTML to your email provider.

1. Welcome email template

When to send

Immediately after signup.

Goal: confirm the account, set expectations, and point them back into the app to complete one meaningful step (for example: “finish onboarding”).

What to include

• Short confirmation that the account is ready
• Quick reminder of what the product is for
• One primary CTA back to the app
• Optional: docs, support, quick start guide

Subject line ideas

• Welcome to {{productName}}
• Your {{productName}} account is ready
• Getting started with {{productName}}

Example template

PreviewCode

Copy

2. Email verification template

When to send

Right after signup, if you require email verification before enabling core features.

Goal: get them to click the verification link and land back in the app with a verified account.

What to include

• Clear explanation of why verification is needed
• A prominent button with the verification link
• A plain URL for edge cases
• Note about link expiry (if applicable)

Subject line ideas

• Verify your email for {{productName}}
• Confirm your email address
• Complete your {{productName}} signup

Example template

PreviewCode

Copy

3. Trial started template

When to send

As soon as a user starts a free trial (or moves from free to trial).

Goal: confirm the trial, set expectations about timing, and point them at the key actions that correlate with activation.

What to include

• Trial duration and end date
• What they can do during the trial
• One or two clear actions (for example: “connect a data source”, “invite a teammate”)
• Link to the billing/plan page so upgrading is obvious

Subject line ideas

• Your {{productName}} trial is now active
• You have {{X}} days to try {{productName}}
• Trial activated for {{productName}}

Example template

PreviewCode

Copy

4. Trial reminder / trial ending soon template

When to send

Usually 1–3 days before the trial ends. Many products also send a final reminder on the last day.

Goal: remind them that the trial is ending, explain what happens next, and prompt them to upgrade or finish setup.

What to include

• How much time is left
• What happens if they don't upgrade (downgrade, limited access, etc.)
• Optional: features they've used vs haven't (if you track it)
• One primary CTA: “Upgrade now” or “Finish setup”

Subject line ideas

• Your {{productName}} trial ends in {{X}} days
• Your {{productName}} trial is ending soon
• Keep access to your {{productName}} workspace

Example template

PreviewCode

Copy

Putting it all together

A simple onboarding email flow might look like this:

1. Signup

   • Send: welcome email
   • Send: email verification (if required)

2. Trial started

   • Send: trial started / activated email

3. Before trial end

   • Send: trial reminder / trial ending soon

4. If extended

   • Send: trial extended email (same structure as “trial started” with new dates)

5. When upgraded

   • Send: “You're now on a paid plan” confirmation (same idea as trial started, focused on what's now included)

You want a consistent system, not a pile of one-off emails:

• Shared layout and components (header, footer, logo, brand colors)
• Clear, focused copy in each email
• One main action per email that moves the user forward

If you don't want to design and code all of this yourself, you can use our React Email Templates bundle for SaaS — 12 production-ready templates (welcome, verification, trial, billing, security alerts) already built and tested across Gmail, Outlook, Apple Mail, and mobile. Plug in your URLs and brand styles, then wire them into your sending logic.

Best practices for SaaS onboarding emails

Templates help, but how you use them matters more.

1. Timing

• Welcome emails: within seconds of signup
• Verification emails: immediately, before or alongside the welcome email
• Trial started: when the trial is activated
• Trial reminders: common pattern is 3 days before, 1 day before, and (optionally) on the last day

2. Mobile-first design

Most emails are opened on phones. React Email components render well, but still test on actual devices and clients you care about.

3. Personalization beyond the name

If you track behavior, use it:

• Which features they've used
• Onboarding steps they've completed
• Integrations they've connected
• Whether they've invited teammates

You don't need to overdo it; one or two relevant details are enough.

4. One clear primary CTA

Each email should drive one main action. Secondary links are fine, but they shouldn't compete with the main button.

5. A/B test subject lines

Test small changes:

• Urgency vs benefit
• With vs without emoji
• More personal vs more neutral
• Question vs statement

Keep what actually gets opened and clicked, not what sounds clever.

For setup details, see:

• Setting up React Email in a monorepo
• React Email template examples

Frequently Asked Questions

How do I send React Email templates with Resend?

Render the React Email component to HTML, then pass that HTML string into Resend's send call as the html property. The same template can be reused across different events by passing different props.

What's the best email service for SaaS onboarding?

Resend, Postmark, and SendGrid are the most common choices for SaaS. Pick based on deliverability, pricing, and how good their developer tooling is for your stack.

Should I send welcome and verification emails separately?

Yes. The verification email is transactional and time-sensitive. The welcome email is for context, education, and next steps. Keep each focused on its job.

How many onboarding emails should I send during a trial?

A common pattern is: one trial start email, 2–3 short activation/education emails, and 1–2 reminder emails before the trial ends. If you're early-stage, start simple and only add more if you see clear drop-offs.

Can I use React Email with existing email templates?

Yes. You can migrate gradually by converting your most important flows first (verification, password reset, onboarding) and leaving less critical templates for later.

Conclusion

Onboarding emails are not a nice-to-have. They're part of your activation funnel.

With React Email and the templates in this guide, you can:

• Ship a clean onboarding sequence quickly
• Keep copy and layout consistent across all system emails
• Iterate and A/B test without fighting raw HTML tables
• Make sure emails render correctly across common clients

Start with the basics (welcome, verification, trial started, trial reminder), measure what users actually do, then refine.

If you want to skip design work and jump straight to implementation, the React Email Templates bundle includes 12 production-ready templates for the full user journey — from onboarding to billing to security alerts. All are TypeScript-typed and tested across Gmail, Outlook, Apple Mail, and mobile clients.