Utility Revenue Protection
For utilities and the contractors who run their disconnection and reconnection (DCRC) work. Notices, disconnections, reconnections, tamper inspections and installment plans run on one platform, connected to your billing system, so crews act only on accounts that still owe and paid customers are reconnected on time.
The problem
The disconnection list is printed in the morning from balances that are already out of date. A crew cuts off a customer who paid last night, and the complaint reaches the utility before the crew is back. Another customer pays at noon and waits until the next day, because the reconnection request is passed along by phone.
Meanwhile nobody goes back to check the supplies that were cut, so some are quietly reconnected. Protected accounts are kept on a separate spreadsheet, and what was collected after each notice is worked out by hand at month end.
How it works
Every overdue account follows your rules, and the balance is checked again before each step.
Accounts come in from your billing system or Excel, and your rules sort each one: notice, disconnection, waiting or protected.
A crew delivers the notice with a GPS-stamped photo, the customer gets an SMS, and a balance check is scheduled.
A disconnection task is raised only if the account is still unpaid, and the crew sees paid or unpaid on site before acting.
Payment raises a reconnection task for the nearest crew, with a countdown against your time limit.
What it covers
Electricity and water, on the same platform and the same crews.
Notices delivered and disconnections done at the fuse, the feeder or the pole, each with photos, GPS and an outcome.
Requests from the counter, the call centre or your billing system reach a crew in minutes, with reminders as the time limit approaches.
A plan is agreed, sent to the customer by SMS and checked on every due date. A missed installment brings warnings, then a disconnection task.
Inspections with a case number, before and after photos, an estimated loss and a report ready for the utility.
Agents call overdue accounts before a crew is sent, and each call outcome sets the next step.
Balances come in from your billing system, and disconnections, reconnections and readings go back to it.
Track record
Utility Revenue Protection runs on the Fieldmaster platform, built by a team that has run field contracts in the GCC since 2015.
15M
Field operations across the GCC and other international markets.
2015
Built by field contractors who ran the work themselves.
10–18
Changes after go-live take days, made by the people who built it.
Results
The balance is checked when the task is raised and again at the door.
Every reconnection has a clock, a crew and a supervisor who sees it running late.
A return visit is scheduled after every disconnection, and misuse moves the account up to the next step.
Accounts on a plan, under legal protection or on your always-protected list never reach a crew’s task list.
Each notice, disconnection and failed visit has photos, a location, a time and a named crew.
Accounts paid after a notice and after a disconnection are counted for you, by segment and by day.
Why field focus matters
When the list goes out on paper and results come back at the end of the shift, the office can’t stop a wrong visit or speed up a late one.
Lists are printed from old balances, so crews visit customers who have already paid, and the utility takes the complaint.
A paid customer waits while the request passes from the counter to a supervisor to a crew, one phone call at a time.
A crew writes “door locked” or “customer refused”, with no photo or location behind it, and the visit is disputed.
A disconnected supply is reconnected illegally, and with no return visit planned it stays on for months.
FAQ
It runs the field side of credit control and loss reduction for a utility: delivering notices, disconnecting for non-payment, reconnecting after payment, and inspecting meters for tampering and illegal connections.
Fieldmaster.ai gives the crews a mobile app and the office a web console, connects both to your billing system, and applies your rules for when each account moves to the next step.
Disconnection and reconnection is the field work behind a utility’s credit control: a notice to an overdue customer, disconnection of the supply if the bill stays unpaid, and reconnection once it is paid. Managing it means deciding each day which accounts crews should visit, proving what they did, and reconnecting paid customers within the time the regulator or the contract allows.
Analytics tools study meter and billing data to find accounts that look wrong. Fieldmaster.ai runs what happens next in the field: the visit, the evidence, the follow-up and the report. It takes lists of accounts from your billing system or your analytics tool, and it does not replace either.
Yes. The balance is checked when the disconnection task is raised, so an account that has paid enough never reaches a crew. The crew’s form checks it again on site and shows paid or unpaid before they act.
Yes. Each has its own task types, rules and waiting periods, and the same crews, areas and reports can cover both.
Our team builds the connection as part of your project. Balances and paid accounts come in from your billing system, and completed disconnections, reconnections and readings go back to it. Where the billing database sits inside your own network, a small agent installed there handles the exchange.
Both. A utility can run its own crews on it, or a contractor can run the work and give the utility the same records, photos and reports.
A typical app is live in 10 to 18 working days. Your task types, rules, areas and reports are set up to match your contract, and work can start from Excel lists while the billing connection is being built.
