Subscriber App — Pay, test and self-serve — without ever calling support.
The Subscriber App is the ISP brand in the customer pocket. Every routine subscriber interaction — pay the bill, change the plan, run a speed test, open a ticket, check on an outage — happens in the app instead of on the care line. Payments in Pakistan, MEA and Asia are the killer feature: JazzCash, EasyPaisa, Mastercard and Visa are wired in from day one via the Netxol collection layer, so operators do not have to sign separate merchant contracts with each processor before they can accept money. The AI Engine drafts the first response to common questions; when it cannot resolve, it hands the ticket to a human agent with full context attached. The app is white-labelled to the operator identity and ships to the App Store and Play Store under the operator brand.
- iOS
- Android
- Progressive Web App
Support, without the wait.
Common questions resolve on the first tap. Your care team only sees the ones that actually need a human.
Pay, plan and top-up
Every routine subscriber interaction about money — pay the current bill, change the plan, top up a prepaid balance, review the invoice history, dispute a specific line — happens inside the Subscriber App in seconds. JazzCash, EasyPaisa, Mastercard and Visa are wired in from day one via the Netxol collection layer; see the operational post on JazzCash and EasyPaisa collection at /blog/jazzcash-easypaisa-for-isps. Card-on-file recurring collection for postpaid subscribers uses 3DS 2 authentication with proper MIT flagging on subsequent charges — see the card-on-file post at /blog/card-on-file-for-pakistan-isps.
Honest speed and health
Speed tests inside the app run against your own edge, not a random public server — so the result reflects what the subscriber connection actually looks like from your network, not what the internet at large looks like from their device. When a subscriber opens a ticket about "slow internet", the diagnostic is already attached: last three speed test results, current ONT optical power, upstream link utilisation, and any recent alarms on the OLT card serving them. Care agents open the ticket already knowing the answer.
Outage transparency
When there is a real outage, subscribers see it in the app inside a minute — a clear notice with an estimated restoration time, drawn from live NMM state. When there is not, they do not sit on hold to find out. The outage transparency wins care-team hours: for large outages the call volume drops materially because subscribers can see what is happening; for false alarms subscribers stop calling because they can verify their own service is fine.
Pay, plan and top-up
Every routine subscriber interaction about money — pay the current bill, change the plan, top up a prepaid balance, review the invoice history, dispute a specific line — happens inside the Subscriber App in seconds. JazzCash, EasyPaisa, Mastercard and Visa are wired in from day one via the Netxol collection layer; see the operational post on JazzCash and EasyPaisa collection at /blog/jazzcash-easypaisa-for-isps. Card-on-file recurring collection for postpaid subscribers uses 3DS 2 authentication with proper MIT flagging on subsequent charges — see the card-on-file post at /blog/card-on-file-for-pakistan-isps.
- JazzCash, EasyPaisa, Mastercard, Visa built-in
- Card-on-file recurring collection (3DS 2)
- Netxol operates the aggregation layer
- Auto-reconciled to the invoice on the shared graph
Honest speed and health
Speed tests inside the app run against your own edge, not a random public server — so the result reflects what the subscriber connection actually looks like from your network, not what the internet at large looks like from their device. When a subscriber opens a ticket about "slow internet", the diagnostic is already attached: last three speed test results, current ONT optical power, upstream link utilisation, and any recent alarms on the OLT card serving them. Care agents open the ticket already knowing the answer.
- Speed test against operator edge
- Diagnostic auto-attached to every speed-related ticket
- ONT optical power in the diagnostic
- Serving-OLT alarm history visible
Outage transparency
When there is a real outage, subscribers see it in the app inside a minute — a clear notice with an estimated restoration time, drawn from live NMM state. When there is not, they do not sit on hold to find out. The outage transparency wins care-team hours: for large outages the call volume drops materially because subscribers can see what is happening; for false alarms subscribers stop calling because they can verify their own service is fine.
- Real-time outage notice from NMM state
- Estimated restoration time
- Reduces call volume during large outages
- Ends spurious calls during false alarms
Everything the Subscriber App carries.
A short reference of what a Standard-edition Core ships with. Advanced adds MDM-managed white-label bundles.
Chat with the AI first
The AI Engine handles the first response to common subscriber questions — "when is my next bill?", "why was I charged extra?", "how do I change plan?", "my speed is slow, what should I check?" — with citations back to the source records (invoice, session, plan). When the AI cannot resolve, or the subscriber explicitly asks for a human, the ticket is handed to a care agent with the full conversation history and the subscriber context attached. Care agents receive complete tickets, not fragments.
White-labelled to you
The Subscriber App ships to the App Store and Play Store under the operator brand, not under Netxol. Your name, your logo, your colour palette, your typographic identity. The white-label pipeline is properly engineered: an operator brand pack (logo, colours, app icons, splash) is applied at build time to a signed IPA and APK, which the operator submits under their own developer account. Support for multiple operator brands from a single Netxol Core cluster (MVNO parent + child brands) is native.
Secure by design
Biometric authentication (Face ID on iOS, biometric prompt on Android), TLS-pinned transport, no third-party trackers, no analytics SDKs leaking subscriber data. Customer data stays on your Core; only the transactions the subscriber initiates (payment, plan change, ticket) leave the appliance and only to the specific processor endpoint. PCI DSS scope for the operator is minimised because Netxol carries the merchant of record scope on aggregated payments — see the aggregation post at /blog/payment-aggregation-vs-direct-merchant.
Where this app takes you.
Questions we get on the first call.
Can we white-label the app to our brand?
Yes — logo, colours, app-store metadata, welcome copy and support links are all configurable. Advanced and Enterprise editions include the white-label build service.
How does payment work?
The app integrates with your existing payment gateway (Stripe, Adyen, local providers). NOS handles the billing state on the back end.
What can the AI actually do for subscribers?
Common questions — bills, plan changes, speed tests, outage checks — resolve without a human. The AI hands off to your care team with the full context attached when it can't.
How is the app distributed?
To your own App Store / Play Store accounts under your brand, or as a Progressive Web App on your domain. Both routes ship with every release.
Put NOS in your subscribers' pockets.
Both apps ship with every Core. Download the installers today, or configure a Core with the white-label service included.