Their pocket.
Your brand.
A self-service app the customer keeps on the home screen. Branded, multi-language, payment-aware — the kind of portal that pulls top-ups off your USSD codes and tickets off your call centre.
Every common request, self-served.
Same data model as your admin console, gated by JWT and tenant context. When a customer changes their plan, the back-office sees it immediately; when the back-office credits an account, the customer sees the new balance.
Branded subdomain
Lives at portal.your-isp.com — your logo, your accent colour, your transactional email and SMS templates. Customers never see ISPStack chrome.
Real-time account
Balance, current plan, usage this cycle, next-renewal date — all gated by the same tenant context as your admin console.
Top-up + plan changes
M-Pesa STK push, Airtel Money, card. Plan upgrades and downgrades with server-side proration; the new profile pushes to RADIUS within the second.
Tickets + speed tests
Open a ticket with screenshots, follow it in-thread, run an HTTP speed test that records to the account so the next agent does not have to ask.
PWA installable
Install prompt on Android and iOS. Service-worker caches the shell so a slow connection still renders the account screen.
EN / SW today
English and Swahili out of the box, with per-customer language preference that travels through to email and SMS templates.
Looks like your ISP, not like ours.
Logo, accent colour, subdomain, language — live preview as you edit. Per-tenant settings travel through to every template and every email signature.
Less call-centre. Faster payments. Quieter Sundays.
A composite of typical numbers we see in the first three months of operators rolling the portal out to their book.
Brand your customer portal this afternoon.
Most operators have their portal live at a custom subdomain within an afternoon of signup — logo, accent colour, language, all your tenant's.