Early cancellation signals hiding in ordinary renewal calendars

Most subscription teams treat the cancellation event as the start of the story. In practice, the decision often forms earlier — in a pause request that never converts back, in a support ticket about a feature that used to matter, or in a quiet drop in usage during the two weeks before renewal.

When we review retention for membership and replenishment brands in Thailand, we ask for the calendar around the billing date, not only the final status change. A cluster of ‘temporary hold’ requests in the same week as a price change is a different problem from scattered holds across the year.

A practical first pass: list every pause and cancellation in the last six months, then mark what happened in the fourteen days before each event. Patterns tend to surface without complex modelling — a particular plan tier, a fulfilment delay, or a support topic that repeats.

The aim is not a longer report. It is a short list of signals your care team can notice while there is still time to respond with a human conversation rather than an automated win-back sequence.