Meter reading dispute
Customer sends a meter photo; the index is read by vision, the estimated bill fixed, big credits approved.
Meter reading dispute is an agent scenario in the Energy & Utilities sector running on the whatsapp, app, web channels. Trigger: Bill dispute with a meter photo via WhatsApp or the app. The Billing Dispute Supervisor coordinates 3 specialist agents (Vision Agent, Billing Agent, Operations Agent) across 4 systems (Billing / CIS (SAP IS-U), Meter Data Management, Regulation Vector Store (EPDK), WhatsApp Business API); of 9 steps, 1 write to systems and 2 are checks or approvals. Outcome: Wrong invoice cancelled, rebill issued, customer informed with an explanation. Approval rule: Credit / correction > 1,000 TL → billing team lead approval.
Meter reading dispute
- WhatsApp: "my bill is 2,840 TL, the meter shows less" + photo; customer verified
- Meter serial 3812-0091, index 48,213 kWh; serial matches, no tampering signs
- Last 12 readings pulled; billed reading 49,760 kWh was an estimate (code E)
- Difference 1,547 kWh · monthly average 310 kWh → estimate ran ~5 months ahead
- Regulation: estimated bills correctable within 12 months on a verified reading
- Rebill: 2,840 TL → 1,318 TL; difference 1,522 TL > 1,000 TL threshold
- Credit > 1,000 TL → billing team lead approved, note attached
- Invoice cancelled, rebill of 1,318 TL issued, field reading scheduled
- Customer sent the new bill and explanation, case closed with an audit trail
- ■completed
Simulation · derived from real agent definitions · every agent can be built by dialogue with the Autonomous Agent and validated with a test corpus
Bill dispute with a meter photo via WhatsApp or the app
Wrong invoice cancelled, rebill issued, customer informed with an explanation
Agents
Billing Dispute Supervisor
Decomposes the objective, delegates to agents, manages approval points, merges the result.
Vision Agent
Reads serial and index from the meter photo
read_meter_photocheck_photo_integrityBilling Agent
Computes the difference against history and regulation
get_reading_historyestimate_consumptionsearch_billing_rulesOperations Agent
Cancels, rebills and informs the customer
cancel_invoicecreate_rebillschedule_field_readingsend_whatsappSteps
| # | Kind | Agent | What happens | System | ms | tok |
|---|---|---|---|---|---|---|
| 01 | ingest | Billing Dispute Supervisor | WhatsApp: "my bill is 2,840 TL, the meter shows less" + photo; customer verified | — | 200 | — |
| 02 | reason | Vision Agent | Meter serial 3812-0091, index 48,213 kWh; serial matches, no tampering signs | — | 920 | 610 |
| 03 | tool | Billing Agent | Last 12 readings pulled; billed reading 49,760 kWh was an estimate (code E) | Meter Data Management | 420 | — |
| 04 | reason | Billing Agent | Difference 1,547 kWh · monthly average 310 kWh → estimate ran ~5 months ahead | — | 700 | 820 |
| 05 | retrieve | Billing Agent | Regulation: estimated bills correctable within 12 months on a verified reading | Regulation Vector Store (EPDK) | 380 | 360 |
| 06 | verify | Billing Agent | Rebill: 2,840 TL → 1,318 TL; difference 1,522 TL > 1,000 TL threshold | — | 460 | 300 |
| 07 | approval | Billing Dispute Supervisor | Credit > 1,000 TL → billing team lead approved, note attached | — | 2,600 | — |
| 08 | write | Operations Agent | Invoice cancelled, rebill of 1,318 TL issued, field reading scheduled | Billing / CIS (SAP IS-U) | 560 | — |
| 09 | notify | Operations Agent | Customer sent the new bill and explanation, case closed with an audit trail | WhatsApp Business API | 240 | — |
Utility customer assistant: bill, outage, consumption and instalments in one dialogue
The customer calls or writes; the high bill is explained, outage ETA given, meter data shown, an instalment plan set up.
Outage report handling
Reports are clustered by feeder, one OSS ticket is raised and everyone affected hears before the crew leaves.
Rooftop solar connection application
Application documents are read, transformer capacity and regulation checked, gaps reported the same day; the connection opinion belongs to the engineer.
Time to move from experimenting with AI to transforming with it.
In a 30-minute discovery session we take your 2–3 priority business problems, show a live demo of a similar scenario, and draft a roadmap that starts with the Value layer.
- Your 2–3 priority problems
- Live demo of a similar scenario
- Roadmap starting with value analysis