The invoice that started a dispute
One of your business mobile customers has a salesperson who spent a week at a trade show abroad. The phone stayed on its home tariff, tethered a laptop and synced a camera roll. Nobody noticed until your monthly invoice went out with a line that was bigger than the rest of the account put together.
The customer's finance director phones. Why did nobody tell them? Your account manager says the network sends usage texts to the user. The user says they ignore texts from the network. The finance director asks for a credit, and you end up absorbing part of a charge the network has already billed you for.
The same pattern turns up at home too: a SIM in a router at a site office that quietly uses far more data than its bundle.
Why nobody sees it coming
- Usage data from the network or distributor arrives in batches, and often only the month-end file is looked at.
- Alerts from the network go to the handset user, not to the person who pays.
- Allowances, bolt-ons and roaming add-ons are set per user, so 'normal' is different for every line.
- Shared data pools across an account make it hard to see which user is using it.
- Your team is busy with orders and has no daily view of usage across all customers.
The information does exist before the bill. It just is not joined up with who should hear about it.
What bill shock costs a reseller
| After the event | Cost to you |
|---|---|
| Customer disputes the charge | Credit or write-off, time on the phone |
| Charge upheld | Relationship damaged at renewal |
| Router SIM overuse | Recurring overage nobody questions |
| No roaming add-on on travel lines | Avoidable charges every trip |
| Alerts only reach the user | Finance learns from the invoice |
There is also an opportunity lost. A customer who keeps going over their allowance needs a different tariff, and that is a conversation you would rather have before they complain.
The usage monitoring we build
- Usage is collected at the frequency your network or distributor provides, by file or API, and stored per line.
- Each line has its allowance and add-ons recorded, taken from your billing platform rather than set up twice.
- Rules are applied per customer: a percentage of allowance used, roaming activity on a line without a roaming add-on, or usage far above that line's own normal.
- When a rule fires, the nominated contact at the customer (usually whoever manages mobiles or pays the bill) gets an email or SMS in plain language, and your account manager gets the same alert with the account detail.
- Where your network allows it through the distributor, an agreed action can follow, such as adding a roaming bundle or applying a data bar, but only with the customer's standing permission.
- A monthly summary per customer shows which lines are consistently over or under their allowance, ready for a tariff review.
The customer chooses who hears and at what point. Some want every roaming alert. Others want only the unusual ones.
We keep the rules in a settings screen your account team can change per customer, because a haulage firm with drivers in Europe and a solicitors' office that never travels need very different thresholds. Everything that fires is logged, so if a charge is disputed later you can show exactly when the customer was told and who received it.
A month with alerts running
The travelling salesperson's line triggers a roaming alert on the first day abroad. The customer's office manager adds a travel bundle through your account manager, and the invoice holds no surprise. The router SIM is flagged in its first week of overuse and moved to a bigger data plan.
Your team moves from arguing about charges after the fact to recommending tariffs based on real usage, which is a far better conversation to have at renewal.
Recognise these?
- You regularly credit customers for roaming or data charges.
- Customers only see their usage when the invoice arrives.
- Usage files from the network are looked at once a month, if that.
- Some SIMs in routers or devices use far more than anyone expected.
- Tariff reviews happen at renewal, not when usage changes.