Copilot chat in the Field Service web app

What it does

A side pane in the Field Service web app where dispatchers and technicians ask questions in natural language about work orders, bookings, accounts and related records. It answers from Dataverse data the signed-in user can already see, and it's the same launch point that the Scheduling Operations Agent hooks into.

Key facts

Generally available and enabled by default in Field Service environments. No separate licence — it comes with Dynamics 365 Field Service.
Users need the Field Service - Dispatcher or Field Service - Resource security role to see the Copilot icon in the app header.
The View Prompts library ships with starter prompts such as listing work orders for a service account, who is booked on a work order, and which products were used. Users can type free-form questions too.
Answers are constrained by the user's security roles. Two people asking the same question can legitimately get different answers, and that is by design rather than a bug.
If the tenant and the environment sit in different Azure regions, cross-region data movement has to be enabled or Copilot returns nothing.
Customising the chat through Copilot Studio is in preview. Microsoft ships a pre-configured agent named Copilot in Power Apps - Field Service that you extend with knowledge sources (websites, files, SharePoint) and custom topics that can call flows, connectors and Dataverse plug-ins.
Separately, Microsoft 365 Copilot can be surfaced in model-driven apps, including Field Service. That path is read-only over Dataverse, isn't available on the Power Apps mobile app, and needs a Dynamics 365 Enterprise or Premium licence — with a Microsoft 365 Copilot licence required for anything beyond Dataverse.
Data Loss Prevention policies that block the Dataverse or HTTP connectors will silently break Copilot responses. The icon still appears; the answers don't.
Regional and language coverage is governed by the Copilot International Availability Report, not by Field Service's own availability.
Selecting or @mentioning an agent inside the Microsoft 365 Copilot pane stops it querying Dataverse unless the agent is configured for it.

When to use / skip

Leave it on for dispatchers. Answering "which of Bob's bookings run past five today" without building a view is genuinely useful, and it costs nothing to have available. It is a productivity nicety, not a workflow, so treat it that way in the scoping conversation.

Where consultants get burned is promising it as a replacement for reporting or for advanced find. It is not deterministic, it doesn't aggregate reliably, and it won't build the client a KPI. If a business question has a right answer that someone will be measured on, put it in a view, a chart or Power BI, not in a chat pane.

The Copilot Studio customisation path deserves a firm "not yet" on most delivery projects. It's preview, it introduces a second product to govern and support, and it drags Copilot Studio licensing and ALM into a project that was scoped as Field Service. If the client genuinely needs a knowledge-grounded assistant across their manuals and SOPs, that's a separate workstream with its own budget, not a checkbox at the end of a Field Service rollout.

Skip it altogether — or at least hide it — for clients in a region the availability report doesn't cover, or where the security model is so heavily tailored that answers will vary wildly by user and generate support tickets.

Configuration decisions

Which roles actually get Copilot. It's on by default, so the real decision is whether to disable it at app level for any user group.
Whether to seed the prompt library expectations in training, or let people discover free-form questions and complain about the results.
Whether to go anywhere near Copilot Studio customisation in this phase, and who owns the agent afterwards.
Whether Microsoft 365 Copilot in the model-driven app is also in scope, which brings a separate licensing conversation.
How DLP policy is written, since the Field Service Copilot depends on connectors that a restrictive tenant policy will block.
Whether cross-region data movement needs enabling, which is an environment-level decision with its own data residency implications.

Gotchas

The most common support ticket is "Copilot gives me nothing" and the cause is almost always DLP or cross-region data movement, not the feature itself. Check both before raising anything with Microsoft.
Users read a confident-sounding answer as authoritative. Because answers are security-trimmed, a dispatcher with narrow access can be told there are no matching work orders when there are plenty.
The Copilot icon disappearing usually means it's been disabled at app level or the user lost the dispatcher/resource role — not that the environment lost the feature.
Copilot Studio customisation being preview means no production support and no guarantee the extension surface survives unchanged into GA.
The Field Service Copilot pane and Microsoft 365 Copilot in model-driven apps are different things with different licensing. Clients conflate them constantly, and so do proposals.
Nothing here works offline, which matters if you assumed parity with the mobile app experience.

Consultant notes

Demo it with the prompt library open. Free-form demos go wrong in front of an audience, and the starter prompts are there precisely because they behave.
Tell the client plainly that this is assistive, not a reporting tool, and get that in writing before UAT so nobody logs "Copilot gave the wrong number" as a defect.
Check DLP with the tenant admin during environment setup, not during UAT. It's a five-minute check that saves a week.
If the client asks about grounding Copilot in their own documentation, scope it as a separate Copilot Studio piece with its own licence and owner rather than absorbing it.
Before go-live, confirm the region and language against the availability report, and spot-check answers under a restricted dispatcher role rather than as a system administrator.

Worth revisiting when Copilot Studio customisation of the model-driven chat reaches general availability.