Hotspot user lifecycle
Create and manage users with the package, duration and access context appropriate to the service.
Hotspot customers and vouchers can have a different access pattern from PPPoE subscribers, but finance, support and reporting still benefit from a unified operational view.
Evaluate this use case together with customer lifecycle, finance and network ownership—not as an isolated feature.
These are practical considerations for comparing software and designing your deployment.
Create and manage users with the package, duration and access context appropriate to the service.
Generate and manage voucher-based access for locations or customer types that need it.
Keep Hotspot revenue visible beside the rest of the ISP collection workflow.
See enough identity and service information to respond to access issues quickly.
Allow the right staff or partner roles to operate only within their assigned scope.
Avoid separate accounting silos when the same business runs PPPoE, Static IP and Hotspot services.
A payment can change service state. A support issue can depend on session or ONU context. A reseller collection belongs to a financial hierarchy. Sweet Billing is structured around those relationships.
A practical look at Hotspot billing, user lifecycle, vouchers, usage visibility, payment workflows and customer access for ISP and WiFi operators.
Read practical guide