WISP billing

WISP Billing Software

Run WISP billing with payments, controlled access workflows, tower and CPE context, technician workflows, inventory, support, and operator-reviewed AI summaries.

WISP management
Operator console

Subscribers, devices, and access in one view

subscribers
4.2k
sites live
3
critical fails
0
LiveSubscriber + device identityMapped
ActionGuarded command previewApproved
AuditEvery change loggedTracked
One operator surface ties each subscriber to their devices, access, and history.
Page type
Solutions
Primary search
WISP billing software
Updated
2026-05-24

WISP billing touches the network

WISP billing is tied to towers, APs, CPE, technician work, service packages, payments, and access control. ISPAgents should connect those operating details instead of leaving billing isolated from the field and network teams.

WISP billing workflows

WorkflowISPAgents role
Plans and packagesPrepaid, postpaid, speed packages, discounts, deposits, and custom durations.
PaymentsMobile money, cash, bank, SMS, WhatsApp, matching, receipts, and reconciliation.
AccessValidated MikroTik, FreeRADIUS, managed RADIUS, CPE agent, and custom site connector paths.
Field jobsInstalls, relocations, signal checks, equipment swaps, photos, GPS, and closeout.
InventoryCPE, antennas, routers, warehouse stock, technician stock, and serial numbers.

What to control first

Start with renewal reminder, payment matching, access restoration, and support timeline update. That workflow creates value quickly and reveals data gaps.

FAQ

Can ISPAgents support towers and CPE?

Yes. WISP operations should track sites, towers, APs, CPE, field jobs, equipment, and customer service state.

Can WISP billing use MikroTik?

Yes, as validated deployment paths. MikroTik direct control, RADIUS, and custom connectors should be selected per site and gated by preview, approval, audit, and rollback evidence.

Next step

See how this works in your network.