Connectivity businesses are billing businesses. When activation, plans, usage, and suspension do not line up, the very first invoice generates a complaint.
On connectivity, customers feel the bill more than the network. Activate, plan change, usage collect, bill, suspend/restore—if those do not line up, the first invoice brings complaints and support can only talk. We write the relation among user, SIM or line, plan, usage, and bill first. Where usage comes from (gateway, vendor platform, own collect), how delayed, which freeze day bills, whether a plan is immediate or next month, live in rules—not in a support script.
Suspend, restore, loss, transfer, and cancel are a state machine, not a few buttons. Debt suspend has a grace and a notice; restore matches a payment. Channel activations and own stores keeping separate books over-issue or sleep SIMs. Number, SIM, and device IMEI stock and activation state are one ledger. Discounts, grants, and caps have a compute order and a bill line the customer can see, or a dispute cannot be handled.
A bill can be rehearsed before bill day so a wrong rule is not found on the day. We preview amount from current plan and usage so ops can sample. Adjustments need approval, a trail, and a reflection on the next bill. Settlement with a vendor or upstream carrier uses a different definition than the retail bill—do not stretch one table.
KYC, transfer, loss and replace are a thicker state machine than the activate screen. SIM resources move between channel and store; over-issue and sleep must be blocked. Caps, off-peak packs, and roaming computed wrong explode as complaints on bill day. We keep retail bills and upstream settlement on separate definitions so support can point at a line instead of talking. Suspend notices arrive inside grace; restore matches payment so a paid line is not still dead.
Go-live walks a small batch of SIMs or one product through a full cycle, then volume. Collect and pay are tested on that cycle rhythm, not only the activate screen. Training is retail and billing. A connectivity system that works can activate, suspend, and show a bill line the customer understands—support does not paper over the system.
Bulk activation, plan binding, and effective dates are controlled in the system, with trial and billable periods separated.
Usage trends per SIM, alerts before overage, and policy-driven throttling or suspension.
Monthly reconciliation with upstream carriers, with customer bills checkable against upstream usage SIM by SIM.
Once volumes grow, nobody can say who is using which SIM
SIMs bind to customer, device, and project, and status changes are recorded.
Overage is discovered only on the invoice, which causes disputes
Usage thresholds alert both customer and sales, with overage handling agreed in advance.
Upstream bills do not match your own usage and you absorb the gap
Per-SIM reconciliation produces a difference list and tracks the dispute outcome.
SIM pools, number ranges, stock and allocation.
Bulk activation, plan binding, effective control.
Usage collection, threshold alerts, throttling and suspension.
Tariff rules, bill generation, invoicing.
Upstream reconciliation, difference lists, dispute tracking.
Customer records, fault tickets, service history.
Write activate, plan effective, usage freeze, bill, and suspend/restore rules. Split product line and channel scope for this phase.
Fix user, SIM stock, plan, and bill relations. Confirm collect delay, payments, and upstream settlement definitions.
Run activate through bill on a small SIM batch. Bill rehearsal, adjustment trails, and debt-suspend grace are acceptance items written first.
Walk a full cycle, then volume. Train retail and billing; customers can read the lines. Iterate next by plan and channel.
Tell us how the work happens today, where it breaks, and when you need it live. We will come back with a scope you can check and a phasing plan.