CRM should explain the customer state
An ISP CRM is not just a contact database. Support, finance, NOC, and field teams need one customer timeline that explains plan, balance, payment history, service state, RADIUS or router policy, tickets, equipment, and field work.
ISP CRM workflows
| Workflow | ISPAgents role | |---|---| | Customer record | Contact, location, account owner, service, package, balance, and status. | | Billing context | Invoices, payments, credits, refunds, deposits, statements, and aging. | | Access state | RADIUS, MikroTik, CPE, connector result, suspension, restore, and speed policy. | | Support history | WhatsApp tickets, incidents, notes, SLA, summaries, and customer communication. | | Field service | Installs, relocations, upgrades, cancellations, equipment swaps, and technician evidence. |
Better daily work
The best ISP CRM helps a support agent answer the customer quickly: what do they have, what do they owe, why is service affected, and what is the safest next action?
FAQ
Is ISPAgents only a CRM?
No. CRM is one part of the platform. ISPAgents also covers billing, payments, access control, inventory, field service, support, migration, and AI workflows.
Can CRM data be imported?
Yes. Imports should support CSV, Excel, APIs, billing systems, UISP, Splynx, RADIUS, MikroTik identifiers, and custom fields.