Reactivation vs win-back: the distinction that changes the program

Before the framework, hold the two people in your head. The drifted user got busy, hit a tough quarter at work, stopped opening — the relationship cooled by neglect, not decision. The cancelled user looked at the bill, looked at a competitor, made a call. One is dormant. The other is gone. The table below sets the split.

The success-rate row is where the two programs earn their separate existence. A 20% reactivation rate and a 5% win-back rate aren't the same metric with different numbers — they're measuring different human decisions. The first is “did the quiet user remember we exist and do something.” The second is “did the cancelled user reverse a deliberate choice.” Running both through one sequence means either the reactivation audience feels over-pitched (you're shoving a 50%-off coupon at someone who never decided to leave) or the win-back audience feels under-served (a friendly nudge isn't reversing a cancellation). Usually both at once.

Reactivation is a memory problem. The drifted user has a specific failure mode: they forgot. Got busy. Lost the habit. The product never offended them — it just slipped out of weekly attention. The fix is to lower the cost of coming back to as close to zero as possible: a light-touch nudge with one specific next action. Heavy discounts feel weird here because the user never perceived themselves as having left, which is arguably the most important fact about them. Throwing money at someone who didn't leave reads as desperation, not generosity.

Win-back is a decision problem. The cancelled user made an explicit call, and the call had a reason — price, a competitor, a product gap, a life change. The win-back has to address the reason (or at least acknowledge it) and offer a credible basis to reconsider. Pretending they never left is the most common win-back failure. The second most common is pretending the reason doesn't exist. “We miss you!” sent to someone who cancelled because the product didn't do the one thing they needed lands as deaf, not warm.

For users who went quiet but haven't cancelled, the sequence is short and gentle. Four to five messages, weeks apart, each doing exactly one job. The point isn't to maximise pressure — it's to give a drifted user the easiest possible re-entry while preserving the relationship for the ones who don't come back.

Message 1 — quiet “here's what's new.” Reminds the user the product exists. References something specific (a feature, unread content, recent activity). No discount. No urgency. If you only ship one reactivation message, ship this one — it catches the users who genuinely just forgot.

Message 2 — a low-friction entry point.The single smallest action that gets them re-engaged. Not “log in to your account.” Something like “here's a 5-minute thing worth doing today.” Friction is the enemy at this stage; the user drifted because effort wasn't there, so don't ask for more.

Message 3 — preference adjustment.“Too much mail? Here's how to get less.” Preserves the subscription even if the user doesn't reactivate. Plenty of reactivation wins come from this message — the user switches to a lower cadence instead of fully leaving. That counts.

Messages 4–5 — specific-value content.If the user still hasn't engaged, the last two messages deliver your best content with no ask. If that doesn't move them, they move to the long-sunset track — a slow, low-frequency taper toward removal rather than an abrupt cut, which we'll come back to in a moment.

A good reactivation rate is 15–25% of the cohort re-engaging inside the sequence; strong programs hit 30%+. And the measurement is re-engagement (opens, clicks, a return visit), not re-purchase — the goal at this stage is stopping the slide toward sunset, not immediate monetisation. Programs that try to measure reactivation in revenue terms flatten the sequence into a discount flow, which then underperforms as both a reactivation and a win-back. The mistake is reading too quickly. Pick the metric that matches the audience's actual state.

The 12 win-back patterns guide covers the tactics for each type. The Orbit Win-Back Playbook skill separates the two programs and produces the right sequence for each.

For users who cancelled, the sequence acknowledges the cancellation and gives a credible reason to reconsider. Three patterns earn their keep — and the choice between them depends on why the user left, not on which one feels best to send.

The “what changed” pitch.If there's been a meaningful product improvement since cancellation, lead with it. Specific, recent, and relevant to why they might have left. “Dark mode is live” doesn't win back someone who cancelled for price. “We dropped the price by 30%” might. The match between their reason for leaving and your reason for messaging is the whole game.

The “friendly re-check” message.A direct-from-a-person note that doesn't pitch — just asks how things are going with whatever they switched to. Lowest conversion of the three. Highest-quality conversations. Cancelled users who re-engage through this message tend to return at higher LTV — lifetime value, the total revenue you expect from a customer over the relationship — than incentive-driven wins, because they're opting back in rather than being bought back. The discount-driven returner often re-churns when the discount ends; the conversation-driven returner doesn't.

The specific incentive.If you're going to offer a discount, make it concrete and time-bound. “3 months at 50% off if you restart this week” beats “Come back and save.” Generic re-pitch without an offer to an audience that actively left almost never converts. Vague urgency reads as a template; a specific number with a specific deadline reads as a real proposal.

A healthy win-back reacquisition rate is 3–8% for cancelled-customer sequences. The math matters more than the ratio — 3% of a large churned cohort is real revenue, especially if the LTV of the reacquired customer is decent. Don't optimise for win-back rate alone. Optimise for reacquired LTV, and measure both. A program that pulls 8% back at half their original LTV is, on net, a worse outcome than one that pulls 4% back at full LTV. The headline number lies; the cohort math doesn't.

Running both programs effectively requires clear, exclusive segments — a user should belong to exactly one. The segments are the foundation; without them you're just sending blended messages to a blended audience and hoping the math works out.

Reactivation audience. Active subscribers with no engagement — no opens, clicks, or product activity — in 60–120 days. Still customers, just quiet. The 60–120 window matters: tighter than 60 and you're messaging users who are about to come back on their own; wider than 120 and you're probably messaging people who have effectively left without telling you.

Win-back audience. Users who cancelled, downgraded, or were sunsetted involuntarily (failed payment, expired card, account closed by you). Actively non-customers. The trigger is a definite event, not silence.

Hard suppressed. Hard bounces (the email address doesn't exist any more), spam complaints, and double-opt-outs — users who ticked the unsubscribe box and then confirmed it on a follow-up page. These users should not receive either program. They opted out definitively; respect it. Sending to a suppressed list is the fastest way to destroy your sender reputation, which then tanks deliverability for the campaigns you are still allowed to send.

Can you run both programs from one sequence? Not effectively. A win-back sequence landing on a dormant subscriber reads as out of touch — “we want you back!” to someone who never left. A reactivation sequence landing on a cancelled user reads as unaware — a polite nudge to reopen the app to someone who deleted their account in February. Segment first, then sequence. And sunset cleanly: for reactivation, move to a minimum-touch quiet list after 5 unresponded messages across 60–90 days; for win-back, permanent sunset after 3 messages across 30–60 days. The sunset is the program. Skipping it is how a re-engagement strategy quietly turns into a deliverability problem.

The Orbit Segmentation Strategy skill covers the stage definitions. The segmentation beyond RFM guide covers how to derive these programmatically.