In 2024 we instrumented 1.4 million dispatch decisions across 230 plumbing tenants on FieldServo. The ones that switched on Smart Dispatch saw a 47% drop in median first-response time. Here is exactly what the engine does — and how to replicate the gains.
The dispatch problem
Plumbing is a special case in field service. Calls arrive in two flavours: scheduled work (routine maintenance, install jobs, recurring contracts) and emergency calls — burst pipes, flooded basements, lost-pressure tickets. The latter is graded by minutes, not hours, and the cost of a bad dispatch is concrete: an unhappy customer, a one-star review, an insurance claim.
Traditional dispatch is a human in a room with a whiteboard. They know their crew, they know the city, and on a calm Tuesday they're brilliant. But on a Saturday afternoon when six emergency calls arrive in the same hour, the whiteboard breaks. We measured this by instrumenting the dispatcher's screen: median decision latency rose from 22 seconds to 4.1 minutes once the queue hit five concurrent tickets.
The signals we score
FieldServo's Smart Dispatch ranks every available technician against every open job using four signal categories. None of them is exotic — the magic is in how cheaply we can compute them at request time.
Skill-tag matching
Every technician carries a set of skill tags (residential, commercial, gas-fitting, backflow-cert, excavation) and a corresponding certification expiry date. Every job carries the tags it requires, derived from the booking widget or the dispatcher's classification.
The naive version returns the first technician whose tag set is a superset of the job's. Better: weight the match so a technician with exactly the right tags ranks above one with all-the-tags-plus-five-extras — over-qualified crews are expensive and you want them on the jobs that need them.
Live calendar collisions
The engine checks each candidate's calendar in a 90-minute lookahead window and discards anyone whose travel time would overlap an existing booking. This is harder than it sounds because calendars are eventually-consistent across mobile clients; we maintain a 200ms-fresh authoritative cache keyed on technician ID.
The proximity bias
Geographic distance gets the heaviest weight in the final score. We bucket the city into 1-km geohashes and pre-compute drive-time multipliers per hour-of-day. At dispatch time the engine reads from the bucket grid rather than calling a maps API — this keeps p99 latency under 80 milliseconds.
Counter-intuitive finding
The closest technician is not always the best dispatch. Over-rotating on proximity creates "milk-run" patterns where one crew gets every job in their geohash and others starve. We added a fairness penalty that decays per-tech every 30 minutes.
Measured impact across 230 tenants
We tracked four headline metrics across the cohort of 230 plumbing tenants that adopted Smart Dispatch between October and December 2024:
- Median first-response time: down from 41 min to 22 min (a 47% reduction)
- Dispatcher screen-time per job: down 74%, with three tenants eliminating the dispatcher role entirely
- Same-day re-dispatch rate: down from 11.2% to 2.8% — fewer wrong-tech sends
- Customer NPS (post-job survey): up 18 points on average
The single biggest win was not the dispatch decision itself but the elimination of phone-tag. Smart Dispatch sends the assignment to the technician's mobile app with a live ETA; the customer gets an SMS with the same ETA before the truck has even pulled out.
"We used to have a dispatcher on call for emergency hours. Now FieldServo handles the routing and the dispatcher just monitors quality. That role got reassigned to growth — and our weekend revenue is up 34%." Maya Lindqvist, COO at Norden HVAC
What this means for your fleet
Smart Dispatch is not a bolt-on. To get the gains you have to actually use the skill-tag model and you have to keep certification data current. Tenants that left skill tags empty saw a 12% improvement — material, but a fraction of what tag-disciplined teams achieved.
If you operate a plumbing or HVAC fleet of more than five crews, the math is simple. Even at our smallest plan, the dispatcher-hours saved pay for the subscription in week one. We'd rather you not take our word for it — book a sandbox and try it against your real Saturday-afternoon queue.