Sort energy billing disputes and spot possible back-bills
Household energy in Great Britain. Gives each billing contact a dispute type and flags signs of long-estimated bills. Code works out the 12-month limit.
Try it on this example
Channel (email, chat, call transcript, letter): Email
Customer contact
- Does the customer question or dispute a bill, a charge, a balance or a payment amount?Yes99%
- What is the customer mainly disputing about their bill?Catch-up bill100%
- Does the customer say they had only estimated bills, or no bills, for a long time?Yes98%
- Does the contact say the customer refused or prevented a meter reading or access to the meter?No94%
- Does the customer say they asked us before for a reading, an accurate bill or a meter fix?Yes99%
- Does the customer give a meter reading in the contact?Yes99%
- How much financial difficulty does the customer describe?Clear difficulty100%
- Does the customer express dissatisfaction with our service, charges, decision or conduct?Yes98%
- Does the customer say they have gone, or will go, to an ombudsman, regulator, lawyer, the press or social media?No91%
- Does the customer mention circumstances that may mean they need extra support?Yes89%
- Which team should pick up this billing contact first?Back-bill review99%
These are real answers stored from one run on this example.
The prism behind it
Sort energy billing disputes and spot possible back-bills
Fields
- Channel (email, chat, call transcript, letter)
- Customer contact
Context
Rule set: Great Britain, household energy. Glenmoor Energy supplies gas and electricity to homes. A water company, a telecom provider or a supplier in another country replaces this paragraph and the back-billing paragraph with its own rules and keeps the rest. Back-billing: Ofgem's rules stop a supplier billing a household or microbusiness customer for energy used more than 12 months before the bill when the customer was not billed correctly through no fault of their own. The limit does not apply where the customer acted unreasonably, for example by stopping the supplier billing accurately, such as by blocking access to the meter, by ignoring requests for payment, or by stealing energy. Whether the limit applies, and which charges fall outside it, is worked out by code from billing and meter data, and a person reviews any suggestion that the customer prevented readings. Nothing here applies the rule. A catch-up bill corrects the account after a period of estimated bills, no bills, or a meter that was not sending readings. It is usually much larger than the customer's normal bills. Customers rarely say back-bill; they write "out of nowhere", "all my bills were estimated" or "I never had a proper bill". Complaints: Glenmoor counts any expression of dissatisfaction about its service, its staff, its charges or how a problem has been handled as a complaint, whether or not the customer uses the word. Extra support: customers who mention health problems, disability, old age, bereavement, money trouble, a language, literacy or hearing barrier, or similar circumstances are offered extra support by a trained person. Go only on what the customer says. Do not infer anything about the customer from their name, wording or tone. Dates, amounts and meter readings are read from the text by code, not here.
Questions
Does the customer question or dispute a bill, a charge, a balance or a payment amount? Yes / No
Read the contact. Yes: The customer questions or disputes at least one bill, charge, balance, refund or direct debit amount. No: The contact is about something else, such as a fault, a move with no charge questioned, or a request for a copy of a bill.
What is the customer mainly disputing about their bill? Choice
Read the contact and the catch-up bill paragraph in the context. Pick the one that fits what the customer mainly disputes. A large bill that follows estimated bills or no bills is a catch-up bill, even when the customer calls it high usage.
Does the customer say they had only estimated bills, or no bills, for a long time? Yes / No
Read the contact. Count "all my bills said estimated", "I haven't had a bill since I moved in", "the smart meter never sent readings" and similar, when the customer describes it as lasting months or longer. Code reads the dates. Yes: The customer says they had only estimated bills, or no bills, for months or longer. No: The customer says nothing of the kind, or mentions a single estimated bill.
Does the contact say the customer refused or prevented a meter reading or access to the meter? Yes / No
Read the contact. This is a statement against the customer, so a person always reviews it. Count only what the text says the customer did: refusing access, turning an engineer away, or blocking or tampering with the meter. Yes: The text says the customer refused or prevented a reading or access to the meter. No: The text says nothing of the kind. A missed appointment the customer tried to rebook, or a reading the supplier failed to collect, is No.
Does the customer say they asked us before for a reading, an accurate bill or a meter fix? Yes / No
Read the contact. Yes: The customer says they contacted us before asking for a meter reading, an engineer to read or fix the meter, or an accurate bill. No: The customer says nothing about asking before.
Does the customer give a meter reading in the contact? Yes / No
Read the contact. Code reads the digits; judge only whether a current reading is given. Yes: The customer gives a meter reading, or says one is in an attached photo. No: The customer gives no reading.
How much financial difficulty does the customer describe? Scale
Go only by what the customer says about their money. Pick the level that fits their strongest statement.
Does the customer express dissatisfaction with our service, charges, decision or conduct? Yes / No
Use the complaints paragraph in the context. Dissatisfaction counts whatever the main purpose of the contact, and whether or not the customer uses the word "complaint". A question about a bill asked without dissatisfaction is not a complaint. Yes: The customer is unhappy with something we did, failed to do, charged, or decided. No: The contact expresses no dissatisfaction with us.
Does the customer say they have gone, or will go, to an ombudsman, regulator, lawyer, the press or social media? Yes / No
Count an ombudsman, a regulator or government agency, Citizens Advice, a lawyer or solicitor, an MP, the press, a public review or a social media post. Count a threat, or a statement that it is already done. Do not count a plain question about how to complain. Yes: The customer says they have gone, or will go, to one of these. No: No such body or step is mentioned as something the customer will do or has done.
Does the customer mention circumstances that may mean they need extra support? Yes / No
Use the extra support paragraph in the context. Count only what the contact says about the customer or someone in their household. Do not infer anything from tone, writing style or spelling. Yes: The contact mentions health problems, disability, bereavement, old age, money trouble, a language, literacy or hearing barrier, or similar circumstances. No: The contact mentions none of these.
Which team should pick up this billing contact first? Choice
Judge the contact as a whole against the context. The answer is a suggestion for the queue; code applies the back-billing rule and a person decides the outcome. When more than one option fits, pick the first in the list.
Lens columns
is_billing_dispute, is_billing_dispute_probability, dispute_type, dispute_type_probability, long_unbilled, long_unbilled_probability, access_obstructed, access_obstructed_probability, reading_asked_before, reading_asked_before_probability, reading_given, reading_given_probability, financial_difficulty, financial_difficulty_average, complaint_expressed, complaint_expressed_probability, escalation_threat, escalation_threat_probability, vulnerability_signal, vulnerability_signal_probability, route, route_probability
Run it on your own text
Add this prism in the app, change any question, and test it on a file of your own.