Customer experience
Investigating a Disputed Usage Charge Without Blaming the Customer
By the Orvlin team · · 2 min read
Usage charge dispute process: what to decide
The customer says they never ran that many jobs. A defensive response about the meter being accurate misses the real possibilities: a retry bug, another workspace, an unclear billable definition or a genuine data error. Investigate the whole chain.
Separate measurement errors from contract misunderstandings and goodwill decisions. A valid technical quantity can still conflict with what sales promised. Keep the investigation record so repeated disputes reveal a systemic issue rather than isolated support tickets.
A concrete scenario
An account disputes 2,000 exports. The records show one integration looping every minute, but the offer prices completed files rather than attempts. Checking completion evidence is more useful than simply counting request logs.
A detail teams often miss
Never share raw payloads casually to prove a charge. Use account-scoped references, timestamps and quantities, and follow the appropriate access policy for deeper records. A dispute should not create a privacy incident.
Before you put this into production
- Confirm the account, period and contested item.
- Compare usage, completion and invoice records.
- Review the agreed charging definition.
- Document the outcome and any preventive action.
Frequently asked questions
- Should we credit every disputed charge immediately?
- Not automatically. Investigate promptly, distinguish errors from goodwill, and follow the commercial policy. Avoid promising a remedy before understanding the facts.