Collections should be visible
Small ISPs often collect through mobile money, cash, bank transfer, SMS, WhatsApp, and manual follow-up. ISPAgents should centralize the state so the team can see who owes money, who paid, who needs restoration, and what still needs reconciliation.
Collection workflows
| Workflow | ISPAgents role | |---|---| | Aging | Show overdue customers by plan, area, collector, and risk. | | Reminders | Trigger SMS or WhatsApp reminders based on due date and customer segment. | | Payment matching | Match provider references, cash receipts, bank transfers, and invoice records. | | Collector app | Limit cash collectors to assigned accounts and controlled receipt workflows. | | Service restore | Restore paid customers through RADIUS, MikroTik, or a connector after confirmation. |
AI-assisted collections
A collections copilot should prioritize accounts, explain payment history, suggest reminders, and flag customers who should not be suspended because of open disputes or active field jobs.
FAQ
Can ISPAgents handle prepaid and postpaid collection?
Yes. The collection workflow should support prepaid renewals, postpaid invoices, partial payments, deposits, credits, and finance review.
Can service be cut off automatically?
Yes, but automatic suspension should be based on trusted billing state, previewed access action, and audit evidence.