Guide
Cancellation Flow Segmentation: Route the Right Experience to Each Customer
A single cancellation flow works until it does not. Your annual enterprise plan and your self-serve monthly trial are not the same customer — but one generic discount screen treats them that way. Segmentation means choosing which cancel experience someone sees before you ask why they are leaving.
This guide covers audience-based routing: multiple flows, priority order, default fallback, and what to segment on first. It does not replay scenario walkthroughs — those live in cancellation flow examples. It also does not replace offer strategy — see retention offer strategy for which offer fits which reason.
Last updated October 13, 2026
Segmentation vs reason-based scenarios
| Axis | Question answered | Example |
|---|---|---|
| Audience segmentation (this cluster) | Which flow does this customer enter? | Trial users → short survey; paid annual → CS contact offer |
| Reason scenarios (Cluster #1 #2) | What happens inside a flow after they pick a reason? | “Too expensive” → coupon step; “Missing feature” → roadmap link |
How priority-ordered routing works
ChurnIntel resolves flows this way: non-default flows are tested in priority order; the first whose audience rules match the subscription context is shown; otherwise the default flow runs. See Stripe cancellation flow implementation for how cancel actions reach Stripe after the flow completes.
- Publish multiple flows, each with audience rules (plan, interval, trial status, age, price band, discount state, custom attributes)
- Assign lower priority number = evaluated first (first match wins)
- Exactly one default flow catches everyone who matches no targeted rule
- Do not stack overlapping rules without intent — ambiguous priority creates “wrong offer” support tickets
When to add a second flow
- Trial vs paid — different save ethics and product data (dedicated guide below)
- Plan tier or billing interval — price and commitment differ
- High recurring value — human touch instead of self-serve coupon
- Discounted cohorts — avoid stacking another coupon on active promos
If every segment would see the same steps and offers, keep one flow and invest in reason mapping instead.
Segmentation playbooks
Measure segmented flows
Compare outcomes per flow: completion rate, offer acceptance, lost MRR — not a single blended save rate. Methodology: customer churn analysis.
Priority-ordered flows with audience rules
ChurnIntel lets you run multiple cancellation flows in your app — plan, interval, trial, age, discount, and custom attributes — with a default fallback.