Email automation for utilities customer service: every email read, every request answered in one reply, and no customer cut off after they paid
A bilingual inbox turned into resolved cases, with no re-keying.
See one case, screen by screen ↓A utility's customer mailbox takes in well over a thousand emails and scanned letters a working day, in two languages. At Lumina Utilities it is about 1,500. Each one is read by a person, who works out what the customer wants, finds the account and premise, types the account number, request type, amounts and dates into the customer system, routes it to the right team and writes a reply. When a customer emails twice, or emails and calls, the case is keyed twice. At the summer move-out peak the backlog reached 4,820 unanswered emails and the reply time 3.1 working days, against a charter commitment of 2.
Two kinds of mail suffer most. About 14 % of emails ask for more than one thing — a move-out, a meter reading and a deposit refund in one message. The handler answers the part their team owns; the rest is forwarded, lost or answered days later, and the customer calls. And time-critical mail sits in the same queue as everything else: a payment proof sent the morning of a disconnection run, a power cut at a home with medical equipment, a report of sparking cables. Regulators penalise wrongful disconnection, so a proof that arrives at 07:31 has to be seen before the 14:00 run.
Estimated split for one email with three requests, in working days, by hand (three replies over about six working days) and with the solution (one reply the same morning).
Seven agents read, sort, match, write the case and draft every reply; one email with three requests becomes three threads and one answer. The case handler sends.
Tuesday 13 October 2026, 08:14. Sara Mendes is moving out of Apartment 1204, Crescent Tower B, Al Waha. She writes one email to Lumina Utilities with three requests and a photo of her water meter. Here is what happens next, screen by screen, in the working solution.
By 11:12, 1,512 emails and scanned letters have come in since 17:00 the evening before. The agents have sorted 1,441 into seven lanes — payment proof, bill query, move-out, meter reading, refund, outage and solar — and 71 are with a person. Inside each lane an email moves from Read to Drafted to With team to Answered. Sara's email is drawn as three coloured strands, one per request.
“1,206 answered · 214 split into threads · 0 fields typed by hand”
The mail reader reads Sara's 112-word email and her photo IMG_2219.jpg: meter W-7731402, register 04821 m³, taken 12 Oct 19:06. The account matcher finds account 2041773908 and premise 305118842 from her sender address and the account number in her signature. The case writer updates case CS-26-1013-0412 with 14 fields, each with its source. The priority watcher checks: not on a disconnection list, no safety words, no medical equipment.
Mail reader: never guesses a number it cannot read — it marks it unreadable.
Close the account on Thursday 15 October goes to account services and Lina Farouk. The water reading — 4,821 m³, not the 4,862 billed — goes to meter operations and Omar Siddiqui. The AED 2,000 deposit refund goes to billing and refunds and Priya Nair, and it waits: the refund depends on the corrected bill.
Refund thread: “waits for the meter reading”
At 09:02 Lina books the move-out as SR-55120481: the final electricity read comes from the smart meter at 23:59 on 15 October, and a water final read visit is set for 10:00–12:00. At 10:40 Omar accepts the photo: the serial matches the premise and the reading is 41 m³ below the estimate, inside the expected range (reading policy MR-2 §3.1). September is re-issued on the actual reading, a credit of AED 184.50.
“We have re-issued your September bill on the actual reading, which gives you a credit of AED 184.50.”
With the reading settled, Priya answers the third thread. Deposit AED 2,000.00, less the final bill estimate for 1–15 October of AED 641.20, plus the September credit of AED 184.50: AED 1,543.30, to the bank account on file ending 4417, within 5 working days of the final bill (charter §6.1). The thread joiner joins the three answers into one reply, in the order Sara asked.
Thread joiner: never sends a partial reply without the case handler.
The reply is in English, as Sara wrote, with every account fact underlined — the account number, 15 October, 23:59, 4,821 m³, AED 184.50, AED 1,543.30, the account ending 4417. Hovering a fact shows where it came from. Hana sends at 11:18. One email, one reply, the same morning — against three replies over about six working days before.
The reply can only be sent once all three threads are answered.
Fatima Al-Zahra writes in Arabic: her September bill is AED 1,148.90 against AED 612.30 in August, with no change in use. The reply drafter answers in Arabic from the meter data: an actual smart-meter reading of 2,940 kWh against 1,610 kWh in August, with the daily peak between 13:00 and 17:00 — usually air conditioning on the hottest days — and offers a technician to check the meter free of charge. An English version sits below for the handler.
Arabic and English templates are kept in step; facts are filled from the account, never typed.
Yousef Al-Hashimi emails in Arabic with a bank-transfer receipt for AED 1,276.40; he is on the 14:00 disconnection list. The priority watcher matches it to the payment posted 12 Oct 21:47 and requests a hold. Of 128 proofs today, 119 match a posted payment, 6 wait for the bank and 3 do not match and go to credit control. At 07:52 Elena Petrova reports no power and a father on home oxygen; the control room calls at 07:54.
Priority watcher: never cancels a disconnection or reconnects — credit control decides.
Mariam confirmed 64 holds at 09:40. Now she confirms the 55 more that are matched, and all 119 are held. The 55 come off the 14:00 run too: of the 312 accounts on the list, 193 are still to be cut. Unposted payments are held until 13:45, and the three proofs that do not match — a part payment, a payment to an old account, a payment from someone else's account — stay with her.
“If they paid this morning, I need to know before two.”
The same morning's mail, seen by the five people who own it — what their day looked like, and what it looks like now.
Seven agents read, sort, match, write the case and draft every reply; one email with three requests becomes three threads and one answer. The case handler sends.
Reads emails, attachments and scanned letters in Arabic and English, including meter photos and payment receipts — serials, registers, amounts, references and timestamps.
Classifies each request into one of 50 intents in seven lanes and splits an email with several requests into threads, each with its team, noting when one waits for another.
Finds the account and premise from the sender address, any account or premise number, the name, the address and the attachments, and merges a repeat into the open case for the same request.
Creates or updates the case in the customer system with the intent, lane, team and every extracted field, each with its source — no re-keying.
Drafts each reply in the customer's language from the approved template, filling every fact from the account, the meter data, the payment ledger or the team's answer, underlined with its source.
Tracks each thread of a split email and, when every thread is answered, joins the answers into one reply in the order the customer asked. Raises a thread open more than 1 working day to the supervisor.
Checks every email against today's disconnection list, the safety words and the medical-equipment list; matches payment proof to the ledger and requests a hold; alerts the control room on safety or medical risk.
Sends every money and disconnection reply; credit control confirms holds. The agents propose; a named person decides.
Ask about an email, a thread, a payment proof or a rule, in plain words. Every answer cites its source.
Why was Sara Mendes's email split three ways?
Her email makes three separate requests: close the account on 15 October, correct an estimated water reading, and refund her deposit. Each belongs to a different team — account services, meter operations, billing and refunds — so each became its own thread. The refund waited for the reading, because the corrected bill changes the amount. One reply goes once all three are answered.
Which payment proofs could still miss the 14:00 disconnection run?
Nine of 128 are not settled. Six are waiting for the bank to post the payment — their holds stand until 13:45. Three do not match: Layla Hassan paid AED 900.00 of AED 1,240.00 and asks for a plan; Mohammed Al-Amiri paid from another person's account; Tomás Herrera paid to his old account. Mariam Tahir has all three.
How was Sara's refund of AED 1,543.30 worked out?
Her deposit of AED 2,000.00, less the final bill estimate for 1–15 October of AED 641.20, plus the AED 184.50 credit from re-issuing September on her photo reading. The photo was accepted because the serial matches her premise and the reading is inside the expected range. It is paid within 5 working days of the final bill.
Show me Sara's reply in Arabic
The same facts are underlined in both languages — account 2041773908, 15 October, 4,821 m³, AED 184.50 and AED 1,543.30 — because both versions are filled from the account, not translated by hand.
13 screens from the working solution, on its sample data. Pick one to see it large.
What the agents may do on their own, what always needs a person, and the clocks they work to are settings — each change approved and saved as a new version.
| Setting | Default | Choose from |
|---|---|---|
| Send replies for intents on the auto-send list | On · 15 intents | On · Off — copy of bill, tariff questions, known-outage notices, reading receipts, solar bookings… |
| Confidence needed to send alone | 0.92 | Set by the supervisor — below it, the reply waits for the case handler |
| Never without a person | On, fixed | Money, disconnection, complaints and safety — cannot be switched off |
| Split emails with more than one request · join threads into one reply | On · On | On · Off — the reply waits until every thread is answered |
| Payment proof for an account on today's disconnection list | Request a hold | On · Off — credit control confirms; unposted payment holds lapse at 13:45 for the 14:00 run |
| Safety words or medical equipment | Control room within 5 minutes | Sparking, burning smell, exposed cable, oxygen, dialysis — the minutes are a number; the control room approves the safety words and the medical-equipment list |
| Reply clock · deposit refund clock | 2 · 5 working days | Working days from the charter; the refund clock runs from the final bill |
| Thread open longer than | 1 working day | Working days — then raised to the contact centre supervisor |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample mail · “target” = the design goal, measured in the pilot · “estimated” = our estimate: 378,000 mails a year × 14.2 % with more than one request × 60 % leading to a follow-up call (assumption, to be measured in the pilot) × $9.54 a call ≈ $307K; the working-day split is also our estimate · “typical” = published figures (E Source: $9.54 average utility cost per call; Ontario Energy Board penalty and payments after wrongly calculated disconnection notices, reported by SooToday). Regulatory context: Essential Services Commission Victoria, Customer K and Simply Energy, s.40B Electricity Industry Act 2000 (2020). Lumina Utilities, the people, customers, accounts and records named on this page are fictional — characters and sample data in the working solution.
Software that reads every customer email and scanned letter a utility receives, works out what the customer is asking for, writes the case in the customer system and drafts the reply. Customer Email Automation does this with seven agents, in Arabic and English, and a case handler sends, edits or reroutes each reply.
The mail reader reads the email and its attachments, the request splitter sorts each request into one of 50 intents in seven lanes, and the account matcher finds the account and premise. The case writer writes the case with every field and its source, and the reply drafter drafts the reply from your templates, with each account fact underlined to where it came from.
Yes. An email with several requests is split into threads, one per team, and a thread can wait for another — a refund waits for a corrected bill. The thread joiner joins the answers into one reply only when every thread is answered. On the sample morning, 214 emails were split and no request was dropped.
The priority watcher checks every email against today's disconnection list. A payment proof jumps the queue, is matched to the posted payment in the ledger, and a hold is requested; the collections officer confirms it. Proofs that do not match go to credit control, and unposted payments are held until 13:45 for a 14:00 run.
Yes. Replies go back in the language the customer wrote in, from Arabic and English templates kept in step. The facts in both versions are filled from the account, not translated by hand. On the sample morning the mix was 58 % English and 42 % Arabic.
Only for the intents on the auto-send list — 15 on the sample, such as a copy of a bill, a tariff question or a known-outage notice — and only above the confidence the supervisor sets, 0.92 on the sample. Anything about money, disconnection, complaints or safety is always sent by a person; that rule cannot be switched off.
Yes. The case handler sends, edits or reroutes every reply that is not on the auto-send list, each team answers its own thread, credit control confirms every disconnection hold, and the contact centre supervisor approves changes to templates and the auto-send list. The agents never close a case, change a balance or cancel a disconnection.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your intents, reply templates, customer service charter, procedures and a sample of past customer mail — and it goes live once every quality gate has passed. We will walk you through it on your own mail first.
Every complaint investigated, answered and closed inside the clock.
1-min demoContact Center Agent AssistCited answers while the customer is still on the line.
1-min demoMove-In Move-Out ProcessingEvery final bill on a real meter read, and the deposit back in 2 days, not 3 weeks.
1-min demoWe'll run Customer Email Automation on a sample of your own customer mail, in the languages your customers write in.