Onboarding email flows: signup to activated

Before you write a single email, define the activation event. This is the single most-often-skipped step in onboarding work, and the reason so many programs can't tell whether they're working. Activation is a specific, measurable action that empirically predicts long-term retention. Signed up is not activation. Opened the app twice is not activation. Completed a profile is rarely activation.

What is: a threshold you derived from your own data, tuned so that users who cross it retain at 2–3x the rate of users who don't. For a messaging product it might be a specific count of messages sent in the first month; for a subscription product it might be reaching a feature or workflow; for a marketplace it might be a second transaction. The number itself isn't meaningful — the discriminating power is. Pick a signal that's behavioural (the user DID something), measurable (you can count it per user), and predictive (retention curves split visibly either side of the threshold).

A representative activation funnel, showing the typical drop-off from signup to activated:

Most activation happens in the first 72 hours or not at all. The onboarding sequence has to match that urgency — spreading six emails across 30 days means half your audience has already decided by email four. The 72-hour window guide covers the intervention grid in more depth; for the sequence itself, a practical structure:

Hour 0 — Welcome with one specific action.Not "explore the product". Not "here's what we do". One clear CTA that moves the user toward the activation event.
Day 1 — Value proof.Show the user what they're going to get from the product, ideally with a specific example. Don't ask for another action — show value first, earn the next ask.
Day 2–3 — The second action. The next meaningful step toward activation. Differentiated by whether the user completed the hour-0 action or not.
Day 5 — Social proof or pattern. How other users are succeeding. Works when real users are referenced specifically; reads as noise when generic.
Day 7 — Check-in. Friendly, low-pressure. This is the message that separates the users still on the journey from the users who have silently dropped out.

All messages are conditional on the user NOT having activated yet. The moment the activation event fires, the sequence stops and the user moves to the post-activation lifecycle stage. Continuing to send onboarding emails to activated users is how you train them to ignore you.

The email sequence is one channel. In-product tooltips, checklist widgets, and empty-state prompts are another. Push notifications are a third. If these three don't coordinate, you send the user the same reminder four times and create friction instead of progress.

Coordination means: the in-product checklist drives the canonical state of what the user has completed. The email sequence reads from that same state and adapts content accordingly. Push notifications fill the gaps where email timing is wrong (overnight pushes don't work; overnight emails often do). And no channel fires its "you haven't done X yet" message if another channel just fired the same reminder within the last N hours.

The Orbit Multi-Channel Orchestration skill handles exactly this — channel selection logic, frequency governance, and the adaptive sequencing that lets onboarding programs actually behave coherently.

The data you collect at signup tends to be the minimum viable — email, maybe a password, maybe a name. That's right, because asking for more at signup increases drop-off. But you still need that additional data to personalise the lifecycle program. Progressive profiling is how you get it: collect more user data over time, at moments when asking makes sense.

The practical rule: tie each additional data request to a specific piece of product value the user is about to receive. "What industry are you in?" alongside a feature that genuinely changes based on industry. "What's your team size?" alongside a pricing page. Never a generic profile-completion email with a form full of demographic questions — that converts poorly and signals to the user that you're doing data collection, not personalisation.

An onboarding sequence is complete when one of three things happens: the user activates (fires the activation event), the user reaches the explicit end of the sequence without activating (transition to the non-activated-user lifecycle stage), or the user hits a hard negative signal (marked the email as spam, unsubscribed, hasn't opened any message in N days).

The third condition is the one most often missed. A user who hasn't opened any email in the sequence is telling you they don't want these emails. Continuing to send them damages sender reputation (see the Deliverability Management skill for the connection) and produces a tiny incremental activation rate. Cut the sequence short when engagement signals are clearly negative.