Onboarding email sequence for signups who never activated

Send a few notes from account create until they do the thing the product is for (first project, snippet, calendar, invite). Stop the moment they activate. This is not a welcome drip and not employee onboarding.

Updated September 3, 20262 min read

Four emails, then stop

Four sends is enough for most self-serve products. Do not welcome. Do not list features. If they activate, cancel the rest.

Email 1: same day or next morning
FromAlex at Acme <[email protected]>
ToMaya Chen
you stopped at inviting teammates

Hey Maya,

You signed up Tuesday and stopped at inviting teammates. Last event I see is opened invite modal on Tuesday evening.

Pick up here: https://app.acme.com/continue

Alex

Email 2: two to three days later
FromAlex at Acme <[email protected]>
ToMaya Chen
two steps left in your setup

Hey Maya,

Two steps left in your setup. The next one is inviting teammates.

https://app.acme.com/continue

Alex

Email 3: about a week (only if you can finish the step)
FromAlex at Acme <[email protected]>
ToMaya Chen
Maya, inviting teammates is already done

Hey Maya,

Inviting teammates is already done. I finished the step you stopped on so the workspace is ready.

If it's useful, continue from here: https://app.acme.com/continue

Alex

Email 4: about two weeks
FromAlex at Acme <[email protected]>
ToMaya Chen
we'll stop after this

Hey Maya,

We'll stop after this. You signed up Tuesday and never invited a teammate, so this is the last note unless you want help.

Reply if you want a hand. Otherwise I won't keep writing.

Alex

Trigger on signup, stop on activation

A calendar drip punishes people who move fast and ignores people who stall on one step. Fire from signup. Send the next note only while they still have not activated. Cancel everything the moment they do. Quiet users who already activated belong on the lifecycle email hub. Cancelled accounts belong on win-back.

  • Name the incomplete step from events. Do not say “getting started.”
  • Make the next step smaller than the last email.
  • You need a signup event and an activation event in the product.

More subjects and bodies: onboarding email examples.

Exit, skip, and do not stack

  • Cancel remaining sends the moment they activate.
  • Skip steps they already finished.
  • Do not run this on top of another automation for the same moment.
  • One frequency count across sequences and campaigns.
  • Start narrow. Expand what beats holdout.
  • If they reply “stop,” suppress.

What to measure

Activation or paid conversion against a holdout. Opens do not count.

FAQ

How many emails?

Four, then stop, unless they already activated and the rest cancelled. Simple products can run fewer.

Calendar or events?

Events. Calendar timing is only a fallback while activation is still missing.

Is a welcome email an onboarding sequence?

No. Welcome celebrates the signup. Onboarding moves a stalled account to first value.

Do I need a holdout?

Yes, if you want to know whether the sequence caused activation. Opens will look fine either way.

Will this send without asking?

It should not. Draft, show it, wait for approval.

Get started

Put Ranla to work this week.

Connect product events and your sending domain. Ranla runs transactional and lifecycle mail from your domain, and shows you where users are dropping off.

Start free