Subscription pause

Every subscriber who cancels for a reason that ends becomes a re-acquisition problem. The person travelling for three months, the household cutting back until a paycheck lands, the sports fan whose season finished in June: each of them leaves over something temporary and comes back, if they come back, through the same paid funnel as a stranger.

A pause turns that exit into a gap. Billing stops, access usually stops with it, and both resume on a known date without anyone deciding again. What differs is how much of that the store will do for you. Support varies by platform, and where the store exposes no native pause the publisher has to construct the equivalent out of what it does control, which usually means a downgrade to a cheaper tier or a scheduled win-back rather than a true hold. Knowing which of those you actually have on each platform matters before the option gets promised anywhere in the interface.

The retention question is not whether pause exists but where it appears. A pause buried in account settings gets found by people who were already staying. The same option offered inside the cancellation flow, to the subscriber whose stated reason is a break rather than the product, is the one that changes the outcome, and it needs to know something about who is asking: tenure, plan, and whether this is a first cancel attempt or a third. That branching is journey logic rather than a billing toggle, so it gets built in Flows, where the pause rate and the resume rate can both be read afterward. The second number is the one that says whether the pause worked or just deferred the loss.