Customer communications review for utilities: plain, compliant bills and letters in Arabic and English, with the calls each sentence caused
Plain, compliant bills and letters in Arabic and English.
See one case, screen by screen ↓Bills, disconnection notices and letters are written in the language of the tariff order: “any variance between estimated and actual consumption shall be reconciled upon the subsequent actual reading”. At Lumina Utilities the monthly electricity and water bill has a reading age of 13 against a plain-language target of 9. It carries 7 of the 12 items the Customer Rights Code requires, and its late-payment line — “suspension of supply without further notice” — contradicts the rule that supply is never stopped without 10 days’ written notice. The Arabic version asks for a meter reading “before the 15th”; the English gives no date at all.
Every one of those sentences turns into contacts. In Jul–Sep 2026 Voice of Customer linked 4,120 calls to wording in Lumina's 46 templates, 641 of them to the monthly bill alone. Yet a template change still goes round as a tracked-changes document by email to compliance and legal, readability is checked by hand if at all, nobody can say which paragraph caused last quarter's calls, and nobody measures whether the new wording reduced them.
Estimated split for one bill or notice change, in working days: by hand, a change goes round for about three weeks; with the solution the target is about two days, inside a 5-working-day review clock.
Six agents redline every paragraph and show the calls it caused; the writer accepts each edit, legal signs.
Lumina Utilities sends about 412,000 electricity and water bills a month, in English and Arabic. On Tuesday 13 Oct 2026 at 09:10, change request CR-2611 “Q4 bill refresh” opens for LU-BL-01 Monthly electricity and water bill, v4.2, due for the 1 Dec 2026 print run. Here is what happens next, screen by screen, in the working solution.
Leila is the writer on the bill. The review shows the live v4.1 wording redlined, the plain v4.2 rewrite beside it, and a call gutter on the left: 0 calls on the greeting, 147 on the amount due, 212 on the estimated reading. The scoreline reads reading age 13 against a target of 9, required items 7 of 12, 641 calls linked plus 101 emails and chats, and 10 findings open — 6 high, 2 medium, 2 low.
¶3 Estimated reading · “Drove 212 calls last quarter” · Missing · how to send your own reading · Rights Code §3.4
The template reader splits v4.2 into 8 paragraphs and pairs the Arabic twin. The plain-language reviewer scores reading age 13 in English and 14 in Arabic, with 15 terms from the word list. The required-content checker finds 7 of 12 items present, 4 missing and ¶7 contradicting §6.2. The call-driver linker searches 18,240 voices from 90 days and links 641 calls to 7 paragraphs; the rewrite writer drafts 7 rewrites in both languages.
Bilingual checker: “2 mismatches in the live wording · 0 in the rewrites”
In Call drivers, Voice of Customer challenges are joined to the words that cause them. CH-4F21 carries 268 calls in Jul–Sep: 212 land on ¶3 of the bill and 56 on the estimated-bill text message. The linker judges that words can fix it — the bill never says how to send a reading, or by when — and that the 38 photo readings that were never booked are a process cause for Billing operations.
In their words: “It says estimated. Estimated how? I sent a photo of my meter two weeks ago.”
The plain rewrite of ¶3 says the meter could not be read, that the estimate is based on use at the same time last year, and to send a reading in the Lumina app by 20 November 2026. Its reading age falls from 14 to 8 and it adds required item 5. Leila accepts it; the bill's reading age moves from 13 to 12 and its required items from 7 to 8.
“¶3 accepted · reading age 13 → 12 · required items 7 → 8”
Arabic and English sit side by side, paragraph by paragraph, with checks for numbers, dates, content, merge fields and plain tone. The live bill has 2 mismatches: in ¶3 the Arabic asks for a reading before the 15th while the English gives no date, and in ¶2 the Arabic leaves out the sentence on payments applied to the oldest balance. The v4.2 rewrites give one date, 20 November, in both.
Reading age 13 in English, 14 in Arabic · 6 merge fields, the same in both languages
¶7 says non-payment “may result in suspension of supply without further notice”, and never mentions payment plans. Its 81 calls include a customer whose father is on oxygen at home. The rewrite offers a payment plan in the app or on 800 586462 and says supply is never cut off without 10 days’ written notice. ¶8 adds the right to ask the Utilities Ombudsman Office to review a complaint and the Priority Care register; both go to Legal.
In their words: “Your bill says you can cut me off without telling me. My father is on oxygen at home.”
CH-9D02, “Planned-outage notice arrives after the outage starts”, carries 403 calls on the electricity interruption notice. The linker finds the wording clear: the notice goes out 24 hours before the work, and 31 % of notices in Q3 reached customers after the work had started. Mariam sent it to Network operations as a timing problem, with the calls as evidence, instead of rewriting a notice that was not the cause.
“Words cannot fix this. Owner: Network operations.”
With all 7 rewrites accepted, Leila sends CR-2611 for approval at reading age 8. Yusuf, the regulatory compliance officer, confirms 12 of 12 required items. Hannah Brooks, legal counsel, e-signs the wording of ¶7 Late payment and ¶8 Help and complaints in English and Arabic, with the meaning of her signature: “Approved as legally correct”.
“We will never cut off your supply without writing to you at least 10 days before.”
Farah releases LU-BL-01 v4.2 to the print run in 1 day, inside the 5-working-day review clock. The record holds every step, people and agents alike: the agents' review, each rewrite Leila accepted, Yusuf's confirmation, Hannah's signature and the release. The record exports with its findings, edits, signatures and versions.
“Released · LU-BL-01 v4.2 prints on 1 Dec 2026 · calls measured for 90 days”
Impact shows the proof from the last rewrite: the 10-day disconnection notice LU-NT-04 v3, released 14 Jul 2026, went from 312 to 198 calls a quarter, payment plans set up from it rose from 410 to 655, and complaints about it to the Utilities Ombudsman Office fell from 9 to 2. For CR-2611 the forecast is 418 calls a quarter against a target of 427 or fewer.
“Target: a third fewer · met” · these 5 challenges account for all 114 fewer calls
The same bill, seen by the five people who own it — what their month looked like, and what it looks like now.
Six agents redline every paragraph and show the calls it caused; the writer accepts each edit, legal signs.
Reads each bill, notice or letter template from the bill print system and splits it into paragraphs; marks every merge field, amount, date, phone number and named right, and pairs each English paragraph with its Arabic twin.
Scores reading age in English and Arabic, the longest sentence and the terms on the word list, and flags any amount shown without how it is made up — citing the style rule for every finding.
Loads the required items for the document type — 12 for a bill, 11 for a notice, 9 for a letter — and finds the sentence that meets each one, reports it missing, or reports wording that contradicts it, citing the Rights Code clause.
Matches Voice of Customer calls, emails and chats from the link window to the paragraph they quote or ask about, decides whether words can fix each challenge or the cause is a process, and names the owning team. After release it counts the template's calls for 90 days.
Drafts the plain rewrite of each flagged paragraph to the reading-age target, in English and Arabic together, using the word list and adding missing required content from the clause text.
Compares Arabic and English paragraph by paragraph — every number, date, phone number, right and merge field — reports content present in one language only, and checks the tone against the style guide.
Accepts each edit; compliance confirms, legal signs. The agents propose; a named person decides.
Ask in plain words — or say what to change. Every answer points to the challenge, the clause or the screen behind it.
Why is paragraph 3 driving so many calls?
¶3 is the estimated-reading paragraph. Voice of Customer links 212 calls and 41 emails and chats to it in Jul–Sep, under challenge CH-4F21. Customers ask what “reconciled upon the subsequent actual reading” means and how to send their own reading. The bill never says how, which is also a missing required item (Rights Code §3.4). The rewrite answers both at reading age 8.
Which templates still miss the right to escalate a complaint?
Item 11 (Rights Code §9.1) is missing from LU-BL-01 v4.1 and LU-NT-07. LU-BL-01 v4.2 adds it in ¶8 once you accept that rewrite; Hannah Brooks signs it. LU-NT-07, the water interruption notice, needs a change request.
Does the Arabic say the same as the English?
Not in the live bill. In ¶3 the Arabic asks for a reading “before the 15th” while the English gives no date, and in ¶2 the Arabic leaves out the sentence on payments applied to the oldest balance. The v4.2 rewrites give one date, 20 November, in both, and keep every merge field from the live wording.
Did the disconnection notice rewrite reduce calls?
Yes. LU-NT-04 v3 was released on 14 Jul 2026. Calls fell from 312 in Q2 to 198 in Q3, down 37 %, and payment plans set up from the notice rose from 410 to 655. The CR-2611 forecast takes a slightly cautious 35 % off each accepted paragraph.
13 screens from the working solution, on its sample data. Pick one to see it large.
The reading-age target, the word list, the call threshold, who signs what and how the agents work are settings, chosen by the communications team.
| Setting | Default | Choose from |
|---|---|---|
| Reading age target | 9 | Set from 7 to 12 · a paragraph above it is flagged, in English and Arabic |
| Longest sentence | 20 words | 15 words · 20 words · 25 words — longer sentences are split in the rewrite |
| Flag a paragraph for calls | 20 calls | 10 calls · 20 calls · 50 calls in the link window |
| Voice of Customer link window | 90 days | 30 days · 90 days · 180 days of calls, emails and chats |
| Wording that carries a right or a charge | Hannah Brooks | Hannah Brooks · Legal team — disconnection, payment, complaints and fees, by e-signature |
| Required content | Yusuf Al-Amiri | Yusuf Al-Amiri · Compliance team — confirms every required right is present and correct |
| Review clock | 5 working days | 5 working days · 10 working days, from opening to release |
| Send process causes to their owner | On | On · Off — when words cannot fix a challenge, it goes to the owning team in Voice of Customer |
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 data · “target” = the design goal, measured in the live solution · “estimated” = our arithmetic from the inputs shown: 4,120 calls a quarter linked to wording × 4 = 16,480 a year, × 35 % fewer, × AED 35 a call · “typical” = published figures (J.D. Power 2025 US Electric Utility Residential Customer Satisfaction Study, 499/1,000; E Source, $9.54 a call, ≈ AED 35). Context: CCW and EWON report billing as the top complaint driver; Ofgem's Standards of Conduct ask for plain, intelligible communication. Lumina Utilities, the Lumina Customer Rights Code, the Supply Regulations and the Utilities Ombudsman Office are fictional, and the people named on this page are characters in the working solution.
Software that reviews a utility's bills, notices, letters and text messages before they are sent: for plain words, for the customer rights they must carry, and for the calls their wording causes. Customer Communications Review adds six agents that redline each paragraph, draft a plain rewrite in English and Arabic and link it to Voice of Customer. People accept each edit and sign before release.
When a change request opens, the agents split the template into paragraphs, score reading age and jargon, check the required items, link the calls, emails and chats each paragraph caused, and draft a rewrite in both languages. The writer accepts, edits or rejects each rewrite; compliance confirms the rights, legal e-signs the wording that carries a right or a charge, and the head of customer communications releases it to the print run.
The call-driver linker searches the Voice of Customer calls, emails and chats in the link window — 90 days by default — for quotes of, or questions about, each paragraph, and attaches each voice to one paragraph only. In the demo it links 641 calls to 7 paragraphs of the monthly bill, 212 of them to the estimated-reading paragraph.
Yes. The required-content checker loads the required items for each document type — 12 for a bill, 11 for a notice, 9 for a letter — and reports each one present, missing or wrong, with the clause. In the demo it found the bill's late-payment line contradicting the 10-day written notice rule, and the Priority Care register for customers who rely on medical equipment missing.
Yes. The rewrite writer drafts both together, and the bilingual checker compares every number, date, phone number, right and merge field between them. In the demo it found the Arabic asking for a reading before the 15th while the English gave no date. It never approves a translation; it flags it for the writer.
The call-driver linker tells wording causes from process causes. A planned-outage notice that is clear but reaches customers after the work has started is a timing problem, so it goes to Network operations in Voice of Customer with its calls as evidence, instead of being rewritten.
Yes. The agents find and draft; a person accepts every edit. Merge fields, amounts and dates are locked in a rewrite, only Compliance may mark a required item not applicable, Legal e-signs rights and charges, and nothing is released without the Head of Customer Communications.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your templates, your customer rights code, your style guide and word list, and your Voice of Customer data — and it goes live once every quality gate has passed. We will walk you through it on one of your own templates first.
Every voice read, and each recurring problem named with an owner and a fix.
1-min demoClosed-Loop Feedback ManagementNo unhappy customer left without a call back, and every recovery measured.
1-min demoComplaint Root Cause AnalysisEach complaint trend proved with system data, owned, and fixed at the cause.
1-min demoWe'll run Customer Communications Review on one of your own bill or notice templates and last quarter's calls.