AI agent · Energy & utilities · Match & reconcile
Meter reading disputes
The software gathers every reading behind a disputed bill, tests the usual explanations in order and drafts the correction when the data settles it. A site visit is booked only when the readings contradict each other, with the question the technician must answer.
Typical volumes for this process, not a client figure.
Each dispute investigated across billing and field systems.
Investigated automatically; the ones needing a visit are scheduled.
Where the time goes today
A customer writes, calls or fills in a web form: the bill is too high, the reading is wrong, here is a photo of the meter. A back-office analyst opens the billing system to see which reading was used and whether it was an actual read, an estimate, a customer submission or a smart meter reading. Then the meter data system for the history, the work management system for recent visits or meter exchanges, and, for a smart meter, the interval data.
The explanations repeat, but the path to them does not. An estimate built on an old consumption profile. Two digits transposed at a manual read. A meter exchanged without the old meter's final reading recorded. Day and night registers swapped on a two-rate meter. Crossed meters in a block of flats, where each customer is billed for a neighbour. Or genuine consumption: a leak, a new heater. Each needs a different fix, and finding which one applies takes four systems and a spreadsheet.
Backlogs build, customers chase, and some disputes become formal complaints with response times set by the applicable rules. To be safe, analysts often book a site visit by default, sending a technician to confirm what the data already showed.
How the agent works
- Read the disputeFrom the email, form, call note or photo, the agent extracts the account, the meter serial, the reading the customer gives and its date. When there is a photo, it reads the digits and checks that the serial on the meter matches the one on the account.
- Assemble the historyIt pulls billed readings with their type, meter exchange records, field visit notes and, where available, interval data. Everything is laid out on one timeline per meter.
- Test the explanationsThe customer's reading is compared with the billed reading and the history, testing known causes in a fixed order: estimate against actual, transposed digits, swapped registers, missing exchange reading, crossed meters, consumption consistent with the past. Each test records the readings it used.
- Draft the correctionWhere one explanation is supported by the data, the agent drafts the rebill with the corrected reading and the calculation. Corrections within your rules and value threshold are applied; the rest wait for approval.
- Schedule the visitWhere readings contradict each other and no data explains why, it books a field visit. The work order states what the technician must check, for example which meter serves which flat.
What stays with a person
A person approves rebills above your value threshold, decides on write-offs, and handles any dispute where a customer contests the outcome after a visit. Anything that suggests interference with the meter goes straight to your revenue protection team; the agent does not raise it with the customer.
Accounts carrying a vulnerability flag, a payment plan or a medical dependency are handled by trained staff under your policy, whatever the data shows. Replies that tell a customer their bill stands are reviewed before they go out, because that is where a dispute turns into a complaint.
What it reads, what it produces
| It reads | It produces |
|---|---|
| The customer's message, call notes and meter photo | An investigation note with the explanation and the readings behind it |
| Billing system readings and bills | A drafted rebill or corrected estimate, applied or waiting for approval |
| Meter data history and smart meter interval data | A field work order stating the question to answer on site |
| Work orders, field visit notes and meter exchange records | A draft customer reply and a dispute closure code |
| Account flags: vulnerability, payment plan, open complaint |
Controls that come with it
- A customer photo is used only when the serial in the photo matches the meter on the account.
- Before any rebill, the agent checks whether a later bill has already corrected the reading, so a credit is never applied twice.
- Value threshold: corrections above it wait for a person; below it, they are applied through the normal billing adjustment and can be reversed the same way.
- Vulnerability flags route the case to a person regardless of the explanation found.
- A weekly sample of closed disputes is re-checked by an analyst.
How you know it works
- Time from dispute received to resolution
- Share of disputes that needed a site visit, and share of visits that found something the data did not show
- Disputes reopened on the same account within six months
- Rebill accuracy on the weekly sample
Is your process ready?
- Written rules: estimation, rebilling and back-billing limits are documented, including how far back a correction may go.
- Systems: billing, meter data and work management expose readings and history, and your licences allow automated access.
- Cheap check: a reviewer confirms the explanation from two readings and a date.
- Volume: thousands of disputes a month repay the build; a few dozen may only need a better report.
- Same description: billing and field teams agree on what counts as a confirmed reading.
The five candidacy checks are explained, with an exam, in the free Module 01.
What goes wrong
- Incomplete meter exchange records, so the old meter's final reading is missing and the agent cannot close the gap without a rule for it.
- Customers in shared buildings photographing the wrong meter.
- Register numbering that differs between meter models, confusing day and night readings.
- Estimation profiles changed in billing without the agent's rules being updated.
Questions we get
Will it book more site visits or fewer?
It books a visit only when the readings on file contradict each other and none of the known explanations fits. Whether that means fewer visits than today depends on how often your analysts currently book one as a precaution. Measure the share of disputes with a visit, and the share of visits that found something the data did not, before and after go-live.
Does it work for meters without smart data?
Yes, with less evidence. For a manually read meter the agent relies on billed readings, the reading history, field visit notes and the customer's photo. Fewer explanations can be confirmed from data alone, so more cases end in a visit or a request for a dated photo. With interval data, gaps and sudden changes in consumption are much easier to establish.
What happens when it suspects the meter has been tampered with?
It stops. The case goes to the team that handles revenue protection, with the readings and dates that raised the concern, and the agent sends nothing to the customer. It also does not describe the case as tampering in any record the customer could see, because the evidence at that stage is a pattern, not a finding.
Who writes to the customer?
The agent drafts the reply from templates you approve, with the corrected figures where there is a correction. Replies that confirm a correction can go out automatically if your policy allows it. Replies that confirm the bill stands, or that concern a customer with a vulnerability flag, are reviewed by a person first.
Want this agent on your process?
Tell us about your version of this process — volumes, systems, what goes wrong. A person answers with an approach and a price, usually within two working days, or tells you it is the wrong project.