Cancellation flow

A subscriber opens the app in the second week of a billing cycle, taps through three screens looking for the cancel option, gives up, and goes to the store’s subscription settings instead. The subscription ends. Nobody learned why, and nothing was offered.

That is the default cancellation flow at most subscription businesses, and it is made of two separate failures. The first is discovery: on store-managed subscriptions the cancel action lives in the store, so an app that does not surface a route to it hands the whole conversation to a screen it does not control. The second is silence. The store asks nothing on the publisher’s behalf, so the reason for leaving, which is the single most useful piece of retention data a business can collect, evaporates at the exact moment the subscriber was willing to state it.

A flow worth building does three things in order. It makes the exit findable, because hiding it now runs into click-to-cancel rules as well as into the subscriber’s patience. It asks one question about why, kept short enough to answer honestly. Then it responds to the answer rather than to the fact of cancelling: a price objection and a content gap and a temporary break each call for a different response, and only one of them is a discount. Building that as branching logic instead of one confirmation screen is what Flows is for, and it means the pause offer reaches the subscriber taking a break without going to the subscriber who has simply finished with the product. The reasons collected on the way out are also the closest thing to a roadmap the retention team will get.