ChurnNote

Cancel flow examples

Cancel flow examples, broken down.

Four cancel flow patterns you'll actually see in SaaS, what each does well, when to use it, and where it goes wrong. Pick the one that fits your stage.

Run the free Churn Leak ReportStart ChurnNote for $12/mo
1

The reason-survey flow

How it works: A single 'why are you leaving?' question with 4-6 options and an optional text box, then a confirm. No offers.

Good for: Simplest to build, respectful, and gives you reason data on every cancellation.

Watch out: It saves no one on its own. Pair it with a follow-up email or reason-matched offers to actually retain.

2

The pause-first flow

How it works: Before any cancel, offer to pause the subscription for 1-3 months as the primary call to action, with cancel as the secondary link.

Good for: Saves 'too busy / not using it right now' customers without discounting. Great for seasonal or project-based usage.

Watch out: Don't make pause the only option or hide cancel. That's a dark pattern and erodes trust.

3

The reason-matched offer flow

How it works: Ask the reason, then branch: price -> discount or cheaper plan; not using it -> pause or onboarding; missing feature -> roadmap note + follow-up; bug -> support handoff.

Good for: Highest save rate because each offer is relevant. The gold standard for higher-volume SaaS that can A/B test.

Watch out: Most work to build and maintain. Resist offering discounts to feature/bug churners. It won't fix their reason.

4

The respectful one-click exit

How it works: A confirm screen that states the access end date and what happens to data, with one clear cancel button, then a follow-up email later.

Good for: Best for trust and for small SaaS. Customers remember a clean exit and come back. The follow-up does the learning.

Watch out: You save fewer customers in the moment. The win-back happens later, via the follow-up, when you've fixed the reason.

FAQ

What's the best cancel flow example to copy?▼
For higher-volume SaaS, the reason-matched offer flow saves the most. For small SaaS, the respectful one-click exit plus an after-cancellation follow-up email gives most of the upside with the least build effort and no risk of dark-pattern backlash.
Should a cancel flow always include an offer?▼
No. An offer only makes sense when it addresses the reason. A pause for 'not using it' or a discount for price-sensitivity works; an offer for a missing feature or a bug doesn't, and can feel tone-deaf. When in doubt, capture the reason and follow up rather than throwing money at it.
How long should a cancel flow be?▼
Short. One reason question and at most one relevant offer. Every extra screen increases frustration and chargeback risk. The depth should be in the follow-up and your response to the reason, not in the number of screens between the customer and the exit.
What do the best examples have in common?▼
They respect the customer, ask why, and follow up. The save attempt is relevant and optional; the exit is easy; and the reason is captured either in-flow or via a follow-up email so the business learns even when it doesn't retain.
Where does ChurnNote fit in these examples?▼
ChurnNote powers the follow-up that all four examples benefit from: after the cancellation, it emails the customer, captures the honest reason, groups it, and queues a win-back. It complements any in-app flow, or stands in for one if you don't build it.

Every good flow ends with a follow-up.

ChurnNote sends it automatically, captures the reason, and queues a win-back when you fix it. Flat $12/mo.

Run the free Churn Leak ReportStart ChurnNote for $12/mo

Related

How to build a cancel flowCancel flow best practicesCancel flow offer examplesCancel flow feedback questionsBest cancel flow tools