The bill went up.
Nobody said why.
So they call you.
A power bill arrives higher than last month, and the bill itself explains the amount without explaining the reason. This demonstrates the alternative: the reason assembled from the customer’s own usage, with one question that settles what the data cannot.
“A bill tells you what you owe. It almost never tells you what happened.”
Tidewatt Energy · an invented exampleThe gap between the bill and the reason
A bill lands eighteen percent up. The customer does not know whether that is the weather, the heat pump, the new flatmate, or a fault. What they do know is that the number is bigger and nobody has explained it. So they ring, and the person who answers starts from nothing.
Every energy retailer holds half-hourly usage data and weather for the same period. The customer holds the one fact neither of those contains — who was in the house. Nobody asks them, because nothing is listening during the wait.
What happens now
A number with no story. The contact centre reconstructs the explanation one call at a time.
What it costs
Bill shock is the single biggest driver of switching in the category, and it is an explanation problem.
What the concept does
Assembles the reason from their own usage, asks the one thing the data cannot know, and stops.
Every power moment, one pattern.
Each of these is a moment your customer already spends with you. Each can carry what the phone above shows: watch the work, earn the wait, answer one thing.
Be relevant — right thing, right moment · Be respectful — short, skippable, quiet by design · Be measurable — real impact, on the record · Be Aotearoa — built here, for how Kiwis actually wait
Every wait on a power account
Six moments where a household is waiting on a retailer, and what each wait could hand back instead.
The lights are on the night you move in, without a phone call made from a driveway.
You find out where the month is going while there is still month left to change it.
The reason for the number is ready before the call is answered, and usually instead of it.
The best hour on the plan gets used, without anyone rearranging their evening to catch it.
The winter bill arrives as something expected rather than something done to you.
The most frightening wait in the category gets a truthful account, and a person still makes the call.
Four steps, every time.
- The signalSomething in your own systems says a person is now waiting, and roughly how long for.
- The predictionHow long this one will really take — not the average, this one.
- The valueSomething worth their attention goes into that window: an answer, a credit, a thing prepared while they wait.
- The exchangeThey get value. You get a customer who stayed, and one optional answer you have always wanted.
This is the reward layer, running for real on this page. Drag to scratch it. Nothing is collected, nothing is sent — it is here so the idea is something you do, not something you read.
US retailers lose an estimated $37.7 billion a year to customers who abandon because of long queues, split roughly $15.8b to competitors and $21.9b abandoned outright (Adyen with 451 Research). The New York State Department of Labor reported a 48% reduction in hang-ups after introducing virtual queuing. Theme parks moving to virtual queues reported a 36% lift in per-capita spending, because guests spent the wait somewhere that sold something. A Seattle-Tacoma Airport study found 63% of passengers said they shopped or ate more because they saved time in the security queue.
Every figure on this page carries its source. Overseas figures are shown as overseas figures — we have not found a published New Zealand equivalent, and we will not invent one.
One bill. Four explanations.
The same eighteen percent, explained four ways. Nothing changes a tariff, a plan or a payment date — and the accounts that need a person get one instead of a chart.
A template sends the same thing to everyone and changes the name. What matters here is the case that should get something different — or nothing at all.
The rules beside each draft are placeholders. A pilot replaces them with your actual policies. We have not seen those, and this concept does not guess at them.
The checks that run before an explanation is sent
Power is an essential service, and the difference between explaining a bill and lecturing someone is whether anything was listening first.
Drafts are held against the Electricity Authority’s Consumer Care Obligations, the Fair Trading Act 1986, the Consumer Guarantees Act 1993, and the Privacy Act 2020.
Press run to see what it catches — and what it refuses to produce at all.
One room. Your people, your agents, every action on the record.
Every concept on this page would run inside a private room like this: your team and the agents in the same space, drafts appearing with receipts, a named person saying yes. It runs on infrastructure you approve — and what is said in the room stays in it.
receipt sources: your rate card · rules: yours · held for approval
Client information stays in your room. Six months later, “where did this come from?” is one line, not a search.
Yours
Runs where you approve — your own room, your own record. Nothing in it leaves it.
On the record
Every agent action lands as a line a person can read — not a log only a vendor can open.
People decide
Drafts wait for a named person. The room shows who said yes, and when.
This panel is a concept picture, not a live room — a pilot stands up the real one, on infrastructure you approve.
The batch, before anything sends
Illustrative and fictional. No production access is requested by this concept.
| Account | Count | Prepared | Waiting on | Status |
|---|---|---|---|---|
| Usage tracks the cold snap | — | Explanation drafted, no tip attached | CX sign-off | Awaiting approval |
| Household grew this month | — | Explanation drafted after the answer | CX sign-off | Awaiting approval |
| Constant overnight draw | — | Investigation raised, no bill explained | Field investigation | Held — under review |
| Usage falling in cold weather | — | Nothing drafted | A named person | Held — no draft |
| Medically dependent flag | — | Nothing drafted | A named person | Held — no draft |
| Meter read estimated | — | Explanation held | Actual read | Parked |
Counts are blank because this is a demonstrator. There is no Tidewatt, and therefore no accounts.
Every draft carries its own working.
Not a log somebody has to go and find. The provenance travels with the work — what it read, which rules it held, who must approve it, and what it refused to do.
This matters most on the day someone asks why it said what it said.
- Artefact
- Bill explanation — usage tracks the cold snap
- Read
- Invented tariff and usage for an invented retailer · account fields: half-hourly usage, weather for the period, medical-dependency flag, payment history shape. No payment credentials.
- Rules held
- Electricity Authority Consumer Care Obligations · Fair Trading Act 1986 · Consumer Guarantees Act 1993 · Privacy Act 2020
- Refused
- No tariff, plan or payment date was changed. No saving was projected. No explanation was sent to an account showing rationing or carrying a medical-dependency flag. No suspected fault was explained away.
- Approver
- A named person. Unsent until then.
- Prepared
- —
- Reference
- —
What this will never do
It does not send. It prepares, and a named person sends. It does not publish to any channel, commit spend, move money, or make a decision that belongs to a person. It does not pretend to be a person — every draft says it was prepared by a machine and approved by a human.
No production access is requested by this concept.
Scope
In a real engagement: bill explanations for opted-in accounts on one tariff, six weeks. Not pricing, not plan switching, not credit management, not the billing engine.
Access
Half-hourly usage and the field names for medical dependency, payment-arrangement history and meter-read type. No payment credentials. No account records leave your systems.
Scorecard
Explanations that prevented a call. Held cases a person agreed should have been held. Faults caught before a customer paid. And whether a CX lead treats the hardship-held list as their own to-do.
Fail any line of the scorecard and we change the design or stop.
What a pilot actually asks of you.
Written out in full, because the honest version of this is short and most of it is your time, not your money.
One named person
The approver. Every draft stops with them and nothing reaches a customer until they say so. Expect about two hours a week — reading drafts, not managing a project.
One situation, not the business
In a real engagement: bill explanations for opted-in accounts on one tariff, six weeks. Not pricing, not plan switching, not credit management, not the billing engine.
Read-only access, nothing that writes
Half-hourly usage and the field names for medical dependency, payment-arrangement history and meter-read type. No payment credentials. No account records leave your systems. No production credentials, no write permissions, no access to anything the pilot does not need.
Your actual rules
The policies, limits and words the drafts must be held against. Every rule on this page is a placeholder standing in for yours. An afternoon with whoever owns them is usually enough.
Six weeks, then a real decision
Scored on: Explanations that prevented a call. Held cases a person agreed should have been held. Faults caught before a customer paid. And whether a CX lead treats the hardship-held list as their own to-do. Fail any line of that and we change the design or stop. You keep everything drafted either way.
A fixed fee, agreed in writing first
No number is published on this page, because it depends on which situation you pick. Whatever it is, it is agreed before any work starts and it does not move.
Run the pilot.
Say yes to the six weeks above, and add anything you would change first. Nothing here is fixed — most pilots move a line or two before they start, and the notes below are how that happens.
Opens your mail app to assembl@assembl.co.nz with your notes in it. Nothing is collected by this page.
- Six weeks, one situation, scored against a written line
- Read-only access, nothing production
- A named approver — nothing sends without them
- A fixed fee, agreed in writing before anything starts
- Stop any time. You keep what was drafted
Pick a verb.
Not “book a demo”. Any of these is a real next step, and the last one is a perfectly good answer.
What is the one constraint we have got wrong?
Every concept is built from the outside. There is always something about how Tidewatt actually runs that we could not see. One line is enough.
Opens your mail app to assembl@assembl.co.nz. Nothing is collected by this page.