
From the complaint about a bill to the correction, with the case already reconstructed
A disputed balancing bill, or a tariff still set for the previous account holder, means piecing the contract, readings and bills back together while the response deadlines run.
Where a billing complaint stalls today
The complaint arrives by email or at the counter and customer service records it in the CRM, but answering it takes the contract, the reading history and the bills issued, which sit in different systems and do not always agree. The case then goes to billing, which checks consumption and assesses whether a correction is needed, and sometimes it comes back because a piece of data is missing. Meanwhile the response times set by ARERA, the Italian regulator for energy, networks and the environment, are running, and when they are exceeded the customer is automatically due compensation.
The complaints handler issues the correction, with the figures already recalculated
As soon as the complaint enters the queue, the agent classifies it by reason and gathers the contract, readings and bills for the disputed period. If it finds an error, for example a tariff changed on a different date from the change of account holder, it prepares the proposed correction with the recalculated amount and the draft reply. The complaints handler checks it and decides whether to issue the correction, because it affects the customer, while the cases that call for judgement go to customer service without a draft.
- The complaint arrives, by email or at the counter
- The agent gathers the contract, readings and bills and ranks the queue by deadline
- If it finds an error, it prepares the correction and the reply
- The complaints handler decides the correction and sends the reply
Illustrative example
Data, modules and responsibilities for billing complaints
| Item | In this case |
|---|---|
| Data | In this caseComplaints in the CRM, contracts and changes of account holder, reading history, bills and credit notes |
| Modules | In this caseData Foundation, Agents, Workspace |
| Who decides | In this caseThe complaints handler on the correction and the reply; the head of customer service on the agent's rules |
| What we measure | In this caseResponse times against those set by ARERA, compensation paid for delays, handovers between customer service and billing and replies to correct, to be recorded before the project and after release |
| AI Act risk class | In this caseThe Annex III high-risk uses most common in our industries concern credit to individuals, life and health premiums and employment, and the case touches none of them; we agree the class with risk and compliance when the project starts. If an assistant replies to the customer, the customer must know they are talking to an AI system |
| Where to start | In this caseWith Deployment, when the person accountable for customer service has already chosen this process and the starting times can be read in the CRM |
With unreliable readings, it is better to fix the data first
If readings arrive late from the distributor, or two systems give different consumption for the same supply point, the agent would build corrections on the wrong numbers. In that case the first job is on the data, with Data Foundation, and assisted correction comes later. The same applies when nobody owns the process between customer service and billing, because the agent's rules would be left without an owner.
The case comes from the Energy & utilities page.
Let's reconstruct a closed complaint together
Starting from a complaint closed with a correction, we look with you at which data was missing and where the case waited.