Hire an AI Dispatch and Field Operations Coordinator Who Overrules the Router

When the Dispatch Algorithm Is Wrong, Who Is Awake?

It is 7:40 on a Tuesday and the board looks clean. The engine has sent your most experienced technician across town to a filter swap, because his close rate on that job type is high, and put a second-year apprentice on the compressor call at the account whose renewal is up in November. Nobody did anything wrong. The scheduler optimized exactly what it was told to optimize.

That is the shape of the problem, and it is now the common shape. Scheduling and dispatch, route suggestions, quotes drafted from job notes and automated appointment reminders are the ordinary uses of AI in field service, and platforms including ServiceTitan and Housecall Pro will match a job to a technician by skill and history without being asked twice ¹. Vendors report productivity gains in the 10 to 15 percent range from that automation plus predictive maintenance and real-time guidance in the field ³. Those gains are real and they are also the reason the exception load moves rather than disappears.

So the day divides. Eighty percent of it the router handles better than a person with a whiteboard ever did: drive time, skill match, parts on the truck, the tightening of a four-hour window. The remaining slice is where the money lives. A callback that has to go back to the tech who was there first even though he is forty minutes away. A commercial account that will tolerate a reschedule from anyone except this customer. A storm that makes every estimate on the board wrong at once. The role you are hiring exists for that slice, and for the loop that turns each override into a constraint the system will honor next week.

The broader pattern is not confined to contracting. Boston Consulting Group's 2026 survey of 11,749 workers found 47 percent now spend more time managing and directing AI than doing the work themselves ². Dispatch is one of the first places in a trades business where that becomes literally the job description.

Which Backgrounds Produce a Real Dispatch Coordinator?

The best candidates have usually sat in one of three seats: a dispatch desk at a contractor big enough to have one, a field supervisor role where they built the day and then drove it, or a technician career interrupted by a back or a knee. What unites them is that they have paid for a routing mistake personally, in windshield time or in an angry customer, and the memory makes them skeptical of a confident recommendation.

The unexpected sources are worth naming, because the obvious ones are picked over. Emergency and municipal dispatchers arrive fluent in triage, in radio discipline and in documenting a decision while it is still happening. Freight and LTL load planners have run constraint-solving software for years and already know that the optimizer is right on average and wrong on the load in front of them. Restaurant expeditors and hotel front-office managers have the same instinct at a smaller radius. Adjacent field roles that software has already rewritten produce good candidates too, which is why a company hiring a drone inspection pilot and aerial data analyst often finds the same person shortlisted for both.

The tells separating real from performed are specific and they show up in the first ten minutes. A real one tells you about a particular override: the date, the job, what the system wanted, what they did instead, and whether it turned out right. They will volunteer the time they overrode it and were wrong. A performed one talks about optimizing workflows, describes the platform's features back to you, and cannot name a single day the software cost the company money. Ask for the worst dispatch decision they ever made. Anyone who has run a board has one ready.

Screen for the Override This Coordinator Can Still Explain

How a candidate got good at AI matters more than which tools they list, and in this role the honest answer is usually unglamorous. The strong ones used a chatbot to write the SMS reminder copy and then rewrote it because customers replied to it wrong. They asked a model to build the spreadsheet formula that compared yesterday's planned routes against actual drive times. They tested a new rule by replaying last month against it before turning it on live.

What that history produces is a person who treats the tool's output as a draft. Give them a real scenario in the interview: here is today's board, here are three calls that came in at 10 a.m., the model has already resequenced everything, tell me what you would change and what you would leave alone. Listen for whether they ask what the model was optimizing for before they touch anything. Listen for whether they check something outside the screen, a phone call to the tech or to the customer, before committing.

The failure mode on the other side is a candidate who overrides constantly, on feel, and never writes down why. That person will make the system worse every week they hold the seat, because the constraints never learn and nobody can audit the day. You want overrides to fall over the first six months, not because the coordinator gave up but because they fixed the rules. If your company is standing up several of these systems at once, the tuning and rollout work may belong to a separate field service AI enablement lead rather than to the person running the daily board.

Where Do You Find Someone Already Running Dispatch on These Platforms?

Not on the general job boards, or at least not first. This person is currently employed, usually at a competitor within forty miles, and is not browsing. The venues that work are the ones where operators talk to operators about the software they run every day.

Start with the vendor ecosystems. ServiceTitan runs an annual user conference, Pantheon, and the sessions on dispatch and scheduling draw exactly the people who tune these systems for a living. Housecall Pro and the other platforms maintain their own user communities where a dispatcher posting a workaround at 11 p.m. is showing you their whole working style for free. Trade associations are the second lane: local chapters of ACCA and PHCC, plus buying and best-practice groups like Nexstar Network and Service Nation, run peer meetings where operations staff attend, not just owners.

The trades subreddits and Facebook groups are underrated and cheap. Someone who patiently answers a stranger's routing question in r/HVAC is demonstrating the temperament you need. Community college HVAC and plumbing programs are the long game: the graduate who liked the theory more than the crawl space is often the one who ends up on the board. And check inside your own building first. The dispatcher you already employ has the domain half of the job, which is the half that takes years. The systems half takes months.

Pay Against Revenue per Truck, Not Against the Old Dispatch Desk

Be straight about the number, because this title is new enough that no public wage survey covers it cleanly. Government occupational wage data still classifies this work under general dispatching, which was priced for a phone-and-whiteboard job, and there is no established national benchmark for the hybrid version that owns a scheduling engine. Anyone quoting you a precise range for it is quoting a guess.

So anchor internally instead. The honest comparable inside most contracting companies is the operations manager band rather than the senior dispatcher band, because the scope is the same: this person's decisions move revenue per truck per day, and that figure is one you already know. Work out what a single wrong high-value dispatch costs you, multiply by a realistic weekly count, and let that set the ceiling you are willing to reach. Then check the local market by what a competitor would have to pay to take them from you, which for someone this embedded is generally more than a step raise.

What kills the offer is rarely the base. It is discovering that the title comes with no authority to override, or that every change to a routing rule needs the owner's approval, or that the software vendor's account manager outranks them on their own system. It is being measured on a utilization number they cannot influence. Candidates worth hiring ask about all three in the first conversation, and a company that has thought about forecasting demand well enough to hire a demand planner usually has better answers ready.

Can This Coordinator Run the Board From Home?

Partly. The mechanical half of the job travels fine: the board, the exception queue, the constraint tuning and the customer messaging all live in a browser, and plenty of coordinators run a clean day from a spare bedroom. What does not travel is the relationship with the technicians, built at the counter at 6:30 a.m. and in the parking lot at 4, which is the reason an override gets accepted without an argument.

The pattern that works in most contracting companies is on-site while the crews stage and depart, then flexible after. Fully remote is workable at multi-branch operations where the coordinator was promoted from inside and already has the credibility banked. It goes badly with an outside hire in month one, every time, because the first override lands as an instruction from a stranger.

When you write the posting, say which of these you mean. Field operations candidates read a vague remote policy as a company that has not decided, and the good ones have a current job. Say the hours, say the on-call expectation for storm weeks, and say who they can overrule without asking. That last line does more recruiting work than the salary line above it.

See the benchmarks >