The Reactivation Email
One well-aimed message to someone who stopped, sent before they forget you.
The problem it solves
Most users who lapse do so quietly and never announce it. A reactivation message is the one cheap chance to find out whether they left for a fixable reason.
What a reactivation send actually returns
Reactivation targets people who used the product and stopped. It differs from a win-back offer because it leads with a reason to return rather than with a discount, and it differs from a newsletter because it is triggered by an individual's absence.
The mistake teams make is treating all lapsed users as one segment. Someone who never activated has a different problem from someone who used the product for a year and stopped, and a single email cannot speak to both. Segment by how far they got before they left.
Segments and what each one needs
Three kinds of lapsed user
- Never activated
- Signed up, never reached value. They need the shortest path to the first useful outcome, not news about features they have never seen.
- Activated then drifted
- Got value, then life moved. They need their own state shown back to them: the project waiting, the data still there, what changed since.
- Churned on purpose
- Something was wrong. They need evidence it is fixed, named specifically, or they need to be left alone.
Timing decides more than copy. Too early and you are interrupting someone who was going to return anyway. Too late and they have forgotten the password, the point, and the product. The window sits somewhere after their normal usage gap has clearly broken and before the account feels like a stranger's.
- 1Define lapsed from your own usage distribution, not from a round number of days.
- 2Segment by how far the user got before stopping.
- 3Lead with the user's own state, or with a specific change since they left.
- 4Send one. If it is ignored, send at most one more, then stop permanently.
- 5Measure whether they were still active thirty days later, and report only that.
That last point is where most reactivation programmes flatter themselves. Opens and clicks are easy. A returning user who opens once and disappears cost you a permission and bought nothing. If thirty-day retention of reactivated users is near zero, the programme is not working, however good the click rate looks.
When it fits
- You can tell activated users from those who never reached value, and message them differently.
- Something genuine has changed since the user left, or their own saved state is still waiting for them.
- The product has a natural usage gap you can measure lapse against.
- You are willing to cap the sequence at two messages and honour silence.
When it backfires
- The sequence runs to five or eight emails. Repeatedly messaging someone who has stopped responding is harassment on a schedule, and it converts a lapsed user into an active detractor.
- Copy uses manufactured urgency or loss. Telling someone their data is about to be deleted when it is not is a lie, and threatening deletion to force a login is coercion.
- It fires on users who quit for a real reason. Emailing someone who left over a bug or a billing problem, with no acknowledgement of it, confirms nobody is listening.
- Success is measured on opens. A reactivation programme judged on clicks will optimise into clickbait subject lines and produce nothing durable.
Products using it
Duolingo
Sends absence-triggered emails referencing the user's specific course and progress, with a documented cap on messaging users who do not respond.
Figma
Surfaces activity on files the lapsed user owns or was invited to, so the message is about their work rather than about the product.
Notion
Reactivation messaging points at the user's existing workspace content rather than at generic feature marketing.
The psychology under it
The takeaway
Send one message aimed at the specific reason that user stopped, cap the sequence at two, and judge it on thirty-day retention rather than opens.
Finished the teardown? Bank it and the day counts toward your run.