ISP Inventory Management — Guided pilot
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap.
Subscribers, devices, and access in one view
The workflows below are evaluation requirements, not a list of shipped modules. Anything beyond the scope above is Roadmap.
Equipment is part of the customer record
ISP inventory is not just a stock count. The operator needs to know which router, CPE, ONT, antenna, cable, or serialized asset is in the warehouse, with a technician, installed at a customer, assigned to a site, or waiting for replacement.
Inventory workflows
| Workflow | Evaluation requirement (roadmap beyond the scope above) |
|---|---|
| Warehouse stock | Track available, reserved, damaged, returned, and serialized equipment. |
| Technician stock | Assign equipment to technicians and reconcile what was used or returned. |
| Customer equipment | Link serial numbers, models, install date, service, and support history. |
| Replacement | Move old and new equipment through job closeout and customer history. |
| Finance | Support deposits, charges, refunds, and write-offs where needed. |
Why it matters
Inventory errors become support and finance errors. A customer may be billed wrongly, a technician may arrive without equipment, or support may troubleshoot the wrong device.
FAQ
Does ISP inventory need serial numbers?
Serialized tracking is important for routers, CPEs, ONTs, antennas, and high-value equipment. Consumables can be tracked with simpler stock counts.
Can inventory connect to field service?
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap. Confirm the required workflow separately before rollout.
Continue the operations map.
Automatic Internet Suspension Software — Guided pilot
Guided pilot: Preview, queued jobs, approvals, result recording, and a mock-safe worker can be evaluated in a guided pilot. Live router/RADIUS mutation remains gated; automated suspension and restoration are not a shipped promise.
Open pageSolutionsCustomer Self-Service Foundations — Guided pilot
Guided pilot: Field-job lifecycle, serialized stock, basic tickets and subscriber portal flows have narrow synthetic-data proof and remain guided pilots. Physical installs and invite email delivery are unproven. The technician PWA, dispatch board, dedicated stock workspace and IPAM remain roadmap.
Open pageIntegrationsController Integration Planning
Guided pilot: External references, import preview/apply jobs, connector profiles, and sync-run records are foundations for a guided pilot. Live UISP and Splynx adapters still require implementation.
Open pageIntegrationsFreeRADIUS Foundations — Guided pilot
Guided pilot: signed Status-Server probing and opt-in SQL accounting import. CoA/Disconnect drivers have fake-transport proof only; live NAS mutation and full policy integration remain unqualified.
Open page