Begin with the customers you must never get wrong. A utility should train the team that owns its vulnerable customer register first, then certify the billing and debt advisors who approve the agent's drafts, then outage and field teams. Widen the agent only when no reviewer has missed a vulnerability flag and the agent is certified on your own cases.
Why does vulnerability come first?
Utilities supply essentials. Some customers depend on power for medical equipment; others are elderly, disabled, or in financial crisis. Most utilities keep a register of these customers and owe them extra care in billing, debt recovery and outages. An agent that drafts a debt letter or schedules a meter exchange must respect that register, and so must the person approving its draft.
If the team that owns the register is not trained first, nobody can write the agent's hold rules properly. They know which flags matter, which combinations signal crisis, and what must never happen automatically. Their knowledge becomes the agent's limits, and their judgement becomes the standard the reviewers are trained to.
What order should training follow?
- The vulnerability and priority services team. Defining hold rules; the reviewer path; owning the calibration cases on vulnerability.
- Customer operations and risk leadership. What each depth means, what the agent refuses, what the record shows.
- Billing and debt advisors. The reviewer path with a practicum during shadow: payment plans, back-bills, debt letters, account changes.
- Team leaders. Calibration, cover during surges, what happens if an agent's certificate lapses.
- Outage communications staff. How the agent drafts updates from network status records, and when a person must take over.
- Field planners, engineers and control room staff. The shared vocabulary. Safety decisions on site and in the control room stay with them.
What must utility reviewers learn?
Vulnerability signals. Not only the register flag, but the signs in a customer's message: mention of a medical device, a new baby, a bereavement, an inability to pay for heating. The agent should hold these, and reviewers must catch any it missed.
Billing evidence by class. A smart meter read from the utility's own system is sealed. A customer's photo of their meter is declared. An estimated read is neither, and a bill built on estimates needs care. A back-bill must stay within the utility's own limits, and reviewers must check the period covered.
Outage messaging. Updates to customers should draw on the network status record, not on social media reports, which are external. Reviewers must check that restoration times in a draft come from operations, not from the agent's guess.
What may the agent do, and what stays with a person?
| The agent may | Stays with a person |
|---|---|
| Read account, meter and register data (depth 1) | Any debt action against a customer on the register |
| Draft bills, payment plans, debt letters and replies (depth 2) | Back-bills outside the utility's limits |
| Set up standard payment plans within limits, once certified (depth 3) | Disconnection or prepayment meter decisions |
| Send outage updates from network status records (depth 3) | Field safety decisions and switching in the control room |
What should be proven before widening?
Before the agent sets up payment plans on its own, the utility should see three things: debt advisors' practicum decisions with no missed vulnerability flag; the agent certified at depth 3 on the utility's own past cases; and the vulnerability team's sign-off on the hold rules. In the EU, many energy and water providers are essential entities under NIS2, so the incident path for an agent fault should also be rehearsed before widening.
An example
Take a hypothetical water company. The priority services team of six defines hold rules and takes reviewer certification first. Forty debt and billing advisors follow while the agent drafts payment plan offers in shadow for four weeks; every draft for a customer with any flag is held. Outage communications staff train on status-based updates. After a review in late spring, the agent sets up standard payment plans for unflagged customers at depth 3.
Banks follow a related order with money movement at the centre, set out in how banks should train staff; universities, with the academic calendar at the centre, in how universities should train staff.
Where the Academy fits
Pryme Intelligence Academy sets module tests in the learner's own industry and role, so debt advisors are tested on held payment plans for utility customers. A business can make approval rights depend on a current certificate, depth by depth, which keeps uncertified staff away from debt decisions.
Questions people ask
Can a utility use agents before advisors are certified?
At depth 1 or 2, with every action sent by a person, yes. Keep anything touching debt at depth 2 until reviewers are certified.
Where can we find a ready schedule?
The AI agent training plan template for utilities sets out the weeks, avoiding winter peaks.
What do utilities get wrong?
Training billing before the vulnerability team. More in what utilities get wrong about AI agent training and the guide to training teams for AI agents.