Plumbing Dispatch Software for Days That Change at Ten in the Morning
A plumbing dispatcher spends the morning rebuilding a day that was agreed the night before. A burst pipe outranks a booked service, someone has to be pulled off a job that was already running late, and three customers need telling. It is a skilled job done at speed, and the reason most dispatch software does not help is that it models the calendar rather than the decision.
Running this manually today?
See how Fieldproxy handles it — a walkthrough on your own workflow, not a canned demo.
Book demoWhat a real dispatch decision uses
- Who is qualified and ticketed for this work, including gas and unvented
- Who is nearest right now, on real roads at this time of day
- What is actually on their van, which decides fix or return visit
- Which booked jobs may be moved, which may not, and who has to be told
- Contracted response times and which jobs are closest to breaching one
- Out-of-hours rates, standby rotas and who is genuinely available
Why the moved jobs matter more than the emergency
Handling the emergency is the easy half — it is urgent, it is visible, and somebody will deal with it. The part that quietly costs money is the wake behind it: the jobs that got pushed, the customer moved for the second time this month, the framework client whose response window slipped past the agreed number without anybody recording it.
Most systems move a job and forget it. The record of why, and of what it cost in commitments, does not exist, so the pattern only becomes visible as a complaint or a contract review.
Software that is told how you dispatch
Fieldproxy holds your dispatching rules rather than a generic algorithm — your skills matrix, your priority ordering, your response commitments, your rules about which customers can be moved. The routine reassignments happen against those rules; the dispatcher spends their attention on the cases that genuinely need judgement.
Things usually fixed elsewhere and yours here:
- Skills, tickets and how strictly they gate assignment
- Priority ordering — what outranks what, and when
- Response-time targets per client or framework, flagged before a breach
- Which jobs may be auto-moved and who gets notified when they are
- Van stock as a constraint on who can take the job
- The dispatch board itself, and what a dispatcher sees first
Two approaches to the same problem
| A fixed product | A configured platform | |
|---|---|---|
| Assignment logic | The vendor's algorithm | Your rules, as rules |
| Moved jobs | Silently rescheduled | Tracked, with the commitment cost visible |
| Response commitments | Reported afterwards | Flagged before the breach |
| An awkward exception | In the dispatcher's head | Part of the model |
| Best when | Simple domestic scheduling | Mixed reactive, contract and framework work |
What you can run on it
- A live board and map showing the day as it actually stands
- Emergency insertion that reshuffles and notifies everyone affected
- Skills, tickets and van stock as real assignment constraints
- Response-time tracking with warnings before a target is missed
- Engineer mobile app that works with no signal and syncs later
- Reporting on utilisation, travel, first-time fix and response performance
When this is the wrong choice
With three or four engineers and a whiteboard that works, this is overhead. It pays once the rules have outgrown one person's memory and a bad assignment carries a contractual cost rather than just an awkward phone call.
Common questions
What is plumbing dispatch software?
It is the system that decides and records who goes to which job and when, and reshuffles when something urgent arrives. The useful versions account for skills and tickets, van stock, travel and contracted response times rather than treating the day as a calendar.
How does it handle an emergency mid-morning?
The job is inserted into the existing day rather than appended to the end, the right engineer is chosen against your rules, the affected jobs move according to what you have said may move, and the customers and engineers affected are notified.
Does it track the jobs that got pushed?
Yes, and this is usually the more valuable half. A customer moved twice in a month, or a framework response window that slipped, becomes a report rather than a complaint.
Can it take van stock into account?
Yes. Whether the part is on the van frequently decides whether the visit is a fix or a wasted trip, so it can act as a constraint on who gets assigned.
Does a dispatcher still make decisions?
Yes, and the balance is yours. Most operations want routine assignment automated against their rules and a human on the exceptions. Full automation tends to get turned off the first time it optimises drive time at the expense of something that mattered more.
How long does it take to set up?
Days. The longer part is usually writing down your dispatch rules explicitly, which most businesses have never had to do.
See it running your dispatch rules
Bring the exceptions your dispatcher keeps in their head — those are the fastest test of whether this fits.
Book a walkthrough