The complaint that isn't about the network
The angriest support calls aren't about outages — they're about disconnections the subscriber didn't see coming. The connection worked at breakfast and died at lunch, and from their side it looks like your failure, not their lapsed plan. The fix is not softer enforcement; it's earlier information.
A cadence that collects
What works across tenants is a short, boring, predictable sequence:
- Three days before expiry: a reminder with the amount, the paybill and their account number — everything needed to pay from the SMS itself
- Expiry morning: a final notice that names the cutoff time
- On suspension: a message saying exactly how to restore, because reconnection is automatic the moment payment lands
- On payment: a receipt confirming the new expiry date
A disconnection should never be news. By the time it happens, the subscriber has heard three times.
Scoped audiences, not blast lists
Reminders come from the same system that knows billing state, so a reminder cannot fire on an account that already paid — the embarrassing 'pay now' SMS to a paid-up customer simply can't happen. Outage notices work the same way: scoped to exactly the subscribers behind the failed site, so proactive comms empty the support queue instead of filling it.
What it does to the numbers
Two effects show up quickly. Collections shift earlier — a meaningful share of subscribers pay on the first reminder, flattening the end-of-month scramble. And the disconnection-complaint category of tickets shrinks toward zero, because the surprise is gone. SMS reminders are part of both the Basic and Premium plans, and against a reconnection saved, a few messages per subscriber a month isn't close.