Retention
Live in Churnkey
Reason-Matched Save Offers
Ask why the subscriber is cancelling, then route them to the offer that answers that reason—price objections get right-sizing, dormancy gets a pause, and a generic one-size-fits-all offer answers nobody.
Reason-routed offers outperform one-size-fits-all offers in Cancel Flows
structured cancel-reason and save outcomes across hundreds of orgs
Consistent effect across multiple independent deployments.
How we grade evidence →Event trigger · Edition 1 · June 2026
What is it?
A subscriber on the way out volunteers the single most valuable piece of targeting data an org will ever get: the reason. A structured cancel-reason question—one tap, fixed options—captures it, and the flow routes on it. "Too expensive" routes to a right-sizing offer. "Not using it right now" routes to a pause. "Missing a feature" routes to product help or the roadmap. "Switching tools" gets a clean, respectful exit.
The premise is that cancellers are not one population, and a single offer treats them as if they were. A discount answers a price objection and nothing else; a pause answers a usage gap and nothing else. Matching the offer to the stated reason puts the right answer in front of each subscriber instead of the average answer in front of all of them.
What the evidence shows
Across the platform, Cancel Flows that route on the stated reason outperform single-offer flows. The pattern in the underlying data is the explanatory part: offer acceptance concentrates where the offer matches the reason—price offers convert price objectors, pauses convert the temporarily dormant, and each performs poorly against the other’s population.
The direction is consistent across orgs; the magnitude is not, because it depends on each org’s reason mix. An org whose cancellers are mostly price-sensitive gains differently from one whose cancellers are mostly dormant. The honest read is that routing reliably beats not routing, and how much it beats it is a property of the audience.
How it runs
In production, the Cancel Flow opens with a structured reason question—a short list of options, answered in one tap, never a free-text field standing between the subscriber and the exit. The selected reason determines the next screen: a right-sizing offer, a pause, a product-help or roadmap path, or a direct route to confirmation for subscribers who are switching tools.
Every reason has a route, and every route includes the exit. The reason data flows into analytics whether or not an offer is accepted, so the org learns its cancel-reason mix even from the subscribers it loses. Subscribers switching tools are not chased with a discount; an exit interview yields more there than a price cut does.
Run this for your business
Want to run Reason-Matched Save Offers for your business? Connect the Churnkey MCP to your favorite AI agent. It reads your own usage and billing data and recommends the growth and retention plays most likely to move your LTV—starting with whether this one fits.
npm install -g @churnkey/mcpThis tactic maps to a Churnkey feature—the same play, running in production.
See it in action in ChurnkeyMore in Retention
All tactics →
Bill the Right Person
In B2B subscriptions the person who sees the dunning email is often not the person who owns the card—declare a billing contact and route recovery there, instead of letting payment-failure messages die in an end user’s inbox.
View tactic
Dunning SMS
Add SMS to the dunning sequence—a failed payment is time-boxed, and a text reaches the subscriber inside the window in a way email increasingly does not, with the gap widest at consumer membership orgs.
View tactic
First-Screen Save Offer
Put the best save offer on the first screen of the Cancel Flow, not after the exit survey—every screen before the offer sheds the very subscribers the offer could save.
View tactic
Put the evidence to work.
The same dataset behind these tactics powers Churnkey's retention products. See what it finds in your subscription data.
