Home Solutions ISP Subscriber Management Software — Fro...

ISP Subscriber Management Software — From KYC to Cross-Partner Transfer

Subscriber management software for ISPs: KYC verification, device/MAC tracking, cross-partner transfers, custom fields & 7 segmentation reports.

Request Free Demo View Pricing
Reviewed by the NowaCRM ISP operations team Last updated: May 18, 2026

Quick answer

ISP subscriber management is not a form with a save button — it's an engine that decides who gets internet access right now, based on billing state, KYC status, suspension flags, and an exact device fingerprint, and it has to agree with RADIUS, billing, and the UI at the same time. Scattered KYC folders, a partner's private spreadsheet of commission notes, and a support agent's WhatsApp thread about a replaced router are the real failure points most subscriber-management pitches skip. This page covers how NowaCRM's subscriber record actually works: the 9-state status machine shared by billing and RADIUS, document-backed KYC with a verifier and an expiry date, per-device MAC bindings that bust the RADIUS cache the moment they change, custom fields for data no schema anticipates, and a transfer engine that can hand a subscriber to a new partner — invoices, tickets, and IP allocations included — in one transaction.

01

The Subscriber Status Engine: 9 Persisted States, One Computed Overlay

Every subscriber carries one of nine persisted statuses: Pending, Active, Grace, Suspended, Paused, Cancellation Requested, Cancelled, Expired, Terminated. A tenth status, Disabled, is never written to the subscribers table — it's computed on the fly whenever the account-level access flag is off, regardless of what the billing cycle says, so an administrator can kill access instantly without touching the underlying billing state. Precedence is strict and shared by every module that reads it: Terminated and Cancelled are permanent lifecycle closures that outrank everything else; Suspended and Paused are administrative blockers; Pending and Cancellation Requested are provisioning blockers; and Active, Grace, and Expired are entitlement states a prepaid subscriber moves through automatically as their paid cycle runs out. This logic lives in one shared policy class, not duplicated across billing, the RADIUS auth path, and the admin UI — so a subscriber's effective status can never drift out of sync between what billing thinks, what RADIUS enforces, and what staff see on screen.

02

From Lead to Subscriber: Where One Record Ends and Another Begins

A prospect is never a row in the subscribers table. Before conversion, they move through 13 stages in the sales pipeline — New, Contact Attempt, Interested, Address Verification, Coverage Check, Site Survey, Survey Report, Plan Selection, Quotation, Payment, Installation Scheduling, Installation, Activation — tracked entirely on a separate Lead record. Only when a Lead reaches the Activation stage does the conversion service create an actual Subscriber record, and it refuses to do so without the Lead being in exactly that stage, without a phone number and name on file, and without checking the Lead isn't already linked to a different subscriber. This hard boundary is deliberate: reporting on leads (conversion rate, time-to-activation, lost reasons) and reporting on subscribers (churn, renewal, usage) never contaminate each other, because they're genuinely two tables with two lifecycle engines, not one table with a loose "stage" column trying to do both jobs.

03

KYC Document Verification — Audit-Ready, Not a Checkbox

Identity documents attach to the subscriber as individual records. Each has a document type — National ID, Tax ID, GST certificate, Voter ID, Passport, Driver's License, Address Proof, Photo ID, Customer Agreement, or a custom type — built as country-agnostic canonical keys, with older region-specific values (Aadhaar, PAN) mapped automatically to their canonical equivalent for backward compatibility rather than hard-coded to one country's ID system. Each document carries file metadata, an optional expiry date, and a full verification trail: who verified it, when, and a rejection reason if it was sent back. KYC status itself sits one level up on the subscriber's profile — Pending, Submitted, Verified, or Rejected — independent of any single document's state. A dedicated KYC compliance report rolls this up per tenant or partner: total subscribers, verified count, pending count, rejected count — so a compliance audit is a report you run, not a spreadsheet you rebuild from scratch.

04

Per-Device MAC Binding Tied to Live RADIUS

Every device a subscriber connects with can be registered as a MAC binding — not a free-text note, but a normalized record: the address is stripped of separators, uppercased, and reformatted to AA:BB:CC:DD:EE:FF automatically regardless of how it was typed in, with an optional label, a primary-device flag, and a vendor name resolved from the MAC's OUI. The moment a binding is saved or deleted, NowaCRM busts the RADIUS authentication cache for that specific subscriber, so a new router added in the UI is enforceable on the very next PPPoE or DHCP authentication attempt — no manual cache flush, no waiting for a nightly sync. And when a subscriber is deleted, their reserved MAC addresses are automatically released rather than staying locked forever, so a churned customer's old router hardware doesn't block the next customer who happens to buy the same model.

05

Custom Fields for Data No Schema Anticipates

Every ISP has at least one piece of subscriber data that doesn't fit a standard CRM form — a housing-society block and flat number, a GPON ONU serial logged outside the asset system, a local franchise reference code, a building access code. NowaCRM's subscriber custom fields are open key-value pairs — field name, value, and type — attached per subscriber, with a sort order for display and an audit trail of who created each entry. No migration, no support ticket to your SaaS vendor to add a column: the field exists the moment your team needs it.

06

Moving a Subscriber Between Partners Without Losing History

Reassigning a subscriber from one local partner or cable operator to another is a single database transaction that updates ownership across every table that references that subscriber — more than two dozen in total — instead of a manual re-entry that quietly orphans their history. Guards prevent transferring a deleted subscriber or one in a conflicting lifecycle state.

Data Tables Touched What Happens on Transfer
Billing invoices, payments, billing_schedules, charges Reassigned to the new partner, full history intact
Commission partner_commission_ledgers Old partner keeps entries already earned; new partner starts fresh
Network cpe_devices, ipv4_allocations, ipv6_delegations, radius_daily_usage Device and IP history stays attached to the subscriber
Support tickets, subscriber_notes, subscriber_documents Full ticket and KYC history moves with the subscriber
Identity subscriber_mac_bindings, subscriber_profiles, subscriber_custom_fields Device bindings and profile data transfer as one unit
07

Addons, Top-Ups & Speed Boosters — Independent of the Base Plan

Not every change to a subscriber's service should mean editing their plan assignment. A subscriber addon (a static IP, an OTT bundle, an extra access point) attaches to the subscriber with its own status lifecycle, separate from the base plan. A top-up is a one-off data or day-count addition for a subscriber who's run out mid-cycle. A speed booster is a temporary bandwidth upgrade — a festival weekend, a work-from-home request — that reverts automatically without anyone touching the underlying plan or billing cycle. All three live on the subscriber record as first-class, independently-tracked entities, not workarounds bolted onto the plan table.

08

Subscribers Can Reset Their Own WiFi — Backed by Live TR-069

The subscriber self-service portal includes a WiFi management screen wired directly to NowaCRM's ACS layer: it pulls the subscriber's CPE devices that are actually registered with the ACS, not just any router on file, and lets the subscriber view and change their own SSID and password. A password-reset request that used to mean a support ticket and a technician visit — or at minimum a phone call talking someone through a router's admin page — becomes a self-service action that pushes the change over TR-069 the same way an admin-triggered config push would. This is a direct line from the subscriber portal into the ACS/CPE provisioning layer, distinct from the portal's billing and usage features.

09

Bulk Import & Segmentation Reporting, Not Spreadsheet Exports

Onboarding an existing base — a migration from another platform, or a batch of society residents signed up offline — runs through a dedicated bulk import service built for subscriber data, plus a second import path purpose-built for backfilling expiry dates during a migration. On the reporting side, segmentation isn't one generic subscriber list with filters bolted on: there are seven dedicated reports — KYC compliance, payment due/aging, wallet ledger, status breakdown, activity, partner-wise distribution, and zone-wise distribution — each its own query and its own view, so an ops team segments by compliance state, aging bucket, partner, or geography without exporting the whole table and filtering it in Excel every month.

FAQ

Frequently Asked Questions

How many subscriber statuses does NowaCRM track?

Nine persisted statuses — Pending, Active, Grace, Suspended, Paused, Cancellation Requested, Cancelled, Expired, Terminated — plus a tenth, Disabled, that's computed from the account access flag and never stored directly. Termination and cancellation always take precedence over every other state.

How does a lead actually become a subscriber?

Through a 13-stage sales pipeline (New through Activation) tracked entirely on a separate Lead record. Conversion only happens when a Lead reaches the Activation stage, has a name and phone number, and isn't already linked to another subscriber — leads and subscribers are two different tables with two different lifecycle engines.

How is KYC verified, and can I prove it later in an audit?

Each identity document is its own record with a type, expiry date, and a verification trail — who verified it, when, and why it was rejected if it was. A separate KYC status (Pending/Submitted/Verified/Rejected) sits on the subscriber profile, and a dedicated KYC report gives verified/pending/rejected counts per tenant or partner on demand.

What happens to a subscriber's MAC-bound devices if they cancel?

Their reserved MAC addresses are automatically released rather than staying locked forever, so another subscriber who buys the same router model later isn't blocked by a churned customer's old hardware. Any live MAC binding change also busts the RADIUS auth cache for that subscriber immediately.

If I move a subscriber to a different partner, do they lose their billing and ticket history?

No. The transfer runs as one database transaction across every table that references the subscriber — invoices, payments, commission ledgers, IP allocations, tickets, documents, notes, MAC bindings — so the new partner inherits full history instead of the subscriber becoming an orphaned duplicate.

Can I track subscriber data that isn't in the standard form?

Yes, through custom fields — open key/value pairs per subscriber with a type and a creator audit trail. No schema migration or vendor support ticket required to add a new operator-specific attribute.

Can subscribers manage their own WiFi without calling support?

Yes, for devices registered with the ACS. The self-service portal includes a WiFi screen wired to the TR-069 layer, so subscribers can view and change their own SSID/password directly — the change pushes to the CPE the same way an admin-triggered config update would.

Ready to Transform Your ISP Operations?

Join 200+ ISPs running on NOWA CRM. Schedule a free demo and see it in action.