Sign in Talk to us
Features

Built from how an ISP
actually works.

Not a generic billing tool with an ISP label on it. Every rule below exists because of something that goes wrong in a real operation.

The customer directory, showing customer IDs, names, phone numbers, market and status The support queue with SLA counters, complaint types and the agent each one is with The WhatsApp inbox, where a customer conversation sits beside that customer account
Every module below exists because something in a real operation goes wrong without it.
Billing WhatsApp Portal Complaints Network Stock Office Reports Security
Why these modules

Every module below untangles one knot - the ones your office ties every month

Each one exists because a question like these used to take a phone call, a notebook or a spreadsheet to answer.

Is his line cut off yet... How much wire is left... Which complaint is late... Who installed this modem? Which area makes money... Eleven modules, one database
Billing

One customer, many services, one bill

Internet, cable TV, IPTV, static IP, cloud storage and voice combine into a single invoice with one line each - because that is how a subscriber is actually sold to.

The problem: Separate bills per service mean separate chasing, separate receipts, and a customer who pays one and forgets the other.

The monthly run

Every active subscriber invoiced in one pass, capped and resumable. Press it twice and nobody is billed twice - the run is idempotent by design.

A rehearsal that cannot lie

The preview IS the real run, rolled back. It cannot promise a figure the run does not produce, because it is the same code.

One-offs that bill once

Wire, modems, installation and deposits each carry their own guard. Remove a line by mistake and the charge is released, not lost for ever.

Free and paid, side by side

Eighty metres laid with fifty as goodwill shows both lines. The customer sees what they were given as well as what they are paying for.

Bills that print properly

A4 PDF with your letterhead, the paying market's own account details, quantity times rate, and the balance at the top where the eye lands.

Overdue without thinking about it

Past-due invoices flagged nightly, customers marked overdue, and returned to active the moment they settle. Deliberate states are never overwritten.

The invoice list - period, total, what is still owed, and the status of each one
One line per bill, with what is still owed on it - not a figure you add up yourself.
WhatsApp

The channel they already read

On the official Cloud API with your own number - not a phone plugged into a laptop that dies when somebody reboots it.

The problem: Reminders sent by hand get skipped on the busy months, which are exactly the months recovery matters.

Twenty messages, sent for you

Bill ready, due soon, overdue, payment received, suspension, restoration, new connection and more - each with editable wording and timing.

Never twice

Every message is a row before it is sent, with a unique key per decision. A retry, a double cron or two overlapping runs still send one message.

Quiet hours delay, never drop

A suspension warning worked out at 11pm goes at 8am. Discarding it would be worse than sending it late.

A menu customers tap

Balance, due date, package, complaint - answered without staff, and it never quotes figures to a number it cannot match to an account.

A real shared inbox

Photos, voice notes, reactions and read receipts, with the customer's balance and open complaints beside the thread.

A bill attached and a Pay button

Sent as an approved template outside the 24-hour window and as a normal message inside it - chosen at send time, not guessed when queued.

The automation screen, where each of the twenty messages is worded and timed
Each of the twenty messages, in your words and on your timing.
Customer portal

Your brand, your address, your subscribers

Served at your own hostname in your own colours. There is no mention of us anywhere on it.

The problem: An office that answers "what do I owe" fifty times a day is an office not doing anything else.

Sign in by WhatsApp code

No password for a subscriber to forget, and no password for your staff to reset all day.

Bills, receipts and balance

The oldest unsettled bill on the front page with a signed day count - negative when it is overdue.

Complaints with photos

A snapped drop wire photographed from site beats three messages describing it.

Add to home screen

Your icon, your colour, your name - generated per ISP, not a shared app store listing.

Pay, or prove you paid

Card checkout on your own merchant account, or upload the transfer screenshot for your staff to approve.

You decide what it offers

Every tab is a switch, and the server refuses a switched-off feature rather than merely hiding the button.

A subscriber own portal, showing this month bill and a way to pay it
What your subscriber sees: this month, what is due, and a way to settle it.
Complaints

A clock on every complaint

Five priorities, from a slow line to a whole area down, each with its own response and resolution target.

The problem: "We will send someone" with no record is how a complaint is still open a week later and nobody knows.

Targets written at the moment it is raised

Editing a target later cannot retroactively breach a ticket that was answered on time.

Routed to the right person

Rules in order, first match wins - or the least-loaded active lineman in that customer's own area.

Who to send, and where

The ticket already shows which box and which landmark feeds the complainant.

Speed claims, measured honestly

What the customer reports against what you sold - always labelled as their own figure, never presented as a measurement.

Rated by the customer

Only the subscriber rates it, and only after it is settled. A score staff can set is not a satisfaction score.

A knowledge base

Published articles your team and your portal both read.

The complaint queue, with the SLA clock running on each one
The clock is running on every complaint, and it is visible before it runs out.
Network register

Who loses internet if this is cut

Boxes, poles, cables, every fibre, joins, splitters and ports - and which subscriber hangs off which one.

The problem: The network lives in one lineman's head. When he is on leave, a cut takes all day to trace.

Impact, derived not guessed

Who can reach an exchange now, minus who could if this were removed. A customer with a second feed is not reported dark.

Tell them before they ring

Turn a fault into a message to exactly the people it affects, once per fault per customer.

Free strands by colour

A jointer with the closure open needs to know which two are free, not that four of six are used.

Your words, not ours

Box, pole, fibre, join. You can rename every type to match what your yard actually calls it.

Checked, and honestly labelled

Never checked and checked long ago are shown differently - painting both amber teaches people to ignore the colour.

No hardware needed

Wholly manual and deliberately so. Nothing to integrate, nothing to break when you change vendor.

The network register - boxes, poles and the cable between them
Your own boxes and poles, in the order your network actually runs.
Stock

A shelf of faulty modems is not stock

New, used, faulty and already-assigned counted separately, so the number you dispatch against is real.

The problem: One quantity column sends a lineman out with a returned dead unit.

Condition-aware counts

Available means new plus used. Defective is held and never offered; assigned is already promised.

Per-area shelves

One depot cannot spend another's stock, and a delivery received while viewing the wrong area cannot top up the wrong shelf.

Every movement says why

A reason is required, the person is recorded, and history is append-only. A miscount is corrected by recording the correction.

Over-dispatch refused

Taking 500 off a shelf of 5 is refused with the real count, not silently clamped to zero.

Suppliers and orders

Purchase orders through shipment stages, received into the destination area's shelf.

Sellable hardware

What you sell and for how much, kept apart from what is merely on the shelf.

Stock counted by condition - new, used, defective and already assigned
Counted by condition, so a shelf of faulty units never reads as stock.
Office & payroll

The staff side, in the same book

Staff records, the daily attendance register, leave, tasks and monthly payroll.

The problem: Salaries worked out in a spreadsheet are salaries nobody can reconcile three months later.

One register

Approved leave writes itself onto the attendance days it covers, and a day already marked present is not overwritten.

Payroll derived, never typed

Base plus bonus minus deductions, worked out server-side. Unpaid leave is the only leave that reaches it.

Paid runs are locked

A re-run refreshes what is pending and leaves paid rows exactly alone.

Tasks with real status

Completion is derived from the state, so the two cannot disagree.

The staff register, with the monthly payroll figure
The register payroll is worked out from, rather than a second list beside it.
Reports

Numbers that reconcile

Billed and collected are never mixed up, so a slow payer does not look like a bad month.

The problem: Revenue you can estimate. Profit per area, after what the equipment really cost, nobody can.

Growth that adds up

Opening plus new plus returning minus lost equals closing - and a month that does not reconcile says so on the page.

Resumed is not won back

A suspension lifted after three days is not a recovered customer, and the threshold is frozen onto the record.

Real cost of sales

Modem and wire costs frozen at the time of issue, so this year's price rise never rewrites last year's margin.

Deposits are not revenue

Money you are holding is excluded from earnings everywhere, so the margin is not flattered.

Per area, per package, per product

With the honest caveat that head-office spend belongs to no single area.

CSV out of everything

Written properly, so a name with a comma in it cannot break the file.

Revenue, growth and per-market figures
Billed and collected kept apart, per market and per product.
Security & backup

The things you think about once

On the day you need them, and not before.

The problem: Most ISP software has one shared login and no way to know who changed what.

Per-module, per-action permissions

Enforced on writes as well as reads, and staff can be locked to the areas they cover.

Two-factor and an IP allowlist

Optional, and built so a half-finished setup can never lock anybody out.

An audit trail

Identity, money and access changes recorded with who and when. Secrets never enter it.

Tiered backups

Fourteen daily, eight weekly, twelve monthly - because the corruption from March is noticed in June.

Verified, not assumed

Archives are read back and checked. One nobody has verified says so rather than showing a blank.

Restore one table

Somebody who deleted a price list wants the price list, not this morning's version of everything.

A record of every change anybody made, with who has been working and what each of them touched
Every change anybody made, with the person who made it and where they made it from.

See it with your own numbers

We will walk through it with your packages, your areas and your own bill - not a demo account.

No card, no contract to read first. A conversation.