How Auto-Activation & Auto-Suspension Works: Stop Chasing Customers for Payment

The Monthly Ritual Every ISP Owner Knows Too Well

Bill due date passes. A customer hasn't paid. Someone on your team has to notice, look up their username, log into the RADIUS panel or router, and manually disconnect them. A few days later they pay — now someone has to notice that, and manually turn them back on.

Multiply this across 300, 500, or 1,000 subscribers and it becomes a full-time job for someone on your team — a job that exists purely because two systems (your billing software and your network) aren't talking to each other.

Auto-activation and auto-suspension solve exactly this by connecting your billing system directly to your RADIUS server, so payment status and network access stay in sync automatically, in real time.

What Auto-Activation & Auto-Suspension Actually Mean

• Auto-activation: The moment a customer's payment is confirmed, their internet connection is automatically enabled — no staff action required.
• Auto-suspension: The moment a customer's plan expires without payment (after any grace period you've set), their internet connection is automatically disabled — again, with no staff action required.

Both directions of this automation rely on the same thing: your billing software and your RADIUS server (H8, IPACCT, Jaze, OneRadius, or another) exchanging a signal the instant something changes.

How It Actually Works, Step by Step

Step 1: Payment Event Happens

A customer pays via UPI, card, net banking, or cash collected by a field agent. This gets recorded in your billing software the moment it happens — not at end of day, not manually entered later.

Step 2: Billing Software Updates Account Status

The billing platform marks that subscriber's account as "paid" or "active" and calculates their new plan validity date.

Step 3: A Signal Is Sent to the RADIUS Server

This is the technical core of the whole system. RADIUS servers support a mechanism called Change of Authorization (CoA) and Disconnect-Request messages (defined in RFC 5176). In simple terms:

• A CoA message tells the RADIUS server to re-authorize an existing session immediately — for example, upgrading a suspended account back to full access without the customer needing to reconnect.
• A Disconnect-Request tells the RADIUS server to end a session right now — used for suspension when a plan expires.

Your billing software sends these signals automatically to whichever RADIUS platform you run, using that platform's API or integration protocol.

Step 4: The Network Responds Within Seconds

The RADIUS server relays the instruction to the NAS (Network Access Server — your router/BRAS/OLT), which either restores or cuts the customer's session. In most setups this happens within 5–30 seconds of the payment or expiry event.

Step 5: The Customer Is Notified

A well-set-up system also fires an automated SMS or WhatsApp message confirming activation, or warning about upcoming/actual suspension — so the customer isn't left guessing why their internet stopped.

What Happens Without Automation (The Real Cost)

Manual activation/suspension isn't just inconvenient — it directly costs ISPs money and goodwill:

• Revenue leakage: Customers who should have been suspended keep using free internet for days because nobody noticed the expiry.
• Delayed reactivation: A customer pays at 8 PM but doesn't get reconnected until the next morning when staff logs in — leading to complaints and refund requests.
• Staff time drain: Someone spends hours every day cross-checking payment lists against active connections.
• Human error: Wrong username disconnected, or a paying customer accidentally cut off — both generate support tickets and frustration.

What You Need for This to Work

• A compatible RADIUS server: H8, IPACCT, Jaze, OneRadius, or another platform that supports CoA/Disconnect messaging
• Billing software that integrates with it: The billing platform needs to actively send these signals, not just track payments internally
• A correctly configured NAS/router: Your access hardware needs to accept and act on CoA/Disconnect requests from the RADIUS server
• Defined business rules: Grace period length, partial-payment handling, and reactivation logic all need to be configured up front

Handling the Edge Cases

Grace Periods

Most ISPs don't suspend the second a bill is due — a 1-3 day grace period is common. Good automation lets you configure this per plan or per customer, so loyal long-term customers can get a slightly longer buffer than new sign-ups.

Partial Payments

If a customer pays only part of their bill, you can configure whether that triggers full activation, a reduced-speed "fair use" mode, or no change until the balance clears.

Prepaid vs. Postpaid Models

Prepaid customers are suspended the moment their validity runs out. Postpaid customers are typically given a billing cycle plus grace period before suspension — automation needs to handle both models correctly based on how each customer is set up.

How BrightCRM Handles This

BrightCRM connects directly to your existing RADIUS server — H8, IPACCT, Jaze, or OneRadius — so you don't need to switch network platforms to get this automation. Once connected:

• Every payment (UPI, card, net banking, or field-collected cash entered by your agent) triggers instant activation
• Every expiry without payment triggers automatic suspension after your configured grace period
• Customers get automatic SMS/WhatsApp confirmation either way
• Your team gets a live dashboard instead of a manual checklist

Real-World Impact

Conclusion: Automation Here Pays for Itself Fastest

Of all the things an ISP can automate, activation and suspension usually delivers the fastest, most visible payoff — it directly plugs revenue leaks and removes one of the most repetitive, error-prone manual tasks in the business. If you're only going to automate one thing this year, this is the one.