Payment and support workflows matter first
For Senegal ISP and WISP operators, the first value should come from reducing manual collection, customer follow-up, service restore, and support work. ISPAgents should support local payment integration through an abstract provider layer and connect it to billing and access state.
Rollout focus
| Area | What to configure | |---|---| | Payments | Mobile money, cash, bank, SMS, WhatsApp, receipts, and reconciliation. | | Billing | Prepaid, postpaid, renewals, grace periods, invoices, balances, and aging. | | Access | Managed RADIUS, existing FreeRADIUS, MikroTik direct control, and custom agents. | | Support | WhatsApp tickets, customer timelines, outage context, and AI summaries. | | Field operations | Technician jobs, GPS, photos, signatures, and equipment used. |
First workflow to prove
Prove overdue collection, payment matching, automatic restore, and support visibility for a small customer group before expanding to full migration.
FAQ
Can ISPAgents add local payment providers?
Yes. The payment layer should be abstract so provider-specific integrations can be added by region.
Can an ISP keep existing FreeRADIUS?
Yes. Existing FreeRADIUS, managed RADIUS, MikroTik, and custom connector patterns should all be supported.