FieldCamp AI Dispatch for Microsoft Dynamics 365 Field Service
Keep Dynamics 365. The AI Dispatcher integrates with Dynamics 365 Field Service to run the dispatch day.
Dynamics 365 Field Service scheduling is a strong system of record, and a hard place to run a live dispatch day. FieldCamp’s AI Dispatcher works on top of D365 FS: it assigns every work order by skill, location and availability with a confidence score, optimizes routes as the day changes, and dispatches the crews and multi-day projects native RSO can’t.
No rip-and-replace — Dynamics 365 stays your system of record. FieldCamp becomes the dispatch brain on top of it.
01 How it works on top of D365
You don’t replace Dynamics 365 Field Service. You give it a dispatch brain.
Dynamics 365 Field Service management already covers work orders, technicians and the schedule board. FieldCamp’s AI Dispatcher integrates with Dynamics 365 Field Service and takes over the part native tooling struggles with: deciding who does what, in what order, on which route, with the reasoning shown for every call it makes.
- 1
It reads your D365 work orders and resources
Your work orders, technicians, skills and availability flow into FieldCamp's dispatch engine, no rip-and-replace, no migration project. Dynamics 365 stays the system of record.
- 2
The AI assigns every job and shows its reasoning
Each work order is matched to the right technician by skill, location, availability and priority, returned as a confidence-scored recommendation. Run Auto (the AI books) or Assist (the AI proposes, you approve). The reasoning is shown per job, not a black box.
- 3
It optimizes the route and asks before it moves anything
The optimizer reorders each technician's visits to minimize travel time and total driving distance. It only reorders. It never silently adds or drops visits, and nothing changes until you Apply or Discard.
- 4
The schedule goes back, and the day stays live
The optimized plan returns to your operation, and FieldCamp keeps watching it, re-routing when an emergency lands or a job runs long, with live GPS tracking so dispatch always knows the truth on the ground.
Heating-certified · 2.4 mi from prior stop · window fits between confirmed visits · no overtime risk
02 Crews, pools & projects
The gap most teams find the hard way: RSO can’t schedule crews.
Microsoft’s own guidance for native Resource Scheduling Optimization is to leave Pool and Crew resources out of the optimization scope: they aren’t among the resource types the optimizer considers. If your work is multi-technician crews or multi-day, equipment-heavy projects, RSO simply isn’t built for it.
FieldCamp dispatches crews and multi-day projects natively: multi-technician teams, shared equipment coordination, and phased work that spans days, planned start to finish, not exceptions to work around.
Source: Microsoft Learn: Configure Resource Scheduling Optimization
03 Real-time rescheduling
RSO plans against yesterday’s roads. Your day doesn’t.
Native RSO optimizes against pre-calculated road and distance data — it can’t account for live traffic, closures or weather, and its optimization time grows as your resources and work orders do.
FieldCamp re-optimizes live. When an emergency lands, it finds the nearest qualified technician and re-sequences the day around it — returned in seconds as a plan you Apply or Discard, with every moved stop explained.
04 What the AI Dispatcher does
Everything a D365 dispatch floor needs. Nothing it has to babysit.
AI job assignment — Auto or Assist
Every work order matched by skill, location, availability and priority, returned with a confidence score. Auto books it; Assist proposes and you approve. The reasoning is shown per job either way.
Real-time route optimization
Reorders each technician's visits to minimize travel time and total driving distance, shows the route and the stats, and applies nothing until you Apply or Discard.
Crew & multi-day project dispatching
Multi-technician crews, shared equipment and phased multi-day work planned natively — the exact scheduling scenario Microsoft's guidance tells RSO users to exclude.
Dynamic rescheduling
An emergency call or an overrunning job triggers a re-plan: the nearest qualified technician, the day re-sequenced, confirmed windows held.
Dispatch modes & labor awareness
Run dispatch immediate or queued, with overtime management and cost tracking, so the schedule respects real labor cost — not just distance.
Live GPS tracking & operational agents
Real-time technician positions, stops, trips and daily summaries keep the board honest — while agents deliver end-of-day reconciliation and next-day capacity forecasts.
05 Where native scheduling stops
Where Dynamics 365 Field Service scheduling hits its limits. Documented, not just felt.
These aren’t opinions — they’re the limitations D365 Field Service teams report in Microsoft’s documentation and the Dynamics community, and the reason a third-party dispatch layer exists as a category.
Its priorities are rigid
RSO enforces optimization goals in a fixed order — the RSO FAQ is blunt: “minimize travel time” can't be set as the first priority without breaking scheduling. Real dispatch decisions are rarely that rigid. FieldCamp weighs objectives together and shows the reasoning per job, so you run it your way in Auto or Assist.
It's a separate add-on to buy, license and wire up
RSO is a separately-licensed add-in — one of the least-adopted in the Dynamics ecosystem — layered on the schedule board and scheduling assistant, and often stitched to Power BI, Power Apps and Power Automate to get real automation. FieldCamp works alongside D365 with no rip-and-replace: keep Dynamics as the system of record, add the dispatch intelligence on top.
Source: Microsoft Learn — Get Resource Scheduling Optimization
The board itself can get in the way
Teams have widely reported the new schedule board dropping or duplicating resources after the forced transition, optimization requests that hang until an admin resets the schedule, and edge cases — like a resource with multiple calendar breaks — quietly breaking optimization. FieldCamp gives dispatch a clean, predictable board and robust constraint handling.
Source: Dynamics 365 Community — “The New Schedule Board” thread
06 The Microsoft cluster
One pillar, many doors. Go as deep as your schedule does.
Every scheduling, dispatch and routing question a Dynamics 365 Field Service team asks has its own page here — 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 scheduling FAQ
Dynamics 365 Field Service dispatch, questions answered.
For setup and configuration questions, see the AI Dispatcher documentation.
What is FieldCamp's AI Dispatcher for Dynamics 365 Field Service?
Here's a quick overview: it's an AI scheduling and dispatch layer that integrates with Microsoft Dynamics 365 Field Service. It reads your work orders and technicians, assigns each job by skill, location, availability and priority with a confidence score, optimizes routes in real time, and dispatches crews and multi-day projects, capabilities the native Resource Scheduling Optimization (RSO) add-in doesn't cover. Dynamics 365 stays your system of record.
Do I have to leave Dynamics 365 Field Service to use it?
No. FieldCamp works on top of D365 Field Service: you keep Dynamics as your system of record and add AI dispatch on top, with no rip-and-replace and no migration project.
Is it on Microsoft Marketplace?
Yes. AI Dispatcher by FieldCamp is available on Microsoft Marketplace, with no separate implementation project. It fits the way Microsoft-based organizations already evaluate and buy software.
How is it different from Resource Scheduling Optimization (RSO)?
Native RSO plans against pre-calculated road data, is a separately-licensed add-in, enforces optimization goals in a rigid order, and doesn't support crew or pool scheduling. FieldCamp re-optimizes in real time, dispatches crews and multi-day projects natively, weighs objectives together, and shows its reasoning per job with a confidence score.
Can it schedule crews and multi-day projects?
Yes. Crew and multi-day project dispatching is native in FieldCamp. This is the scheduling scenario Microsoft's configuration guide tells RSO users to exclude from the optimization scope, and it's the single biggest gap teams discover when they push native scheduling.
Does it optimize routes?
Yes. The optimizer reorders each technician's visits to minimize travel time and total driving distance, returns the route with its stats, and only applies changes after you Apply or Discard. It never silently adds or removes visits.
Is it fully automatic, or human-in-the-loop?
Both, your choice. Run Auto and the AI books assignments itself, or run Assist and it proposes each assignment for your approval, with per-job reasoning and a confidence score shown either way.
How does it handle emergencies?
Dynamic rescheduling finds the nearest qualified technician and re-sequences the day around the urgent job, accounting for confirmed windows on the other stops, and returns the change as a plan you approve, not a silent rewrite of the board.
Can I see where technicians are?
Yes. Live GPS tracking shows real-time technician positions, movement history, stops, trips and daily summaries, so the dispatch dashboard reflects the truth on the ground.
What does it cost?
Pricing depends on your dispatch volume and technician count. Book a demo and we'll walk you through it against your own scheduling scenario.
How do I get started?
Book a demo. We'll show the AI Dispatcher running against a Dynamics 365 Field Service scheduling scenario like yours: your work orders, your technicians, your routes.
Is my data secure?
FieldCamp uses encryption in transit and at rest with role-based access control, and we're happy to walk your team through a security review call.
Run FieldCamp on top of your D365 — and watch your own schedule improve.
Book a demo. Bring a real dispatch day — the work orders, the crews, the routes RSO couldn’t untangle — and we’ll run it through the AI Dispatcher live.
No demo deck. Your Dynamics day, our dispatcher.