Every multi-branch field service company eventually hits the same ceiling. Technician headcount grows. Jobs closed per technician does not.
The reason is rarely a scheduling problem. It is a diagnosis problem — a technician standing in front of a piece of commercial equipment with no record of what has already failed on that specific unit, what fix worked last time, or what quirk of that installation makes the textbook fix wrong. The visit ends in a temporary patch and a second appointment, and the second appointment is what actually caps growth.
This is what we found at a commercial HVAC and refrigeration service contractor operating across twelve branches. We are calling it Corrigan Mechanical. The name has been changed; the constraint has not.
The Constraint
Corrigan dispatches technicians to commercial refrigeration and HVAC faults across twelve branches, each running its own paper tickets and local service notes. A unit serviced eighteen months ago by a technician who has since moved branches carries no memory of that visit into the next one.
The result was a first-time fix rate stuck in the low sixties — meaning close to four in ten visits ended without resolution, and each of those became a second job competing for the same finite technician hours as every new inquiry.
The company was not short of demand. Service contracts kept renewing. What it lacked was the ability to close more of those jobs on the first visit, because the knowledge required to do so lived in whichever technician happened to remember the last visit — if it was the same technician at all.
Growth in headcount did not fix this. Every new technician arrived with no access to twelve branches' worth of equipment history, and needed years in the field before pattern recognition caught up to what a senior technician already carried.
Diagnose
We did not start by asking what a scheduling algorithm could optimize. We mapped where the actual failure occurred, and it was not in dispatch. Jobs were being assigned to available technicians correctly. They were failing during the diagnosis itself, because the technician standing at the unit had no access to what had already been tried on that specific piece of equipment.
That is the constraint we engineered against: not who gets sent where, but what a technician knows the moment they arrive.
Engineer
We did not place a chatbot in the technician's hand and call it transformation.
We built the infrastructure underneath the visit. Service tickets, technician notes and warranty records across all twelve branches were unified into a single equipment-level history, indexed by unit serial number rather than by branch or job ticket. Before a technician arrives on site, the system surfaces the specific unit's fault history, prior fixes attempted, and any recurring pattern flagged across similar units in the fleet.
The system does not diagnose the fault. It gives the technician the equipment's memory back, so the diagnosis starts from precedent instead of from scratch.
Deploy
The system now runs ahead of every dispatched job, not alongside it. A technician receives the unit's service history before the job even shows up on their route, and logs the outcome of the visit back into that same record when the job closes — so the system gets more accurate with every job it supports, not less.
First-time fix rate rose from the low sixties into the high seventies within two quarters. Second visits fell by roughly a third. Technician capacity that had been absorbed by callbacks became available for new contracts, without adding a single technician to headcount.
What This Changes
The advantage was never going to come from a smarter dispatch algorithm. It came from twelve branches' worth of equipment history, finally attached to the equipment instead of scattered across whoever happened to service it last.
This pattern holds across field service businesses broadly, whatever the equipment: refrigeration, elevators, industrial pumps, medical devices under service contract. The constraint on growth is rarely the number of technicians on the road. It is what each of them knows the moment they arrive — and that is a system problem, not a hiring problem.
If second visits are quietly capping your growth, talk to us. Contact Anveril →
Author: