Case study · Broadband internet service provider
A CRM, billing portal and customer app for a broadband ISP
iNet Wireless runs its subscribers, plans and RADIUS in Jaze ISP Manager. We built the layer around it: an admin CRM, a franchise portal, a field-staff app and a customer app with online renewals, all reading and writing Jaze through one secure gateway.
- Client
- iNet Wireless
- Where
- Karur, Tamil Nadu
- Status
- In production
- Used by
- Office staff, NOC, finance, field engineers, franchise partners and subscribers
The problem
- Jaze handles subscriber accounts and billing well, but it has no tools for franchise commissions, field work, outages, network inventory, sales leads or customer self-service.
- iNet's network is split across 67 Jaze zones (main, franchise and cable-operator zones). Jaze can't filter on the server, so payment and reconciliation screens were slow, capped, and only showed one zone at a time.
- The brief was clear: don't replace Jaze. Put one control layer around it that staff, partners, engineers and subscribers can all use.
What we built
Gateway on top of Jaze
- A single Node.js gateway is the only system that talks to the Jaze API, with role and permission checks on every route
- Routing across all 67 zones, with a nightly rebuild of the zone-user index
- Hourly payment ledger and invoice cache, so reports no longer wait on Jaze
Admin CRM for the office
- Customer 360, subscribers, tickets with TAT tracking, invoices, payments, renewals and reconciliation
- Franchise management, leads, inventory, outage monitor, staff attendance and HR
- Broadcasts, vouchers, coupons, FUP templates and invoice PDFs
Apps for subscribers, partners and engineers
- Customer app and web portal: plan, data usage, invoices, online renewal through CCAvenue, tickets, speed test and add-on store
- Franchise partner portal, with one login per Jaze zone
- Field-staff app: attendance, tasks, tickets, subscriber lookup, cash collection with receipts, and lead capture
- WhatsApp OTP login, WhatsApp and push notifications, and AI triage of support tickets
In numbers
- 65 s → 3 s
- Load time of dashboard, reports and reconciliation after the payment cache went live
- 67
- Jaze zones brought into one admin view
- 2,152
- Payments visible across all zones in a 30-day check, against 36 in the main zone alone
- 1,000+
- Automated tests on the gateway
From the project's own test, deploy and status records.
Built with
Node.js, Express, TypeScript, PostgreSQL, React, Next.js, React Native, Jaze API, CCAvenue