# How to Build an Onboarding Email Sequence Type: Playbook Canonical: https://sendops.dev/guides/onboarding-email-sequence/ Publisher: SendOps Updated: 2026-10-04 An onboarding email sequence helps a new customer reach a useful first outcome. Start it at signup, introduce one action at a time, branch on product activity, and stop the onboarding reminders when the customer activates. The example below is a starting design, not a claim that one schedule fits every product. ## Journey at a glance - **Who it helps:** New customers who have signed up but have not reached their first useful outcome. - **What starts it:** Account signup, with an activation signal from your product. - **The sequence:** Welcome → wait → check activation → offer a tip or practical help. - **When it stops:** Activation, account closure, or the end of the planned sequence. - **What to measure:** Activation rate and time to first useful action, alongside skipped sends and delivery failures. - **Beyond email:** Ask your app to send a push nudge to an eligible contact who needs help getting started. ## Start with a first win you can measure Choose one action that demonstrates the customer has used the product successfully: publishing a page, creating a project, inviting a teammate, or completing an integration. Account creation alone is rarely the whole job. Record that action in your product and send it to your workflow platform as activity or a contact attribute. The workflow needs a trustworthy signal to decide whether to help, move on, or exit. - Entry: a new account with the appropriate email permissions. - Goal: the customer completes the first useful action. - Exit: activation, account closure, or another condition that makes onboarding irrelevant. ## A three-message sequence to adapt Immediately after signup, welcome the person and point to the first useful action. Keep the email focused: one next step, a clear link, and a way to ask for help. An example subject is “Your first project starts here.” After a two-day wait, check the activation signal. If they have completed the action, offer a more advanced tip or exit this journey. If they have not, send a short guide addressing the most common obstacle. An example subject is “Need a hand with your first project?” After another few days, make the last onboarding follow-up specific and low pressure. Offer an example or a direct path to support. These waits are illustrative; adjust them to the time a customer reasonably needs to try your product. ## Branch on progress, not just the calendar A customer who has already created five projects should not receive a message explaining how to create the first one. Evaluate the activation condition before each relevant follow-up, and use a goal exit to end redundant reminders. Use product actions as the primary signal of progress. An email open can provide context, but it does not prove the customer completed the task. Check what the product actually recorded. ## Add a push nudge when they need a hand After the welcome email, wait for the first useful action. If the contact has not created a project, call a webhook that asks your app to send a push notification. Your app owns device registration, permission checks, and delivery through its push provider. Give the webhook a failed branch that sends a getting-started email if your service cannot take the action. Record project creation back into SendOps as activity so the same workflow can respond to progress across channels. ## Build it in SendOps Connect your AWS account, prepare your sending domain, and bring in contacts and activation activity. Create the welcome and help templates. On the workflow canvas, add the entry trigger, send, wait, and branch. The SendFlow source is another view of that same definition. Set enrollment scope deliberately: a new-user journey may need future signups only. Review topic consent, frequency caps, and the goal exit. Use a fixed cohort list for a shadow rehearsal, inspect the timeline, then review the enrollment estimate before going live. ## Measure the customer outcome Track how many enrolled contacts reach activation, how long it takes, and where people stop progressing. Inspect delivery failures and skipped sends before concluding that the copy is the problem. Change one useful part at a time: the first action, the wait, or the help message. Keep the version history so the team can explain what changed. Avoid claiming that a higher open rate alone means the onboarding worked. ## Common questions ### How many emails should an onboarding sequence contain? Use the fewest messages needed to help someone reach the first useful outcome. The three-message example here is a starting point. Add a message only when it addresses a distinct need. ### When should onboarding emails stop? End redundant onboarding messages when the activation goal is met. Also respect unsubscribe and suppression at send time, and define exits for account states that make the sequence irrelevant. ### Can I run onboarding emails alongside transactional SES email? Yes. SendOps workflows deliver through your AWS SES account while your application can continue its existing direct SES sending integration. ## Sources and related reading - [Trial conversion workflows](https://sendops.dev/guides/trial-conversion-email-workflow/) - [Workflow builder](https://sendops.dev/product/workflows/) - [Audience and product activity](https://sendops.dev/product/audience/)