We hold consumption data and Priority Services Register details. How is that handled?

All processing runs on EU-hosted infrastructure under a data processing agreement, inside your security perimeter where required, and customer data is never used to train models. PSR data keeps its special-category handling: agents read the flag to stop automation, while the underlying detail stays under your existing access policies.

Our billing platform is a heavily customised Junifer. Can you actually integrate with it?

Yes — we build around what is there, whether that means REST APIs, database views or the batch and flow-file patterns utilities actually run on. We design around your billing windows rather than fighting them. Nothing gets migrated or replaced.

What should we not automate?

Debt escalation decisions, anything leading towards disconnection or involuntary prepayment, and any account carrying a vulnerability flag. Given Ofgem's scrutiny of those paths, an agent should prepare the case file and a person should make the call. We build that boundary in as a hard rule, not a setting.

Where do suppliers usually start?

The billing exception queue or complaint triage. Both are bounded, measurable daily, and painful enough that the operations team notices the difference. Success there earns the harder conversations about switching casework and field scheduling.

Energy automation solutions

We build agents for the retail energy back office: billing exceptions, meter read validation, erroneous transfer casework, complaint triage and Ofgem reporting. They work inside the systems and industry flows your teams already use — Junifer, Kraken, SAP IS-U, the DTS — which matters more as market-wide half-hourly settlement raises the cost of bad meter data. Hard escalation rules keep vulnerability and debt decisions with people.

Use cases

Works the billing exception queue: matches D0010 reads against estimates and releases held bills within tolerance
Triages complaints and inbound email, pulls account history from Junifer or Kraken, drafts replies for agent approval
Chases erroneous transfer cases through industry flows and keeps the customer informed until resolution
Validates incoming meter reads, flagging crossed meters and implausible consumption before a bill goes out
Books smart meter exchange visits against engineer skills and access notes, rebooking failed appointments automatically
Assembles Ofgem RFI responses and performance packs from billing, CRM and settlement data, fully audit-trailed
Processes change-of-tenancy requests: verifies move dates, raises the final bill, opens the new account
Runs early-arrears contact journeys, escalating any account with a PSR or vulnerability flag to a human

Common workflow problems

Billing exceptions and unbilled accounts age quietly in the queue until they surface as a write-off conversation.
Smart meter comms drop, estimates stack up, and the first accurate bill lands as a shock catch-up nobody explained.
Erroneous transfers mean months of flow-chasing with the other supplier while the customer holds two bills.
Engineers abort visits because access notes on the account never reached the job, and the rebook is weeks out.
Each Ofgem RFI sets off spreadsheet archaeology across billing, CRM and settlement extracts that swallows the reporting team.

How we help

We connect billing, CRM, field service and the DTS flows, so agents see the whole account rather than one screen.
Exception handling runs on your own validation rules; anything outside tolerance lands in a named human queue.
Customer-facing drafts are grounded in the account's actual reads, flows and tariff, with sources shown to the approving agent.
PSR and vulnerability flags hard-stop automation: those accounts always route to a person, never down a debt path.
Every automated action is logged against the account, ready for REC performance assurance and Ofgem scrutiny.

Systems we work with in this sector

We integrate around Gentrack Junifer, Kraken, ENSEK and SAP IS-U for billing, Oracle Utilities CC&B, Salesforce Energy & Utilities Cloud for CRM, Oracle Field Service or Totalmobile for scheduling, and the DCC and Electralink DTS for industry data.

Frequently asked questions

We hold consumption data and Priority Services Register details. How is that handled?: All processing runs on EU-hosted infrastructure under a data processing agreement, inside your security perimeter where required, and customer data is never used to train models. PSR data keeps its special-category handling: agents read the flag to stop automation, while the underlying detail stays under your existing access policies.
Our billing platform is a heavily customised Junifer. Can you actually integrate with it?: Yes — we build around what is there, whether that means REST APIs, database views or the batch and flow-file patterns utilities actually run on. We design around your billing windows rather than fighting them. Nothing gets migrated or replaced.
What should we not automate?: Debt escalation decisions, anything leading towards disconnection or involuntary prepayment, and any account carrying a vulnerability flag. Given Ofgem's scrutiny of those paths, an agent should prepare the case file and a person should make the call. We build that boundary in as a hard rule, not a setting.
Where do suppliers usually start?: The billing exception queue or complaint triage. Both are bounded, measurable daily, and painful enough that the operations team notices the difference. Success there earns the harder conversations about switching casework and field scheduling.

Relevant ways we support this sector

Business Automation Solutions — Practical automation built around the way your business already works.
AI Automations — Use AI where it improves throughput, quality, and decision support.
Process Audits — Find where time, accuracy, and money are being lost before building anything.

Discuss this industry: [email protected]