Why do free-text cancellation notes fail?
Most ISPs already ask why a subscriber is leaving. The answer lands in a notes field, typed by whoever took the call, in whatever words came to mind. Six months later nobody can answer the simple question: how many subscribers did we lose to price, and where?
- The same reason is written ten different ways, so it cannot be counted.
- Agents record the last thing said, not the underlying cause.
- Cancellations by email, web form or non-payment often get no reason at all.
- Notes live in the ticketing tool while subscriber data lives in billing, so nobody joins them.
The fix is not a longer form. It is a short, fixed list of reasons that every channel uses, plus an optional note for detail. See how to reduce ISP churn for the wider retention picture this feeds into.
Which disconnection reasons should an ISP track?
Keep the top level to about seven reasons. Too many and agents pick at random; too few and the categories hide the cause. Add sub-reasons only where you will act on the difference.
| Reason | Includes | Controllable? |
|---|---|---|
| Moving | Relocating outside your coverage area | Mostly no, but track moves within footprint |
| Price | Bill too high, promo ending, cheaper plan elsewhere | Partly: offers, plan fit |
| Competitor | New fiber or fixed wireless build, a specific rival offer | Partly: timing and offer |
| Service quality | Outages, slow peak speeds, repeat faults | Yes: network and support |
| Billing dispute | Unexpected charge, unclear invoice line, credit not applied | Yes: billing and communication |
| Non-pay (involuntary) | Disconnected for non-payment and not recovered | Yes: dunning and payment options |
| Other | Deceased, business closed, duplicate account | No, keep it small |
Treat non-pay as its own reason, never as “other.” It is a different kind of churn, with different fixes, and it is often the easiest to win back.
How do you capture a reason on every channel?
A reason taxonomy only works if every cancellation path records it the same way, including the ones where no person is involved.
- 1.Phone and chat: make the reason a required field before an agent can close a cancellation, with the note optional.
- 2.Web and email cancellations: show the same list as a single required question on the form or in the reply.
- 3.Non-payment disconnects: set the reason automatically when the dunning policy disconnects an account.
- 4.Port-outs you learn about late: backfill the reason from the last contact, or mark it unknown rather than guessing.
- 5.Review a sample each month: listen to or read a handful of cancellations and check the recorded reason matches what the subscriber said.
Calls are where reasons get lost most often. Transcribing and summarizing every cancellation call, as Subscriber Intelligence does, lets you check the recorded reason against what was actually said.
How should you report churn by reason?
A single churn rate tells you whether things are getting worse. Churn by reason, area and tenure tells you what to fix and where.
- Reason × month
- Which causes are growing. A rising price share often follows a competitor launch or a promo roll-off.
- Reason × service area
- Service-quality churn concentrated in one sector or tower is a network problem, not a support problem.
- Reason × tenure
- Early-life churn (the first few months) usually points to installation, expectations or first-bill surprises.
- Reason × plan
- Price churn concentrated on one plan suggests the plan, not the market, is the issue.
Zone 07 flagged. Ninety-four contacts from one service area in nine days, clustered before a single one was filed as an outage.
What should you do with each reason?
| Reason | What to do |
|---|---|
Moving Offer a transfer when the new address is in your footprint; otherwise exclude from controllable churn. | Offer a transfer when the new address is in your footprint; otherwise exclude from controllable churn. |
Price Review plan fit before promos end and contact subscribers weeks ahead, not at the cancellation call. | Review plan fit before promos end and contact subscribers weeks ahead, not at the cancellation call. |
Competitor Map where the rival is building and prioritize outreach and offers in those areas. | Map where the rival is building and prioritize outreach and offers in those areas. |
Service quality Send sector-level churn to the network team with the affected addresses attached. | Send sector-level churn to the network team with the affected addresses attached. |
Billing dispute Fix the invoice line or process that caused it; one unclear charge can drive many calls. | Fix the invoice line or process that caused it; one unclear charge can drive many calls. |
Non-pay Tighten reminders, payment plans and reconnection. See collections and dunning. | Tighten reminders, payment plans and reconnection. See collections and dunning. |
Close the loop monthly: pick the two reasons that grew most, assign an owner to each, and check the next month whether they moved.
Where does Inerxia fit?
In Inerxia the subscriber record, tickets and conversations share one dataset, so a disconnection reason sits next to the service area, plan, tenure and support history of the same subscriber. Subscriber Intelligence transcribes, scores and clusters every call and ticket by theme and service location.
The retention agent scores every subscriber daily on usage, billing, network quality and sentiment and steps in weeks before the cancellation, which is where reason data pays off: you learn which causes you can get ahead of.