Microsoft Dynamics 365 Field Service · AI Dispatch
AI dispatch for Dynamics 365 Field Service — a board that runs itself.
Dynamics 365 Field Service dispatch still runs on a manual loop: requirement pane, Find availability, drag, drop, repeat. FieldCamp’s AI Dispatcher is dispatch software that works on top of D365 FS — it assigns every work order by skill, location and availability with a confidence score, dispatches in Immediate or Queue mode, and keeps the board true as the day moves.
No-cool call · Riverside
Panel inspection · Oak Hill
Quarterly PM · Marina Pl.
Filter swap · Downtown
Compressor swap · Northgate
Warranty return · Brookfield
No-heat call · Riverside
Boiler service · Westside
No rip-and-replace — Dynamics 365 stays your system of record. FieldCamp runs the dispatch day on top of it.
01 Morning dispatch, automated
The dispatch day starts at 6:00 AM. Your dispatcher doesn’t have to.
On the native schedule board, morning dispatch is a loop: open the requirement pane, select an unscheduled requirement, run Find availability to launch the schedule assistant, pick a resource, book — one requirement at a time.
FieldCamp runs that loop as an agent. It reads the unscheduled work orders from your D365 Field Service data, matches each one to the right technician by skill, zone and availability, books the confident calls, and hands the dispatcher a short review list — not a full board to build.
34 jobs assigned before the dispatcher sat down.
The review list is 3 deep — everything else is booked, sequenced and ready to dispatch.
Emergency & P1 work orders — assignment goes to the technician the moment it’s booked.
Routine work batches and releases on schedule — technicians get a plan, not a ping every few minutes.
02 Dispatch modes
Emergencies go now. Routine work goes in waves. You set the policy once.
On the schedule board, a booking dispatches when a dispatcher drags it — there’s no dispatch policy, just people moving bars on a Gantt.
FieldCamp gives dispatch modes: run Immediate for emergency work — the assignment goes to the technician the moment it’s booked — and Queue for routine work, batched and released at the times you set. An overtime cost guard holds any assignment that would push a technician past their hours, and flags it with the reason instead of quietly booking the cost.
03 A live board
A board is only useful if it’s telling the truth.
The native board needs a manual refresh for most changes — and Microsoft Learn note the schedule assistant’s availabilities don’t refresh with the board at all; you search again or refresh the browser.
FieldCamp’s board updates itself. Statuses flow in from the field — en-route, on-site, complete — with live GPS behind them. When a job runs long or an emergency lands, the dispatcher doesn’t discover it at 4 PM; the board proposes the re-plan in the moment, and nothing moves until it’s applied.
Source: Microsoft Learn — Use the schedule board in Field Service
04 What AI dispatch covers
Field service dispatch software, run as one system on top of D365.
AI assignment with per-job reasoning
Every work order matched to a technician by skill, location, availability and priority, returned with a confidence score and the reason — certified, distance, window fit — shown on the card.
Morning agent runs
The dispatch agent runs before the shift: unscheduled work orders read from your D365 FS data, confident assignments booked, edge cases handed to the dispatcher as a short review list.
Immediate & Queue dispatch modes
Emergency work dispatches the moment it's booked; routine work batches and releases at the times you set. Policy, not drag-and-drop.
Overtime cost guard
Any assignment that would push a technician past their hours is held and flagged with the reason — labor cost becomes a dispatch constraint, not a payroll surprise.
A board that updates itself
En-route, on-site and complete statuses flow in live with GPS behind them — no manual refresh, no rebuilding resource lists when the team changes.
Re-plans as proposals, not rewrites
When the day shifts, FieldCamp proposes the change — who moves, why, what it costs in drive time — and applies nothing until the dispatcher says so.
05 Where native dispatch stops
Written in the docs. Felt on every dispatch floor.
These aren’t opinions — they’re the dispatch limitations D365 Field Service teams report in Microsoft’s documentation and the Dynamics community, and the reason dispatch software exists as a layer on top.
The new schedule board has widely reported resource bugs
After the forced move to the new schedule board, teams report selected resources being hidden while non-selected ones show — so dispatchers remove all resources and rebuild the board whenever technicians or equipment change. A community moderator confirms these as widely reported, known issues requiring Microsoft Support escalation. FieldCamp's board doesn't need rebuilding: resources and their assignments are always what's actually on the schedule.
Source: Dynamics 365 Community — “The ‘New’ Schedule Board” thread
Dispatch is manual by design — one requirement at a time
The documented workflow is: select a requirement in the requirement pane, select Find availability to launch the schedule assistant, pick from the matching resources, book — then drag and drop to adjust. And the schedule assistant's availabilities don't refresh when the board refreshes; Microsoft's guidance is to search again or refresh the browser. FieldCamp assigns the whole day in one agent run, with the reasoning shown per job.
Source: Microsoft Learn — Use the schedule board in Field Service
Known behavior changes ship with the new board
the schedule-board documentation lists them: requirement-panel filters reset when you switch between the classic and new board, the Gantt view can scroll away from your selected resource when you reschedule a task, and for RSO organizations the optimization checkboxes now appear only on the RSO extension tab — which uses the classic board. FieldCamp gives dispatch one clean, predictable surface instead of two boards with different rules.
Source: Microsoft Learn — Known behavior changes with the new schedule board
06 The Microsoft cluster
Dispatch is one door. The whole cluster is here.
Every scheduling, dispatch and routing question a Dynamics 365 Field Service team asks has its own page — each one grounded in what the AI Dispatcher actually does.
Microsoft, Dynamics 365 and Dynamics 365 Field Service are trademarks of Microsoft Corporation. FieldCamp is an independent product and is not affiliated with or endorsed by Microsoft; references are for compatibility and comparison.
07 D365 Field Service dispatch FAQ
Dynamics 365 Field Service dispatch — questions, answered.
What is Dynamics 365 Field Service dispatch?
Dynamics 365 Field Service dispatch is the work of assigning work orders to bookable resources and managing those bookings through the day — natively done on the schedule board, one requirement at a time. FieldCamp's AI Dispatcher automates it on top of D365 FS: every work order assigned with a confidence score, dispatched by policy, on a board that stays live.
How does FieldCamp dispatch work orders on top of D365 Field Service?
It works with your D365 Field Service data: unscheduled work orders and bookable resources flow into FieldCamp's dispatch engine, the AI matches each job by skill, location, availability and priority, and dispatches per your policy — Immediate for urgent work, Queued waves for routine work. Dynamics 365 stays your system of record.
Do I have to replace the schedule board or leave Dynamics 365?
No. FieldCamp works on top of Dynamics 365 Field Service — no rip-and-replace, no migration project. You keep D365 as the system of record and add the AI dispatch layer that runs the board for you.
What are Immediate and Queue dispatch modes?
Immediate mode sends the assignment to the technician the moment a job is booked — built for emergency work. Queue mode batches routine assignments and releases them at the times you set, so technicians get a clean plan instead of a phone that pings all day. Both run with the overtime cost guard active.
Can it run morning dispatch automatically?
Yes — that's the agent run. Before the shift starts, FieldCamp reads the unscheduled work orders, assigns the confident calls and hands the dispatcher a short review list with per-job reasoning. The dispatcher starts the day approving edge cases, not building a board.
How is this different from the schedule board's Suggest resources and Book resources buttons?
Those buttons are Resource Scheduling Optimization features, in preview, and require the separately licensed RSO add-in — and for RSO organizations, the optimization checkboxes appear only on the RSO extension tab, which uses the classic board. FieldCamp is one dispatch layer: assignment, dispatch modes, overtime guards and a live board, with reasoning shown per job.
Does it help with the new schedule board's problems?
It sidesteps them. Teams on the new board report selected resources being hidden and boards needing full rebuilds when technicians or equipment change — confirmed in the Dynamics community as widely reported, known issues. FieldCamp's board is generated from the schedule itself, so there's nothing to rebuild.
Dynamics 365 Community — “The ‘New’ Schedule Board” thread →
Is it on Microsoft Marketplace?
Yes — AI Dispatcher by FieldCamp is available on Microsoft Marketplace, so it fits the way Microsoft-based organizations already evaluate and buy software.
What does it cost?
Book a demo and we'll walk you through it against your own dispatch day.
How do I get started?
Book a demo — we'll run the AI Dispatcher against a Dynamics 365 Field Service dispatch scenario like yours: your work orders, your technicians, your board.
Give your D365 board a dispatcher that never sleeps in.
Book a demo. Bring a real dispatch morning — the unassigned column, the emergencies, the board you keep rebuilding — and we’ll run it through the AI Dispatcher live.
No demo deck. Your Dynamics day, our dispatcher.