Hotspot or PPPoE: Choosing the Billing Workflow

WayaDesk / PPPoE and renewals

Choose an access method around the way customers connect and buy service. A walk-up customer using a phone and a household with installed equipment have different onboarding and support needs. The billing workflow should match that relationship.

Compare the customer journey

A Hotspot offer commonly centres on login and pass purchase. A persistent PPPoE subscriber has an ongoing account and an authentication path associated with the installed service. Both need accurate payment and entitlement handling, but the customer-facing steps and troubleshooting evidence differ.

Compare the required controls

List the limits your packages need rather than assuming they are interchangeable. LinkDesk’s supported local Hotspot vouchers can use documented data caps. The current release does not apply those caps as PPPoE quotas, and RADIUS PPPoE has a separate simultaneous-session limitation.

• Write the expected customer connection and renewal journey.
• Match required controls to the documented implementation.
• Test the chosen method using the actual customer equipment.

Consider staff workload

A busy counter issuing passes may need a straightforward cashier process. A home-internet operator may spend more time on renewals, credential support and scheduled package changes. Demonstrate the tasks your team performs most often before choosing the deployment path.

Mixed networks need separate acceptance

An operator can have different service types, but a successful Hotspot pilot does not validate the PPPoE path. Keep the evidence for each workflow distinct. That prevents a working demonstration in one area from hiding an unmet requirement elsewhere in the business.