When an OLT or PON is down, or work is planned, tell exactly the subscribers behind it in one broadcast from the dashboard. You choose who gets it and press send. Nothing sends by itself.
Who receives it
The audience comes from your RADIUS billing book. On the Notices page you pick it: an OLT, a PON under it, subscribers who are online or dark, a billing status, or a list you tick by hand. A number comes from the book, or from the phone number the survey recorded at the house when the book has none.
A family sharing one handset gets one message, not four. A shared ONU with several billing customers on it reaches every resident. If you run two billing panels on one network, a notice can be held to one of them, so it never reaches the other book's subscribers.
How the send works
Picking an OLT lists its customers with every box unticked. You arm the broadcast yourself, and the button says how many people it will reach. Change the OLT or the filter and it disarms again. Untick anyone you want left out. The cost is on the page before you press send.
One broadcast runs per org at a time, and a second attempt names the one already running. Cancel stops the rest and reports honest counts. Each org has a daily cap, and a refusal says where you stand against it. Every notice keeps its own record of who was messaged, and that record survives the customer or the device being deleted later.
What a subscriber sees
A WhatsApp message from HansaNet's business number carrying your text, as one paragraph, with no buttons on it. The preview on the page is exactly what will arrive.
Receipts come back on the same channel. Each recipient moves from sent to delivered to read, and the counts on the page never go backwards.
Where it starts
A down device's panel and the triage card link to a notice already scoped to that device. They are links, not triggers. A person picks the audience and presses the button, every time. Notices are owner-only, so workers never see the billing book's phone numbers.
What it costs
Rs 0.90 per message, where one message is one number reached. Only a message that was accepted is billed. A failed row bills nothing, and so does the unsent remainder of a cancelled broadcast. The day's messages are added to the bill when the day closes. Outage pages to your own staff are never charged. Full rates are on pricing.
What it does not do
- It never sends by itself. There is no automatic notice on an alarm, on a schedule or on a recovery.
- It puts no buttons on the message, so there is nothing for the subscriber to tap back.
- It cannot reach a subscriber whose record has no usable mobile number. Those people are left out rather than guessed at.
- A dashboard locked for an unpaid bill cannot send notices. Monitoring and staff alerts keep running.
- It is not for staff. Staff are paged by WhatsApp alerts, which never touch this path.
The book itself, and how customers are matched to ONUs, is on the RADIUS billing book. What confirms the outage in the first place is on outage detection.
Put a probe on your plant tonight.
One setup .exe on a Windows machine in the rack, or a .deb on Linux. Rs 3 per ONU a month, no plans, no caps.