Retention flows must not block cancellation

What it is

Once cancel is tapped, the UI may ask why, offer a discount, or suggest a downgrade, but completing cancel must stay unblocked. Blocking is: must phone, must wait for support hours, must watch a video, must pick a reason, confirm buried in a fold. Reachability is whether the door can be found; this is whether, inside the door, leaving is still allowed.

Why it happens

Retention leans on loss aversion and extra friction: another “half price for a month” pulls the decision from “stop charging” back into comparison. One optional choice can be information; a forced survey, extra confirms, and “still cancel” as grey small type turn retention into a gate. People mash reasons to end the task, the data rot, and the cancel is remembered as hostility. Phone-only cancel adds a time gate: after hours you cannot cancel, so the right is tied to opening hours. Once the block is recognized, people chargeback; the merchant loses more than this period.

Studying it

Compare cancel flows: one-tap confirm, one optional retain, required survey, required call. Watch time to completed cancel and diversion to chargeback.

Independent variables: retain skippable, required fields, visual weight of “still cancel,” human-only and time-bound. Dependent variables: cancel completion, duration, survey answer credibility, chargebacks.

Lab participants instructed to cancel will bull through gates; that is not real abandon. Remote unincentivized tasks are closer. Do not use “retains won” as the only metric—put beside it the people the gate turned away who then went to the bank.

Where it stops holding

When law requires identity to cancel, verification is not retention, but failed verification needs a written or mail fallback, not phone-only. Enterprise contract termination is legal process, not self-serve subscribe. Accidental cancel may get a short undo window; the window must be short and default to completed cancel, not default to keep charging.

Applying it

• At most one retain screen, skippable; the primary control completes cancel, the offer is secondary.
• Reason questions optional; cancel works with none.
• Do not bind completed cancel to a call, live chat, or an ad.
• Verify a cancel walkthrough: between tapping cancel and state “will not renew,” were there non-optional steps. Required survey, phone, or a hidden complete control is a block.

Related

• Within the group: H7.08.1 Renewal date and amount need advance notice · H7.08.2 Cancel must be at least as reachable as subscribe
• Adjacent: O4.03 Dark patterns in subscribe and cancel · H7.14 Subscriptions, renewal, and cancellation · H3.05 Confirmation dialog abuse
• Search terms: cancel retention · confirmshaming · blocking cancellation