Cancellation Flow
Method
The order of screens a customer passes through to end a subscription, together with whatever is placed there to keep them.
Why it exists
Companies used to believe that making cancellation hard kept customers. The button went three menus deep, or it wasn't available on screen at all and had to be done by phone. Easy to sign up for and hard to leave is a pattern called a roach motel.
That approach loses twice. Customers who have decided to leave leave anyway, and they tell people how it went. Meanwhile the company collects nothing about why they went. Add the support tickets asking where cancellation lives, each of which needs a person, and the cost is real. So cancellation started being treated as a flow to design rather than a wall to build. The reasoning is that a customer who leaves cleanly can come back, and one who leaves angry becomes a review.
How to run it
Put the button somewhere findable, collect the reason, and offer one alternative that matches it.
- Place the cancel button within two clicks inside settings. Hiding it raises ticket volume, and those tickets are a direct cost that shows up in the support queue rather than in revenue.
- Say what disappears before anything else. Whether teammates lose access, whether documents stay readable, when data gets deleted. Some people stop here on their own once they see what a shared workspace loses.
- Ask why. A cancellation survey with five or six options plus a free-text field goes here.
- Offer one alternative matched to that reason. Too expensive gets a lower tier; not needed right now gets a pause — a save offer. Stack two of them and the trust built in step one is gone, along with any chance of an honest answer in step three.
- Let it finish, and leave a way back. Stating on the confirmation screen how long data is kept brings some customers back. Enterprise accounts follow the termination clause in their contract rather than this screen, so they sit outside the flow.
How it sounds at work
"We're not going to act on the request to make the cancel button harder to find."
Confirming that retention won't be attempted structurally.
"A quarter of the people who reach the cancellation screen choose pause instead."
One alternative is genuinely substituting for cancellation.
"Let's promote moving to a competitor into the list of reasons."
The same answer keeps appearing in free text, so it should become an option.
After Pagedeck added a pause option to its cancellation screen, 23 percent of the people who reached that screen chose pause over cancelling. Sofia had heard the same request for a two-month break from her accounts repeatedly, and Mia placed it in step four as an alternative rather than in step three as a survey option.
Easily confused with
| Term | What it is | How it differs from a cancellation flow |
|---|---|---|
| Churn prevention | Catching the signs of leaving early and acting on them | The whole activity that happens before anyone decides. A cancellation flow is the screens someone sees after they already clicked cancel |
Where to go next
- Subscription
see the billing structure this flow attaches to
- Auto renewal
see the mechanism that continues the cycle from the other side
- Cancellation survey
see what gets done with the answers this flow collects
Related terms
Last updated 2026-09-16