Email sequence template · 5 steps · 7 min read
Onboarding Email Sequence Template: 5 Emails + Timing
An onboarding email sequence is a short, triggered series that starts at signup and has one job: get a new user to the first action that represents value in your product. This template has five emails across 10 days. Every step has its own audience rule, and anyone who completes the activation event leaves the main path the moment it happens, so nobody is asked to do something they have already done.
Replace the placeholders in double braces before you send anything. {{product_name}} is your product, {{activation_event}} is the one action you treat as first value (for example creating a first project or inviting a teammate), {{first_step}} is the smallest action that leads to it, and {{sender_name}} is a real person on your team who can read replies. Decide the activation event before you write a single subject line; the sequence is only as good as that definition.
Sequence at a glance
- Entry ruleAccount created. Exclude internal and test accounts, and users who joined through a teammate invitation if they already receive a separate invite flow.
- Exit and suppressionRemove the user from emails 2, 3 and 5 as soon as {{activation_event}} is recorded. Remove anyone who unsubscribes, marks a message as spam or opens a support ticket about setup (hand them to the support conversation instead).
| Step | Send | Audience |
|---|---|---|
| 1. Welcome and the one first step | Immediately after signup (within a few minutes) | Everyone who matches the trigger. No engagement conditions on the first email. |
| 2. Nudge toward the first action | Day 1 (24 hours after signup) | Signed up 24 or more hours ago AND has not completed {{activation_event}} AND has not unsubscribed. |
| 3. Remove the most common blocker | Day 3 (72 hours after signup) | Signed up 72 or more hours ago AND has not completed {{activation_event}}. If you track a partial step such as {{setup_started}}, send the variant subject to people who started but did not finish. |
| 4. Next step for users who activated | 1 day after {{activation_event}} is recorded (only within the first 14 days after signup) | Completed {{activation_event}} within 14 days of signup AND has not completed {{second_value_action}}. This is the only email activated users receive from this sequence. |
| 5. Personal check-in | Day 10 after signup | Signed up 10 or more days ago AND has not completed {{activation_event}} AND has not replied to any earlier email in this sequence. |
Copy, timing and audience for every step
Replace each placeholder in double braces with your own value. Send a test of every step to an internal address before you switch the sequence on.
Step 1: Welcome and the one first step
Subject: Welcome to {{product_name}}. Here is your first step
Preview text: One thing to do today, and why it matters.
Hi {{first_name}},
Thanks for signing up for {{product_name}}. You are here to {{job_to_be_done}}, so let's get you there without a long tour.
The fastest way to see whether {{product_name}} fits is to {{first_step}}. It is the step that most directly leads to {{activation_event}}, and you can do it with the information you already have.
If you get stuck, reply to this email. It comes to me, not to a no-reply inbox.
{{sender_name}}, {{sender_role}} at {{product_name}}
Button: {{first_step_button_label}}
Step 2: Nudge toward the first action
Subject: {{first_name}}, your {{product_name}} setup is one step away
Preview text: Pick up where you left off.
Hi {{first_name}},
You created your account yesterday but haven't {{activation_event_past_tense}} yet. That is the moment {{product_name}} starts doing something useful for you, so here is the shortest route to it:
- {{step_one}}
- {{step_two}}
- {{step_three}}
Each link below opens the exact screen you need. If one of these steps doesn't apply to your setup, reply and tell me what you are trying to do; I will point you to the right place.
{{sender_name}}
Button: Finish setup
Step 3: Remove the most common blocker
Subject: The part of {{product_name}} setup people ask us about most
Preview text: Variant for partial setup: You're halfway there. Here's the rest.
Hi {{first_name}},
When new users pause at this point, it is usually because of {{common_blocker}}. Here is how to get past it:
{{blocker_explanation_in_two_or_three_sentences}}
If you would rather see it done once, here is a short walkthrough: {{walkthrough_link}}.
Still not the problem? Reply with one line about what's in the way and I will answer it personally.
{{sender_name}}
Button: Show me how
Step 4: Next step for users who activated
Subject: Nice work. Here is what to try next in {{product_name}}
Preview text: You've done the hard part. One more step makes it stick.
Hi {{first_name}},
You {{activation_event_past_tense}}, which means {{product_name}} is now {{value_now_delivered}}.
The step that usually makes it part of your routine is {{second_value_action}}. It takes the work you have already done and {{benefit_of_second_action}}.
If you are working with a team, this is also a good moment to invite them, so the setup you just finished is shared rather than stored in one account.
{{sender_name}}
Button: {{second_value_action_button_label}}
Step 5: Personal check-in
Subject: Quick question about {{product_name}}
Preview text: One-line replies are perfect.
Hi {{first_name}},
I noticed you haven't {{activation_event_past_tense}} yet, and I'd like to understand why rather than keep sending you reminders.
Which of these is closest?
- I haven't had time yet
- I got stuck on a step
- It doesn't do what I need
- Something else
Just reply with the one that fits. I read every answer, and it changes what we build and how we explain it.
{{sender_name}}
Button: None. Send as plain text and ask for a reply.
What to measure
| Metric | Definition | Why it matters |
|---|---|---|
| Activation rate | Share of new signups who complete {{activation_event}} within your observation window (for example 14 days). | The primary outcome. Compare it with a random holdout group that receives no sequence emails, not with last month. |
| Time to activation | Median time from signup to {{activation_event}} for users who activate. | A sequence can pull activation earlier without raising the total. Both matter. |
| Step click-to-activation | Of the users who click a given email, the share who activate within 48 hours. | Shows which email actually moves people, as opposed to which one gets clicked. |
| Unsubscribes and spam complaints | Per send, for each step. | A rising rate on one step usually means its timing or audience rule is wrong. |
| Reply themes from email 5 | Count of replies by the four answer options. | The cheapest product research you will run. Feed the 'got stuck' answers back into email 3. |
How to run it in Questera
Send your events in
Activation logic needs product events, not just email opens. Elma and Sega both work from your existing data stack, including Segment, Mixpanel and Amplitude, so send {{activation_event}} and signup events from the tools you already use.
Build the audiences with Sega
Sega, the Segmentation Agent, creates segments from activity, demographics and behavior and updates them automatically as user data changes. Create one segment per step rule above; because membership updates in real time, a user who activates drops out of the 'not activated' segment without a manual list pull.
Run the emails with Elma
Elma, the Email Lifecycle Marketing Agent, creates email campaigns, adds and removes users from them, reads product usage data for each user and writes personalized emails. Use the copy above as the brief and let Elma personalize the {{first_step}} and blocker lines from each user's own usage.
Add other channels with Omnia
If email alone is not reaching people, Omnia, the Omni Channel Journey Agent, can run the same steps as a journey across email, SMS and in-app, adding and removing users based on their real-time behavior.
Report with GIA
GIA, the data analysis agent, builds reports and dashboards you can query by chat. Ask for activation rate by signup week, split by sequence and holdout, using the definitions in the measurement table.
A failure worth checking
The most common failure is an exit rule that runs on a batch schedule. If the 'not activated' list refreshes once a day, a user who activated this morning can still receive this afternoon's nudge telling them to do what they just did. Test the exit with a synthetic account: sign up, complete {{activation_event}}, and confirm that no further 'not activated' email is queued.
Common questions
How many emails should an onboarding sequence have?
As many as you need to reach one activation event, and no more. Five is a reasonable starting structure because it gives you a welcome, two practical nudges, a branch for people who succeeded and a final personal check-in. Remove any step that your measurement shows does not change activation against the holdout.
Should onboarding emails be triggered by behavior or sent on a fixed schedule?
Both. The delays in this template are measured from signup, but every step also checks behavior before it sends. That combination keeps the sequence predictable while making sure people who already activated are not nudged.
What should the activation event be?
The first action that shows the user received value, defined in the same way in your analytics and your campaigns. Account creation or a first login is rarely enough. If you are unsure, the field guide on activation event contracts walks through the decision.
Should I gate later emails on opens?
Avoid it. Some mail clients load images automatically, which records opens that never happened, so open-based conditions are unreliable. Gate on product events instead, and use clicks only as a secondary signal.
How do I know the sequence is working?
Keep a small random holdout of new signups who receive only the welcome email, or none, and compare activation rates over the same window. Without that comparison you cannot tell the sequence's effect apart from the users who would have activated anyway.
Basis and scope
This is a starting template with placeholder copy, not a measured benchmark or a customer case study. Prepared with AI assistance. Adapt the copy to your product and audience, and validate timing and audience rules against your own data and test environment before sending.
