Skip to content
UX Atlas
Case studyCraft conventionIntermediate

Designing a Cancellation Flow

A retention gauntlet kept subscribers for one more month and produced public complaints, regulatory attention and worse reactivation.

Definition

A decision case about offboarding: the short-term retention argument for cancellation friction, the costs it produced, and what replaced it.

Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.

On this page
  1. Definition
  2. Sources
  3. Continue from here

A composite scenario assembled from situations that recur across teams. It is written to teach reasoning rather than to report on a named company, and outcomes are stated directionally rather than as invented measurements.

Problem

Cancellation required five screens, a phone call in some regions, and a retention offer that could not be skipped. Complaints were appearing publicly and support volume was rising.

Context

A consumer subscription product with a retention team whose target was cancellations prevented. The flow had been optimised repeatedly against that single metric.

Constraints

  • The retention target was in place for the current year.
  • Genuine retention offers existed and did help some users who had a fixable problem.
  • Several markets had introduced or were introducing rules requiring cancellation to be as easy as signup.

Decision

Reduce cancellation to two steps: a single reason question that can be skipped, and confirmation. Offer a targeted alternative only where the stated reason has a real remedy, such as pausing for a user who is going away.

Rationale

The flow was optimised for a metric that measured the wrong thing. Preventing a cancellation this month while producing a person who will never return, and who tells others, is a net loss that the metric could not see. Regulatory change also made the existing flow a compliance risk rather than a design preference.

Evidence used

  • Reactivation rates for users who cancelled easily in one market versus those who went through the full flow in another.
  • Support contact volume attributable to cancellation.
  • Public complaints and review sentiment mentioning cancellation specifically.
  • Legal review of the FTC negative option rules and equivalent EU consumer protection requirements.

Trade-offs accepted

  • Immediate cancellations rose, which showed up as a worse number in the current quarter.
  • The retention team's target had to be renegotiated, which was an organisational rather than a design problem.
  • Some genuinely useful retention offers were shown to fewer people.

Outcome

Cancellations rose in the short term and reactivation improved over the following year. Support volume fell, and cancellation stopped appearing in negative reviews. The compliance risk was removed.

Alternatives considered

Keep the flow and improve the copy

Why not: The problem was the number of steps and the inability to skip them, not the wording. Better copy on an obstructive flow reads as manipulation.

Keep one retention offer for everyone

Why not: An untargeted offer is noise for the majority whose reason it does not address. Targeting by stated reason keeps the useful cases without the friction.

Wait until the regulation applied in the main market

Why not: The reputational cost was already being paid, and building it twice would have cost more than building it once.

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  • Negative Option Rule and enforcement actions

    US Federal Trade Commission

    Rules covering automatically renewing subscriptions and the ease of cancellation.

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

Concepts behind this decision

What the reasoning in this case rests on.

Short definition

The one-paragraph version, for when that is all you need.