Welcome → first project nudge → activation celebration.
The day-zero sequence every SaaS needs. A static welcome on sign-up, then a behavior-aware follow-up that only fires if the user hasn't created a project after 3 days.
Real, end-to-end examples of behavior-triggered email, from the event you track in your product to the message that lands in the user's inbox. Each one is a working pattern, not a hypothetical.
The day-zero sequence every SaaS needs. A static welcome on sign-up, then a behavior-aware follow-up that only fires if the user hasn't created a project after 3 days.
Track each step of your onboarding checklist. If a user gets stuck on the same step for more than 24h, send a how-to email that's specific to that step, not a generic "need help?".
A user finishing trial gets one of two emails: highly-engaged users see a "ready to upgrade" message; low-engagement users see a "let us extend it" save offer.
Identify your "habit-forming" event (e.g. report_exported). When a previously-active user goes 14 days without it, send a check-in from the founder, not a marketing template.
A 3-email sequence after cancellation: ask why (week 1), share what shipped since (week 2), offer a discount or comeback path (week 4). Exits if the user re-subscribes.
Send the receipt immediately on order_placed. Then wait 7 days; if the customer hasn't returned to the app, send a post-purchase nudge with their order context inline.
You signed up but haven't invited a teammate after 5 days. For B2B products this is one of the strongest activation predictors; a small in-context nudge does the work.
If a paid user views a higher-tier pricing page twice in a week, send an upgrade email tailored to that exact tier: pre-filled CTA, plan-specific features.
During beta, we'll write the example for you and add it here. The patterns we publish come from real teams.