First-time fix is won at the dispatch desk

A repeat visit costs a service business two ways: a truck and a technician you pay for again, and a customer who waited twice. Most of those visits trace back to the dispatch desk.

Most Dynamics 365 Field Service↗ rollouts that fail get through configuration fine. They fail at the dispatch desk, in week three, when the schedule the system proposes doesn’t match the one the dispatcher trusts.

The rollouts that stick have a few things in common. Our consultants learned them at the dispatch desk.

The dispatcher decides whether the investment pays off

The dispatcher is the first user who can quietly switch the system off. Work orders, territories, and the mobile app can all be right on day one. If the dispatcher overrides the board every morning, none of it matters.

The whiteboard has never been wrong about which technician can handle which machine. The board only knows what someone configured.

One bad morning is enough for the dispatcher to go back to the whiteboard and phone. After that, the system records the day after the fact.

The gap is between where the schedule is made and where it’s kept.

The board has to know what the dispatcher knows

Skills, certifications, territory, and parts are what a good dispatcher carries in their head. Put them in the system before go-live, or the board will propose schedules the dispatcher knows are wrong.

That starts at intake. Capture the serial number, meter hours, and fault codes when the call comes in. Match the job to the technician whose skills fit it, and check the part before the truck rolls.

All of it is ordinary Field Service capability, designed with the person who will use it at 6 a.m.

Hand the board and its rules to the dispatchers

A rollout sticks when the dispatch lead owns the rules. Territories change, technicians earn new certifications, and a new service line shows up mid-year. If every change needs a partner, the board falls behind the business within a quarter.

So we build the enablement in from week one. Your admin pairs with our consultant on the real scheduling rules, and each design decision is written down with its reason. By go-live, your dispatch lead can add a skill or redraw a territory without calling us.

At a dispatch desk, agility means the system changes as fast as the day does.

The dispatch desk is one handoff in a longer chain

A trusted board fixes one handoff. The part still has to be on the truck, and the finished job still has to reach the invoice. When parts are reserved against the work order and the technician’s hours flow to billing at close, the right first visit also becomes a billed one.

So we also connect dispatch to the parts counter and to finance.

The second truck roll is the number to watch

What we call the second truck roll is the visit that happens because the first one arrived without the right part or the right answer. It shows whether the fix reached the field.

First-time fix is the usual headline. The second truck roll is easier to see in the data, and it points at the cause: the wrong technician, a missing part, or a diagnosis that came too late. Track it by week from go-live, and dispatchers can see their own progress.

Capture the veteran’s knowledge before you need it

The technician shortage makes dispatch design matter more. The TechForce Foundation’s 2026 report puts demand for new diesel technicians at 26,692 a year, with 14,011 of those roles unfilled. That leaves 52 percent of demand unmet.

When you can’t hire the veteran, capture what the veteran knows. Today an equipment dealer’s newer technician, facing an unfamiliar fault, calls around until a senior tech picks up. Recording the fault, the fix, and the part on every work order puts that knowledge in the system.

AI is one of the tools that can put it on the tablet. A knowledge agent reading the service history and the manuals can surface likely causes and the right part before the truck leaves the yard. It only works if the history was captured well first.

The evidence points the same way, with a caveat. In a study of 5,179 customer-support agents at one firm, novices using AI resolved 34 percent more issues per hour. The average gain was 14 percent (Brynjolfsson, Li and Raymond, 2025). Nobody has run that study with field technicians yet.

What stays human matters as much as what the agent drafts. The repair call, the safety call, and the warranty call stay with the technician.

Some dispatch desks need a different sequence

This pattern doesn’t hold everywhere. Where dispatch is unionized, sequencing rules change the design, so plan for them from week one. In a single-branch operation where the service manager is also the dispatcher, the fix is lighter.

Equipment dealers have one more limit. Dynamics 365 is not a dealer management system on its own; it needs the OEM’s template or a dealer ISV. Legacy dealer systems usually integrate in batches, not in real time. And the Field Service Scheduling Operations Agent is still in preview, so don’t design a rollout around it yet.

What service leaders should do in the first three weeks

Start at the dispatch desk. Sit with the dispatchers in week one, before anyone touches the data model. The design follows what they trust.

Put skills, certifications, and parts in before go-live. A board that doesn’t know what the dispatcher knows will lose the first morning it gets wrong.

Measure the second truck roll alongside first-time fix. It’s the number that shows whether the fix reached the field.

Hand the rules to your dispatch lead. Pair your admin with the consultant and document every scheduling decision. The board should change as fast as the business does.

Capture the veteran’s history on every work order. Then put it on the newest technician’s tablet, with AI where it helps. The repair and safety calls stay with the technician.

How we know this

This point of view comes from Ludia’s Field Service delivery. Technician figures: TechForce Foundation, Technician Supply, Demand and Opportunity Report (May 2026). Support-agent study: Brynjolfsson, Li and Raymond, Quarterly Journal of Economics (2025).