The shape of the operation
This is an illustrative composite, modeled on operational patterns we see across estate tenants rather than one verified customer's audited results. The shape: several thousand home-plan subscribers across a cluster of estates, hotspot coverage in the common areas, monthly plans paid by M-Pesa, and a small office team who — before automation — spent the last week of every month on renewals.
Before: the month-end week
The ritual was familiar: export the spreadsheet, mark who paid against the M-Pesa statement, hand the disconnection list to the technician, then spend days reconnecting as payments dribbled in — each reconnection a phone call, a manual router edit, and an apology. Two full-time equivalents of work, concentrated into the week everyone dreaded, with mistakes in both directions.
After: the loop runs itself
With reminders, suspension and restoration running from billing state, the month-end week stopped existing as an event. The patterns that follow are consistent across tenants of this shape:
- Payments pull forward — reminders shift a large share of renewals to before expiry day
- Reconnection time collapses from hours-with-apology to seconds-with-receipt
- 'Why am I disconnected' tickets shrink to the genuinely confused few
- The office team's job changes from executing renewals to handling exceptions
The month-end week didn't get easier. It stopped being a thing that happens.
The honest caveats
Two things this doesn't fix: subscribers who genuinely can't pay still churn — automation makes their exit graceful, not impossible — and the first month surfaces every data error the spreadsheet was hiding, which is work. Budget for the cleanup; it's the price of the spreadsheet years, not of the platform.
Honesty note: this case study is an illustrative composite of operational patterns across CoreSync tenants — not a verified, named customer's audited results. We would rather tell you that plainly than invent a testimonial.