Subscriber portal
Most calls to an ISP office are four questions: how much do I owe, how do I pay, when does my line expire, and why is it slow. The portal answers all four in your own branding, on the phone the subscriber already has in their hand.
What a subscriber can do
This month's invoice, what is still owed, and every payment they have made — with dates, not from memory.
bKash, Nagad or SSLCommerz from the same screen. The payment settles the invoice and the line comes back on its own.
Only if you allow it. When you do, the change is priced for the days involved rather than argued about on the phone.
A complaint opens a ticket with a number, so "I called last week" becomes something both sides can look up.
Maintenance windows, a price change, a festival offer — pushed to the app and kept on the notifications screen.
For networks selling Wi-Fi time as well as home lines, the same login buys the next pass.
Getting in
Real phone numbers first
A subscriber imported from a router carries their username in the phone column until you fill it in, and the portal's first login checks the phone on file. Finish the CSV step on the billing page before you tell subscribers the portal exists.
Your name on it
Hand out a Play Store link or the APK itself, or let them use it as a web app — the same portal either way.
A due reminder that arrives without an SMS charge, and a notice that reaches everyone at once.
Your name, logo, banner and login photography — set from the panel, no rebuild and nobody else's name on the screen.
Questions
It is built for the connections it is actually opened on — often a phone with one bar, sometimes a line that has already been cut for non-payment. The screens are light and the sign-in path is short.
Only if you switch it on. Left off, they can see everything and pay, but the package stays the office's decision.
Yes — a subscriber can hold more than one connection, and paying for one renews that one rather than the first one found.
It is the opposite in practice: the calls it answers are the repetitive ones. What still reaches you arrives as a ticket with a subscriber, a package and a payment history already attached.
The rest of SKYNITY
Billing, the routers and the fibre share one set of records, so a payment, a package change or a failing ONU is the same fact everywhere it shows up.
Tell us how many subscribers, which routers and what packages, and the demo is set up the way you actually run.
Request a demoor email support@skynity.net
SKYNITY