WISP Management Software

WISPs need more than billing

A WISP has to manage towers, access points, CPEs, customer locations, technician jobs, router policies, payments, tickets, and stock. If these live in disconnected systems, the owner cannot see the real operating state.

ISPAgents is designed to connect the business state and the network state so teams can answer the questions that matter:

• Who paid and still has no access?
• Which customer is blocked by billing, signal, router policy, or CPE state?
• Which technician has the required CPE or antenna in stock?
• Which tower, AP, or router is tied to a customer complaint?
• Which changes were approved, executed, and proven?

WISP workflows covered

Router and CPE control

WISPs often depend on multiple control paths. ISPAgents should model that reality as protocol-specific, validated paths:

• MikroTik RouterOS API
• Existing FreeRADIUS
• ISPAgents Managed RADIUS early access after tenant launch signoff
• SNMP
• TR-069 / CWMP
• TR-369 USP
• UISP CRM and Network integration
• Custom site and CPE agents

Field service and stock

Field work is where many WISPs lose margin. ISPAgents tracks jobs, equipment, photos, GPS evidence, signatures, cash collection, and technician stock so operations and finance can agree on what happened.

FAQ

Can ISPAgents work with UISP Network?

Yes. UISP integration is part of the target integration layer. The goal is to coexist with UISP where it already manages network assets, while ISPAgents handles broader operations such as billing, payments, support, inventory, and field execution.

Can technicians have limited permissions?

Yes. Technician workflows should be role-limited so field staff can see jobs, capture evidence, use stock, and collect payments without getting unrestricted access to finance or network controls.