A customer opens a bill that is far higher than usual. Within a minute she has decided it is wrong, and she wants to speak to someone immediately. The queue is forty minutes because several thousand other people opened the same bill run this week.
Most of them have the same question, and most of that question has a published answer.
What customers ask
They usually ask how to submit a reading, where to find the meter number, why a bill is estimated, how the bill is calculated, why it is higher than last time, whether the reading was used, how to set up a payment plan, how to change a direct debit date, what the standing charge is and how to dispute a bill.
Separate procedural from account-specific
How to read a meter, where to submit it, what a standing charge is and how billing periods work are all publishable. What a specific customer owes and why is not, and needs authentication.
Example conversations
These scripts use information a provider might publish. Your answers should come from your own pages.
Customer: How do I send you a meter reading? Assistant: The meter page explains how to submit readings, including the online form and the app, and shows which digits to record for each meter type with photographs. It also gives the reading dates for your billing cycle so the reading is used on the next bill.
Customer: My bill is much higher than last month. Why? Assistant: The page explains what can change a bill, including estimated readings, seasonal usage and rate changes, and how to check which reading was used. To look at your specific bill you will need to sign in or speak to the team, and the page shows both routes with the opening hours.
Customer: I cannot pay this. Assistant: Please contact the team about that rather than leaving it, as the page explains the payment arrangements available and the support for customers in difficulty. It shows the direct number and the priority routes, including for customers on the priority services register.
Photographs of meters are the best content
Customers genuinely cannot tell which digits to record. Images for each common meter type, with the digits highlighted, prevent a large share of both incorrect readings and estimated bills.
Publish the reading window
A reading submitted after the billing run will not appear on that bill. Telling customers when to submit is what stops the estimate complaint.
Explain estimates properly
Why they happen, how they are calculated, what happens when an actual reading follows and whether a bill is rebalanced. Customers assume estimates are deliberate over-charging.
Payment difficulty goes straight to people
Anyone unable to pay needs the right team and proper support routes, never an automated response. This must be prominent and immediate.
Vulnerable customers need a visible route
The priority services arrangements, who qualifies and how to register. Publishing it reaches people who do not know it exists.
Moves generate a spike of their own
They are covered in moving home questions utility customers ask.
Outages swamp the same queue
That is covered in service outage and billing questions that swamp support.
Billing frustration drives churn
It is the pattern in billing questions that turn into cancellations and an AI assistant for a subscription business.
Getting started
Publish meter guidance with photographs, reading windows and how bills are calculated, then answer procedural questions at any hour while accounts stay behind secure access. SpideyChat for B2B providers answers from your published pages. Try SpideyChat on your own site, or read about answers on the features page.