Helpdesk software for energy and utility service teams

Why do generic helpdesks struggle in energy and utilities?

A generic helpdesk files work under a requester and a ticket. Utility work hangs on a premises, its meters and the circumstances of whoever lives there, and regulators set several of the clocks.

• Premises, not people. Tenants, landlords, executors and debt advisers all write in about one address and its meters, and without account and meter IDs as fields their threads never meet.
• Vulnerability reorders the queue. Ofgem's contact guidance expects suppliers to put first the customers who need immediate help, such as a prepayment customer who has run out of credit, and to make it easy for carers, social workers and advice agencies to contact them on a customer's behalf. First-in, first-out routing does the opposite.
• Some contacts cannot wait for Monday. Suppliers in Great Britain must run a round-the-clock service for customers who lose supply because of a meter fault, and must triage the cause and urgency when the customer gets in touch.
• Deadlines, not reply targets. Ofgem gives energy suppliers 8 weeks to fix a complaint before the Energy Ombudsman can step in, and water companies in England pay customers when complaints, account queries or payment arrangement requests miss the deadlines in the Guaranteed Standards Scheme. A first-response SLA tracks neither.
• Complaints are routine, not rare. Suppliers reported 936 complaints per 100,000 customer accounts in the second quarter of 2026, according to Ofgem's customer service data. Without a complaints queue they end up mixed into general billing work.

How should a utility set up its helpdesk inbox?

Build queues around urgency and training, each with its own SLA. Treat these targets as starting points to check against your regulator's rules.

Routing rules

• Fields. Store the account number, meter point IDs (MPAN and MPRN in Great Britain), payment type, vulnerability flag and complaint start date as custom fields, and use them as filters and columns in Inbox views.
• Keyword tags. A workflow tags messages containing "no gas", "no power", "no water", "smell", "oxygen", "can't afford" or "ombudsman" and sets the SLA before anyone opens them.
• Trained groups. Round-robin inside the payment support and complaints groups (Growth and up), never across the general pool.
• Side conversations. Ask metering operations or the debt team in Slack from inside the thread, and raise a Jira issue when one billing fault reaches many accounts.

What reply templates do utility service teams need?

Use templates where one careless phrase causes harm. Each names the next step and a date; have compliance review the wording.

Customer struggling to pay

Hi {first_name}, thank you for telling us, and you don't have to sort this out alone. We can set up a payment plan based on what you can afford, look at a short payment break, and check whether our hardship fund can help. Call us free on {free_number}, or reply with a time that suits you and {agent_name} will ring you by {callback_date}.

Complaint acknowledgment

Hi {first_name}, I'm sorry about {issue_summary}. I've logged this as a complaint on {complaint_date}, reference {complaint_ref}, and {owner_name} in our complaints team now owns it and will update you by {update_date}. If it isn't resolved within 8 weeks, or you're unhappy with our final response, you can ask the Energy Ombudsman to review it.

Account holder has died

Hi {first_name}, I'm so sorry for your loss, and there's no rush with any of this. We've paused bills and reminders on {address} for now. When you're ready, send a meter reading from around {date_of_death} if you have one, and the name of whoever is handling the estate, and {agent_name} will take it from there.

Back-bill after missed readings

Hi {first_name}, we haven't billed you accurately for energy used between {start_date} and {end_date} because {reason}, and we're sorry. Under the back-billing rules we can only charge for energy used in the last 12 months, so we've removed {removed_amount} and your bill is now {billed_amount}. You can spread it over {months} months, or call {agent_name} free on {free_number} to agree something else.

Extended outage update

Hi {first_name}, power is still off at {address} because of {cause}. Crews are on site and the current estimate to restore it is {restoration_time}; we'll text you if that changes. If anyone at home relies on powered medical equipment, reply MEDICAL and we'll call you straight away. If you see a fallen line, keep well away and call {emergency_number}.

How should a utility service team be structured and staffed?

Organize by skill, not channel:

• Account services for readings, moves, payments and account changes.
• Billing specialists for disputes, back-bills and credit balance refunds.
• Payment support trained to assess affordability and spot vulnerability, with authority to agree plans and hardship payments.
• Metering specialists who can read communication logs and book engineers.
• A complaints team that owns cases to resolution and prepares ombudsman or regulator files, plus a quality lead who reviews safety and vulnerability conversations weekly.

Hours and peaks

• Winter. Heating drives usage, bills and payment difficulty. Ofgem's retail market data notes that direct debit credit balances build in summer and get spent in the colder months, so "why has my direct debit gone up?" arrives with autumn payment reviews.
• Price changes. Ofgem sets the price cap every 3 months, and each change brings letters, payment reviews and a wave of questions.
• Storms, heat and wildfire season. US electricity customers averaged about five and a half hours of interruptions in 2022, per the EIA, mostly from major events. California's CPUC sets notification rules for Public Safety Power Shutoffs.
• Supplier failures. When a GB supplier fails, Ofgem picks a supplier of last resort, which can take up to 14 days. The receiving team then fields questions about credit balances, opening readings and deemed contracts.

Ofgem may ask a supplier with poor service to justify its hours if it is not open for a meaningful time outside 9:00 to 17:00 on weekdays, such as 2 extra hours a day or 7 across the weekend.

Where does AI help a utility service team?

AI takes the lookups and the long threads; people keep affordability, complaints and safety.

• Drafts with sources. Copilot drafts replies that cite the tariff document, price change letter or Knowledge article behind them, so an agent can check before sending. Teams using it on every conversation see a 2.4× faster median reply (Aftersales' own figure).
• Summaries. A billing dispute can run for months across calls, emails and letters. Ofgem's ethical AI guidance names case history summaries as a use that saves agents time, and warns that inaccurate output could lead to unfair treatment, so keep the sources visible.
• Translation in 31 languages, including right-to-left scripts, without a separate bilingual queue.
• Monitors on every conversation. Monitors review every conversation rather than a sample, catching a missed vulnerability signal or a reply that drifts into collection pressure. Aftersales customer Helio Energy recorded a 14-point rise in quality scores after switching from sampling to Monitors.
• Agent for the routine share. Readings, moves and balance questions can be resolved before they reach a person; see AI customer service for energy and utilities.

Which customer service metrics matter for energy and utilities?

Track the deadlines regulators watch, the contacts that point to billing or metering faults, and how fast vulnerable customers reach a person. Measure CSAT separately for AI and human replies.

Insights reports resolution rate, CSAT and cost per conversation. The Events API and CSV export come with every plan, and Scale adds Snowflake, BigQuery and Redshift sync for joining support data to billing data.

How do utilities switch helpdesk software?

Most utility service teams start from one of three setups.

• A billing platform as the hub. A utility operating system such as Kraken, or an older customer information system, holds the account and its contact history. Keep the platform as the record; Aftersales Inbox runs the conversations and posts notes back through the Aftersales API or webhooks (confirm specific connectors on a call).
• A contact center suite beside shared mailboxes. Calls live in one tool and emails in another. Merge them so a customer's call and follow-up email share one thread and one complaint clock.
• Salesforce, Zendesk or Freshdesk. Keep it and run Agent inside it, or move AI and people into one Aftersales inbox.

1. Export your macros and rewrite them in the style of the templates above.
2. Recreate queues and custom fields: account number, meter point IDs, payment type, vulnerability flag, complaint start date.
3. Carry open complaints across with their original start dates so no clock resets.
4. Set up phone numbers per brand, with recording consent and a free line for customers in payment difficulty.
5. Run both systems side by side for a week, then move the help center and chat widget last.

Migration usually takes an afternoon, and on Growth and Scale the Aftersales team does it alongside you. Growth costs $69 per seat a month on annual billing; full details are on the pricing page.

Frequently asked questions