Suspension is high-impact automation
Cutting off internet access affects customers immediately. ISPAgents should automate suspension only with clear billing state, service identifiers, access mapping, operator rules, audit evidence, and rollback paths.
Suspension and restore paths
| Enforcement path | Best fit | |---|---| | Existing FreeRADIUS | PPPoE or centralized auth networks with trusted RADIUS policy. | | Managed RADIUS | Operators that want cloud-managed access control and health visibility. | | MikroTik direct control | Queue, address-list, firewall, or site-specific RouterOS workflows. | | Custom agents | Private networks, NATed sites, vendor APIs, or unusual topology. |
Controls operators need
- Preview who will be affected.
- Show invoice, balance, due date, and payment state.
- Show router, NAS, RADIUS, or connector action.
- Require approval for risky batches.
- Record execution result and failures.
- Restore paid customers with evidence.
FAQ
Can suspension run in batches?
Yes. Batch actions should include preview, filters, exclusions, approval, execution status, and post-run evidence.
Can paid customers be restored automatically?
Yes, when payment matching and access mapping are trusted. Otherwise the customer should enter a review queue.