Utility Call Center Scripts: 7 Scripts for the Calls That Eat Your Queue

Italy put numbers on this. ARERA's quality standards for energy seller call centres require a free line for at least 95 percent of opening hours, an average wait of no more than three minutes, and at least 85 percent of callers reaching an operator. Source: ARERA call centre quality standards.

Those are fair targets in any market. Every avoidable second on a bill query is borrowed from the caller sitting at position 40.

The bar for how the call feels is lower than you would guess. Ofgem research into consumer experiences of customer service standards found participants had low awareness of the Guaranteed Standards of Performance and low expectations of service, shaped by their experiences across many sectors.

Low expectations are an opening. A fast, clean, well scripted call still surprises people in energy and water.

Pull this from your ACD before you read on: what share of last month's inbound volume came from your top five call reasons? Above 60 percent and seven scripts will move your numbers more than any new tool.

The letter goes out on the 1st. The calls arrive on the 3rd. The caller does not want a tariff explainer. They want to know what they owe and whether it is a mistake.

Opener: "Thanks for calling, I have the account open. Before we go through the charges, is it the amount that is the concern, or how it was worked out?"

• Confirm identity, then read the two numbers that matter: last bill, this bill.
• Name the driver in one sentence: unit rate change, estimated read, longer billing period, or standing charge.
• Offer the fix on the call: an actual read, a recalculation, or an instalment plan.
• Close with the date the customer will next hear from you.

Handoff line: "I would rather get this right than guess. I am bringing in a colleague who can adjust the account now, and I will pass over everything we have covered so you do not repeat yourself."

Do not defend a price. Explain a number on a page.

Storm calls arrive in a wave and ask three things: do you know, when is it back, am I owed anything.

• Lead with the answer: "Yes, we know about it, your street is on the list."
• Give the current restoration estimate and when it was last updated.
• Offer an SMS or a callback the moment that estimate changes.
• Ask for address detail last, and only if the address is not already flagged.

Most teams ask for a postcode before saying whether the outage is known. Swapping those two steps cuts handle time on every storm call.

This is the script where after hours coverage matters most. Substations do not trip inside business hours.

Lowest value call in the queue, highest volume in the fortnight before a billing run.

Opener: "Happy to take that reading. Which meter, and what does the display show, left to right, ignoring anything after the decimal point?"

• Read the digits back before you save them.
• Challenge an implausible read on the call, not in an exception report a week later.
• Confirm the effect: "That read replaces the estimate and your next bill will use it."
• Mention the self service route once, without pushing it.

A meter read call should never need a human, and it should never need an eight step phone tree either.

Two accounts, two dates, and a caller standing in a hallway surrounded by boxes.

• Capture the move date, the closing read at the old address and the opening read at the new one.
• Say out loud who is liable up to which date. Ambiguity here becomes an arrears case in 60 days.
• Confirm the forwarding address for the final bill.
• Set the payment method on the new account before you end the call.

A large share of a mid market supplier's arrears book traces back to a tenancy change recorded loosely. Tighten this script and you shrink the workload of a team you do not even manage.

Day 5 is a service call. Treat it as a collections call and you damage a customer who simply forgot.

Opener: "Quick courtesy call about the bill dated the 1st, it is showing as unpaid. Did it reach you?"

• Ask about receipt before you ask about payment.
• Offer a payment link on the call, sent to the number you are speaking to.
• If they can pay now, take it. If not, agree a date and say what happens on that date.
• Log the reason. "Waiting on payday" and "disputes the amount" belong in different queues.

The goal on Day 5 is contact, not recovery. Recovery belongs to the Day 15 script.

A promise with no follow up is a wish. Kept promise rate is the number that decides whether your arrears book shrinks.

Opener: "You had said the 14th for the 82 euro balance and it has not landed. Has something changed, or shall I resend the link?"

• Quote the exact amount and the exact date they gave you. Specificity earns credibility.
• Give two paths only: pay now, or restructure inside policy.
• Never negotiate outside policy on the call. Escalate instead.
• Confirm the plan in writing the same day.

Call timing is regulated in some markets. In the US, CFPB guidance on debt collection calls describes a general prohibition on calls before 8am or after 9pm, and a presumption that more than seven calls in seven days about the same debt crosses the line. In Europe your cadence limits come from national law and your own policy, so check with your compliance team before you set a dialer schedule.

Every script above needs an exit. Disclosed vulnerability, a dispute, a bereavement, real anger, or a request outside policy: that call belongs to a person.

Handoff line: "I am bringing in a colleague who handles this directly. They will already have the details, so you will not need to start again."

• Put trigger phrases in the script, not in a supervisor's head: "I cannot afford", "I am unwell", "my husband passed away", "ombudsman", "complaint".
• Context travels with the call. No recaps.
• The receiving agent opens with a summary, not a question.

Get the handoff right and your hardest calls reach your best people. Get it wrong and your best people spend the morning reading back meter digits.

Read this as a queue plan. Anything with a fixed path and an out of hours spike goes first.

AutoNurture.AI answers inbound calls without a phone tree, identifies the customer, resolves on the first call, and sends payment links, status updates or callbacks. When intent or risk spikes it pulls a human in mid call.

AI and human agents share one dialer, one number and one call log, with live handoff in both directions plus supervisor whisper and barge. You can see how that works on one platform for AI and humans.

On the credit side it makes past due calls and SMS on cadence, negotiates payment plans inside your policy, sends tokenized payment links so no card data sits on the call, and writes back to your CRM per call. That work sits under utilities and B2C collections.

If your billing runs on SAP IS-U, powercloud, Schleupen or Salesforce Energy and Utilities Cloud, those connectors are listed on the integrations page, with a webhook and REST API for the rest. Data is EU hosted, GDPR ready, DPA on request.

Scripts and voices get A and B tested in the Workbench, with dial windows per market, retry logic and do not call rules enforced automatically. Automation takes the repeatable volume so your advisors and collectors get the calls that need judgement. There is a longer read in The Future of Voice AI in the Energy Sector.

Practical, not scary. Work through it once with your compliance team and it stops being a blocker.

• Lawful basis written down per script, including your basis for arrears contact.
• Recording notice in the opener, in the caller's language.
• Retention set per script rather than one blanket setting.
• Data residency confirmed and named in your DPA.
• An erasure path that reaches recordings and transcripts, not just CRM notes.
• Quiet hours and do not call lists enforced by the dialer, not by memory.
• Vulnerability flags that pull a call out of automation immediately.

None of this is legal advice. Take the list to your compliance team and let them mark it up.

1. Export last month's call reasons and rank them. Confirm your own top seven.
2. Listen to six real calls per reason and write down the opener your best agent already uses.
3. Draft each script to one page: opener, path, handoff line, logging rule.
4. Run the consent checklist across all seven.
5. Pilot with three agents for five days, tracking handle time and first call resolution per script.
6. Rewrite the two scripts that fought back hardest.
7. Roll out to the floor, then load the outage, meter read and Day 5 scripts into a voice worker for evenings and weekends.
8. Review abandonment and kept promise rate after 30 days.

Two weeks, no procurement cycle. The only real cost is the discipline to listen to real calls before you write.

Pick your two highest volume scripts and write them this week. Measure handle time and first call resolution before and after.

If you want to hear the same scripts run by a voice worker in Portuguese, German, Italian or English, book a demo. It is a 20 minute live call in your language, mapped to your queue.