Start with subscribers and the backhaul path
For a small ISP with a team in N’Djamena and remote sites, distinguish terrestrial backhaul, long wireless hops and satellite backup. At a VSAT-fed site, measure latency on the actual path and plan recovery after interruption.
These are planning scenarios, not customer references. During a power cut, check the router, CPE and relay power supply before treating an outage as an unpaid account. A payment receipt is not proof that connectivity has returned.
For PPPoE and hotspot access, record the authenticating router, speed profiles and existing session rules. Keep a local diagnostic path when backhaul is interrupted. This page promises neither a local RADIUS region nor offline availability.
What you can evaluate with ISPAgents
- Available: ISPAgents supports subscriber creation and search, and device assignment and removal.
- Available: the TR-069/CWMP ACS receives informs, reads and writes parameters, and provides CPE diagnostics.
- Guided pilot: CRM and Customer 360 foundations support evaluation of customer records and context; they are not a complete CRM/BSS suite.
- Guided pilot: customer billing foundations cover invoices, payments and reconciliation; tax, refunds and production recovery still need validation.
- Guided pilot: MikroTik RouterOS REST operations and SNMP require qualification of models, firmware and reachability.
- Guided pilot: the existing FreeRADIUS adapter provides a Status-Server probe; synchronization, policy write-back and CoA are not available.
- Guided pilot: the service-policy engine offers previews and approvals; live router/RADIUS mutations remain gated on adapters and rollback evidence.
Local payments: integration planned
ISPAgents integration with Airtel Money is planned, not live. Integration with Moov Money is also planned. Confirm the local merchant product, exports and transaction references with the provider.
Moov Money Flooz is a name used in other markets; do not assume a Flooz account or API applies in Chad. Any Flooz integration is planned and needs country-specific qualification. These names do not imply an ISPAgents partnership.
In a guided pilot, ISPAgents payment adapters provide webhook-mapping and settlement-import foundations; local payment API clients remain planned. Prepare anonymized examples of a transaction, duplicate, partial payment and bank settlement. Keep cash and bank transfers as separate reconciliation cases.
XAF: zero decimals and an explicit currency code
Chad uses the BEAC CFA franc, code XAF, with zero decimal places in ISO 4217 / SIX. In an illustrative preparation example, a 15,000 XAF invoice and 10,000 XAF received leave 5,000 XAF to reconcile. This is neither ISPAgents pricing nor proof of complete local billing support.
Keep XAF in every export: XOF and XAF are distinct currencies even though both are called “FCFA”. Validate fees, rounding and invoice fields separately during the guided pilot.
Prepare for outages and support calls
Before a pilot, document site contacts, battery capacity, restart procedure and synchronization windows. Compare payment, session and router-availability timestamps after the link returns. An offline technician app remains planned; do not depend on an offline action queue.
Customer WhatsApp/SMS workflows remain planned. Agree on message language and a manual fallback without promising automatic customer confirmation.
Resources for the pilot scope
Review mobile-money billing — guided pilot, FreeRADIUS — guided pilot, MikroTik — guided pilot and migration preparation.