Onboarding Email Templates You Can Copy, and the Tools to Send Them
For most small and mid-sized SaaS teams, Make is the best starting point for onboarding emails that fire on real product events, because it connects your app's events to the email service you already use and its free plan lets you build a first flow at no cost. The Core plan is $9 a month billed annually for 10,000 credits. You still need an email service to deliver the messages.
Who This Guide Is For
This page is for product, growth and lifecycle teams that already have signups and want the first days of use to be deliberate. It covers five ready-to-adapt onboarding emails, a sequence structure you can apply to any SaaS product, and the tools that decide when each email is sent. It does not cover general email marketing, newsletters or re-engagement campaigns for long-dormant users.
The templates below use square-bracket placeholders such as [First name] and [Feature name]. Replace them with your own product language before you send anything. Each template assumes one clear trigger: a signup, a missed setup step, a completed milestone, or a trial that is about to end. Sending a welcome email on a fixed timer is simpler to set up, but event-based triggers are usually more relevant, and the tables in this guide are built around that trade-off.
The Tools in This Guide at a Glance
Onboarding emails need three things: a trigger from your product, logic that decides who gets which message, and a sending service. The three tools below cover different parts of that chain. None of them replaces a sending service. Make and Heap help you define and route the events that start an onboarding email, and Convert helps you test the onboarding pages and in-app flows that the emails point to.
| Tool | Best for | Entry price (plan, billing) | Key limitation |
|---|---|---|---|
| Make | Routing product events and API calls into an email flow | Free plan: 1,000 credits per month. Core: $9 a month billed annually for 10k credits ($10.59 billed monthly) | Free plan allows only 2 active scenarios and runs at most every 15 minutes |
| Heap | Capturing and defining the activation events that should trigger emails | Free plan up to 10k monthly sessions. Paid plans: pricing on request | Free plan keeps 6 months of data history; Session Replay is an add-on |
| Convert | A/B testing onboarding pages and in-app flows | No free plan. Growth: $299 a month billed annually ($399 billed monthly), 100,000 monthly tested users | Tests web pages and flows, not email sends; no free plan, only a 15-day trial |
Prices in this guide were taken from each vendor's public pricing page on 7 October 2026. Plans and limits change, so confirm the figures on the linked pricing pages before you buy.
Make: Connecting Product Events to Your Email Flow
Make is a visual automation builder. For onboarding, the typical scenario starts with a webhook or an app connector that fires when a user signs up, completes setup or invites a teammate. The next modules check conditions, wait, and then call your email service to send the right template. Each module action uses one credit, so a flow with four actions per user costs four credits per user.
What it does well for onboarding: it lets a non-engineer rebuild a onboarding path without deploying code. Routers and filters handle branches such as "setup complete" versus "setup stalled after 24 hours". The free plan includes more than 3000 apps, so you can usually connect your product database, CRM and email service without writing an integration. Scenario templates on paid plans let you share a working flow with a colleague.
Where it falls short: on the Free plan, scenarios run at most every 15 minutes, each run can last 5 minutes at most, and the execution log is kept for 7 days. For onboarding, the 15-minute interval is fine for most flows, but a message that should go out within seconds of a payment failure or a trial ending needs a faster path. Make is also not a place to store your subscriber list or to design email layouts. Those belong in your sending service.
Price: the Free plan includes 1,000 credits per month with no time limit. Core is $9 a month billed annually for 10k credits, or $10.59 billed monthly. Pro is $16 a month billed annually for the same 10k credits and adds priority execution, custom variables and full-text log search. Teams is $29 a month billed annually and adds team roles and shareable scenario templates. Larger credit allowances are priced on the slider on Make's pricing page, and the figures above do not cover them. Enterprise is priced on request. See the Make pricing page for current figures.
Heap: Defining the Activation Events
Before an onboarding email can be triggered by behavior, someone has to define what behavior counts. Heap captures user interactions automatically, which lets a product team pick activation events such as "created first project", "connected an integration" or "invited a teammate" without adding every event by hand. Those definitions can then feed an automation tool such as Make, or be checked against the sequence after it has run.
What it does well for onboarding: it shows which steps new users actually complete and where they stop. That is the input you need to decide which emails matter most. The Free plan includes core analytics charts, unlimited enrichment sources, guides integrations, and SSO. Growth adds unlimited users and reports, CSV exports and 12 months of data history. Pro adds account analytics, an engagement matrix and report alerts. Premier adds a data warehouse integration, behavioral targeting and region-specific storage.
Where it falls short: Heap is an analytics tool, so it will not write your emails or send them. The Free plan keeps 6 months of data, which is enough for a first onboarding review but short for seasonal cohort analysis. Session Replay is sold as an add-on on the Pro plan, so budget for it separately if you want to watch how users struggle with a setup step. Paid tier prices are not published on the pricing page, so you will need to request a quote.
Price: the Free plan covers up to 10k monthly sessions. Growth, Pro and Premier are priced on request. Check the Heap pricing page for the current plan list.
Convert: Testing the Pages Behind Your Emails
Convert is an experimentation platform for websites and in-app flows. It does not send email. Its use in onboarding is narrower: if your onboarding emails link to a setup page, a pricing page or an in-app checklist, Convert can split traffic between two versions of that destination and tell you which one gets more users to the activation action.
What it does well for onboarding: it fits teams that already have a solid email sequence and want to improve the landing experience behind it. Growth includes 100,000 monthly tested users. Pro adds more segments and advanced features. Pricing is flat by plan and by monthly tested users, with a discount for annual billing.
Where it falls short: Convert has no free plan. You can run a 15-day free trial on Growth and Pro, and that is the only way to try it before paying. It counts tested users, not email recipients, so a large mailing list does not automatically push you into a higher tier. Teams with a small product and modest traffic will get more value from fixing the email trigger first.
Price: Growth is $299 a month billed annually, or $399 a month billed monthly. Pro is $420 a month billed annually, or $599 a month billed monthly. Both are priced for 100,000 monthly tested users on the default slider. See the Convert pricing page for current figures.
What Onboarding Costs at Realistic Volumes
Costs depend on how many people start onboarding each month and how many automation steps each person triggers. The table below uses one assumption you should replace with your own count: each new user triggers four Make actions (one trigger, one condition, one wait-and-check, one send). At four credits per user, the Make credit allowance works out as shown. Heap and Convert are priced on sessions and tested users, which track site traffic rather than signups, so they are shown as plan ranges.
| New users per month | Make credits needed (4 per user) | Make plan that fits | Heap | Convert |
|---|---|---|---|---|
| 250 | 1,000 | Free: 1,000 credits per month, no charge | Free plan, if monthly sessions stay under 10k | No free plan. Trial only, 15 days |
| 2,500 | 10,000 | Core: $9 a month billed annually ($108 a year), or $10.59 billed monthly | Free plan, if monthly sessions stay under 10k; otherwise pricing on request | Growth: $299 a month billed annually ($3,588 a year), or $399 billed monthly |
| 10,000 | 40,000 | Above the 10k-credit tiers. Use the credit slider on Make's pricing page | Pricing on request | Growth or Pro, depending on segments needed. Pro: $420 a month billed annually ($5,040 a year) |
The arithmetic in this table is simple. At 2,500 users a month and 4 credits each, you need 10,000 credits, which is exactly the Core allowance. If each flow uses six actions instead of four, the same 2,500 users need 15,000 credits and you should move to the next allowance on the slider. Count your own actions before you choose a plan. Adding an extra wait step or a second condition changes the bill more than you might expect.
Convert is only worth its cost once you are running experiments on onboarding pages with enough traffic to reach a clear result. For a product with a few hundred visitors a day, the free trial is the right way to decide.
Which Tool Fits Your Situation
Most onboarding setups come down to one question: is the problem that you cannot trigger emails from product events, that you do not know which events matter, or that the onboarding pages convert poorly? Each answer points to a different tool. The table below is meant to narrow the choice before you open a pricing page.
| If you need | Pick | Because | Watch out for |
|---|---|---|---|
| Emails triggered by real product events | Make, with your existing email service | Routes events and conditions without custom code; Free plan lets you prototype | Free plan allows only 2 active scenarios and 15-minute run intervals |
| Deciding which activation events to email about | Heap | Shows which setup steps users complete and where they stop | Session Replay is an add-on; paid prices require a quote |
| Better landing pages behind the onboarding emails | Convert | Splits traffic between page versions and reports which converts more users | No free plan; does not send or manage email |
| Only a simple fixed-day sequence | Your email service's built-in sequence builder | No extra tool to run; enough for a basic 5-email path | Cannot react to behavior; timers can mistime users who already finished setup |
Copyable Onboarding Email Templates
The five templates below cover the stages most SaaS onboarding flows need. Each one lists its trigger, the subject line, and the body. Use them as a starting draft: change the wording to match your product, and remove any line that promises something your product does not do. Keep the single call to action in each email and link it to the exact screen the user needs next.
Template 1: Welcome and first step (trigger: signup confirmed)
Subject: Your [Product name] account is ready, start here Hi [First name], Your account is set up. The fastest way to get value from [Product name] is to complete one step: [single core action, for example "connect your first data source"]. It takes about [time estimate] and you will see your first [result] as soon as it is done. [Button: Complete this step] linking to [specific setup URL] If you get stuck, reply to this email and a person from our team will answer. [Sender name], [Product name]
Template 2: Setup nudge (trigger: signup 24 hours ago, core step not completed)
Subject: One step left before [Feature name] works Hi [First name], You started setting up [Product name] yesterday but the [core step] is not finished yet. Until it is, [Feature name] cannot [specific outcome]. Here is what is left: 1. [Step one] 2. [Step two] [Button: Finish setup] linking to [resume URL] Need a hand? Book a 15-minute setup call here: [booking URL].
Template 3: Feature education (trigger: core step completed, feature not yet used)
Subject: How [customer type] uses [Feature name] to [outcome] Hi [First name], You finished [completed step], so your account is ready for [Feature name]. Teams like yours usually use it to [specific use case]. Try it on one real item: [specific example from your product]. [Button: Try [Feature name] now] linking to [feature deep link] Short video (2 minutes): [video URL]
Template 4: Progress recap (trigger: milestone event, for example the third completed step)
Subject: You have completed [number] of [total] setup steps Hi [First name], Here is where your [Product name] setup stands: - Done: [step], [step], [step] - Next: [next step] Once [next step] is done, you can [specific outcome the user gets]. [Button: Continue setup] linking to [next step URL]
Template 5: Trial ending (trigger: 3 days before trial end)
Subject: Your trial ends on [date] Hi [First name], Your [Product name] trial ends on [date]. In that time you have [specific accomplishment, for example "set up two workflows and sent 340 messages"]. To keep your data and your workflows running, choose a plan before the trial ends: [plans URL]. If [plan name] does not fit your team, reply and tell us what is missing. We will answer within [response time].
Notice what the templates have in common. Each email has one trigger, one action, and one link. None of them relies on a statistic, a testimonial or a claim the product has not earned. If you add an industry-specific detail, make sure it is accurate for your product: for example, a healthcare scheduling tool needs to be careful about any message that refers to patient information.
Onboarding Sequence Structure That Works Across Products
A sequence of five to eight emails over the first two weeks is common, but the length matters less than the logic behind it. The best sequences are built around milestones rather than calendar days. Start by defining one activation event: the single action that users who stay tend to complete. Then build backward. Which steps must happen before that action? Which messages help a user take each step? Each email should answer one question the user is likely to have at that point.
Use time only as a floor. If a user has not completed setup 24 hours after signup, a nudge is appropriate. If the user has already completed setup, a setup nudge is noise and can make the product feel slow or naggy. Event triggers prevent this. The Make scenario in the earlier section can check whether the activation event has already happened before it sends anything.
Keep the total number of messages low enough that users notice each one. A sequence that sends seven emails in six days will be muted or unsubscribed from by many recipients. For most products, three event-based emails plus two time-based check-ins is enough to cover the early stages without crowding the inbox.
Setup and Migration Checklist
If you are moving from a fixed-day sequence to event triggers, or building onboarding emails for the first time, work through the checklist below in order. Each step has a clear finish line, so you can tell when it is done before moving to the next one.
| Step | What to do | Done when |
|---|---|---|
| 1. Define activation | Pick one user action that predicts continued use, and write it down in plain words | The whole team can name the same action |
| 2. Capture the events | Use Heap or your own event logging to record setup steps, invites and milestones with consistent names | Each step appears in your analytics with a single event name |
| 3. Map the triggers | List each email with its trigger, condition and exit condition (for example, "setup complete") | Every email has one trigger and one exit rule |
| 4. Build the flow | Create the scenario in Make, or the equivalent workflow in your email service, and connect it to your sender | A test signup receives the first email within the expected window |
| 5. Check the limits | Count actions per user against your Make credit allowance and confirm the run interval fits your triggers | Monthly credit use is below the plan allowance with room to spare |
| 6. Review the links | Make sure each button points to the exact screen the user needs, and that the page loads for a logged-in user | Every link has been clicked through in a test account |
| 7. Switch on and review | Turn on the flow, then review opens, clicks and activations at the same interval each month | A monthly review is on the calendar with a named owner |
Measuring Whether Onboarding Emails Work
Measure the metric that matters most first: the share of new users who complete the activation event. Opens and clicks are useful for checking that emails are delivered and read, but they do not show whether the product became more useful. Compare two groups of users over the same period: those who received the sequence and those who did not, or those who received the old fixed-day sequence and those who received the new trigger-based one.
Track time to activation as well. If activation happens sooner after signup, the emails are doing their job even if the overall completion rate stays the same. Look at drop-off points too. If most users stop at the same setup step, the next email should address that step, not repeat the welcome message.
Frequently Asked Questions
Which tool should I start with for onboarding emails?
Start with the email service you already use, and add Make if you need to trigger emails from product events. The Make Free plan includes 1,000 credits per month, so you can build and test a first flow at no cost. Heap is useful when you are still deciding which activation events to use. Convert only makes sense once you are testing onboarding pages and have enough traffic to reach a clear result.
How many onboarding emails should I send?
Most SaaS products do well with three to five emails in the first two weeks. Send each one only when its trigger fires, and stop the sequence when the activation event happens. More messages rarely help once the user has done the key action, and they make the product feel noisy.
How do I count Make credits for an onboarding flow?
Each module action in a scenario uses one credit. A flow that triggers on signup, checks a condition, waits, and sends an email uses roughly four credits per user. Multiply that by your monthly new users to estimate credit use, then compare it with the allowance for your plan. Check the figure again after adding each new branch.
Can I use Heap's free plan for onboarding analytics?
The Free plan covers up to 10k monthly sessions and keeps 6 months of data. That is enough to see which setup steps users complete and where they stop. It does not include CSV exports or 12 months of history, which you will need for a year-over-year review of onboarding changes.
Should onboarding emails include product screenshots?
A screenshot helps when a user needs to find a specific button. Screenshots age quickly, though, and every interface change means updating the email. Use one screenshot per email at most, tied to a single step, and describe the location in words too, such as "in the top-right menu, choose Settings".
What should happen when a user does not respond to any onboarding email?
After the sequence ends, stop sending onboarding messages and move the user to your ordinary lifecycle or newsletter flow, if they have opted in. Continuing to send setup nudges to someone who has not engaged in two weeks rarely helps and can hurt deliverability. Review the users who went quiet to see whether a specific step is blocking them.
Do I need a separate trial-ending email if I already have a trial sequence?
Yes. The trial-ending message should be triggered by the trial date, not by the signup date, and it should list what the user has accomplished in the trial. Keep it factual. Name the plan, the date and the outcome, and link to the plan page so the next step is clear.