Fleet operations10 min
WISP Manager
Use customer, service, billing and live device context in one workspace.
Outcome
A service record connected to the correct customer, device and live state.
Before you start
- WISP Manager access
- A customer/service naming convention
- Connected fleet telemetry
Build the operational record
- 1Create or import the customer.
- 2Define the product before attaching a subscription.
- 3Link the service to the customer and managed device.
- 4Add billing state after the service relationship is correct.
- 5Keep durable files with the customer/company record.
Operational note: Customer, subscription and device are separate objects; an equipment swap should not rewrite billing history.
Use live fleet context
- 1Check that revenue, uptime and throughput have current timestamps.
- 2Use Managed device pulse to find stale endpoints.
- 3Open the linked device for topology or remote access.
- 4Return to the service record and document the outcome.
Operational note: An empty or disconnected collector means unknown, not zero.
Verify the result
The customer has the intended service.
The service points to the correct device.
Live fields have a current timestamp.
Replacing equipment preserves service history.
Common issues
Overview cards are empty or stale.
Likely cause
Collector is disconnected, no device is linked or the snapshot is old.
Fix
Check collector readiness, the device link and refresh after telemetry resumes.
Customer and device totals differ.
Likely cause
Not every device is billable, or a service is linked twice.
Fix
Reconcile subscriptions and device links separately; the totals need not be identical.
Continue with
Topology and access policySeparate the network you observe from the paths you intend to allow.Teams, accounts and auditGive each operator the smallest durable access they need and keep actions attributable.Common issues and fixesStart from the symptom, isolate the failing layer and verify recovery at the target.