A field service company in Manchester has 35 technicians covering Greater Manchester, Lancashire and Cheshire. Every morning, dispatchers review new jobs, check engineer availability and assign appointments. Some repairs need specialist skills. Others involve equipment that has already been visited several times.
The pressure continues after an engineer reaches the customer. Technicians need to check previous repair notes, record parts and labour, update service tasks and close the work order. If an engineer calls in sick, the dispatcher has to rearrange appointments without disrupting the rest of the day's schedule.
Table of Contents
Copilot in Dynamics 365 Field Service brings AI assistance into these activities. It helps users understand work orders, find service information and complete supported updates. Microsoft's Scheduling Operations Agent also helps dispatchers assess scheduling options. Each capability has different licensing, setup and availability requirements.
Quick Answer
Copilot helps technicians, dispatchers and service managers work with service records and complete supported tasks.
Capabilities include work order summaries, natural-language assistance, mobile updates and AI-assisted scheduling.
The standard Field Service licence costs £80.70 per user/month. Resource Scheduling Optimization costs an additional £23.10 per resource/month. Both prices exclude VAT and assume annual payment.
Accurate asset records, technician skills, job requirements and booking rules are essential for useful AI recommendations.
What Is Copilot in Dynamics 365 Field Service?
Copilot brings Microsoft's AI assistance into the Field Service application. It works with information already held in the system, helping users review records and carry out selected tasks.
A technician preparing for a repair might need to check an asset's history, previous work orders and parts used during an earlier visit. A work order summary brings relevant information together. A dispatcher dealing with an unavailable engineer has a different requirement: finding suitable resources and rearranging bookings. The Scheduling Operations Agent addresses that scheduling work.
Neither capability replaces the underlying service records or scheduling configuration. Their usefulness depends on how well the organisation has set up Field Service.
Key Copilot Features in Dynamics 365 Field Service
1. Work Order Summaries
A work order summary changes according to the job's lifecycle stage. An unscheduled job needs different information from one that has been completed or cancelled.
| Work order stage | Information highlighted |
|---|---|
| Unscheduled | Work requirements and planning information |
| Scheduled | Booking, site, asset and previous service details |
| In Progress | Current job status and relevant service history |
| Completed or Posted | Costs, prices and applicable invoice details |
| Canceled | Core work order and financial information |
The summary can draw on related bookings, notes, activities, products, services and service tasks. Administrators can configure the tables and fields used.
Summaries are generated when requested rather than saved as permanent replacements for work order records. User permissions determine which information is accessible. In UK environments, administrators must enable the feature because it is disabled by default.
2. Natural-Language Assistance
The Copilot side pane lets Field Service users ask questions about information in the application. A service manager investigating a repeat repair, for example, can ask about related service activity rather than manually searching through several records.
The response is useful for an initial review, but the original work order remains the source of truth. Dates, parts and repair outcomes should be checked before approving a warranty claim or making a customer commitment.
3. AI-Powered Work Order Updates
After replacing a faulty pump, a technician needs to record the work performed, enter the parts used, complete service tasks and update the booking.
The AI-powered work order update feature lets technicians describe supported changes using text or speech in the new Field Service mobile experience. Copilot suggests updates to fields such as booking status, times, service task completion and product line details. The technician reviews and confirms the changes.
This feature is in public preview. It requires administrator enablement, a paid Field Service environment and the supported mobile experience. It does not update every work order field.
4. Form-Fill Assistance and Inspection Templates
Form-fill assistance suggests values for blank fields using available context. This includes information from previous app activity, text or images copied through Smart Paste, and uploaded files. Suggestions remain optional and are saved only after the user accepts them.
Inspection template creation uses PDFs or images to produce draft digital inspection templates. An administrator can edit the generated template before publishing it.
There is a regional restriction: inspection template creation remains in preview and is currently unavailable in UK-hosted Dynamics 365 and Power Platform environments.
How Does the Scheduling Operations Agent Work?
A dispatcher has to consider more than technician availability when assigning a job. Skills, territories, working hours, promised arrival times, job duration and existing appointments all affect the decision.
The Scheduling Operations Agent evaluates selected resources, unfulfilled requirements and existing bookings against configured scheduling goals. These goals combine objectives, such as reducing travel or completing high-priority work, with constraints that determine which resources are eligible.
For the Manchester company, an engineer calling in sick could leave four appointments without a suitable resource. The dispatcher can ask the agent to suggest changes across the selected schedules and review the proposed assignments before applying them.
Microsoft's preview documentation sets these optimisation limits:
| Optimisation type | Resources | Jobs | Time window |
|---|---|---|---|
| Interactive | Up to 5 | Up to 120 | 72 hours |
| Batch | Up to 50 | Up to 4,000 | 14 days |
The job count includes existing bookings and open requirements. Batch optimisation can run on demand or on a recurring schedule.
Scheduling Operations Agent Limitations
The agent does not support every resource or scheduling arrangement in Dynamics 365 Field Service. Its current limitations include:
Unsupported resource types: Equipment, Pool and Facility resources are not supported.
Requirement groups: Jobs that need multiple resources scheduled together cannot be optimised through the agent.
Multiday requirements: Requirements involving multiple days and related requirement detail records are not supported.
Fulfilment preferences: The agent does not consider a requirement's fulfilment preferences when suggesting a schedule.
The agent also doesn't support fields specific to Resource Scheduling Optimization (RSO). Businesses using these scheduling arrangements should assess compatibility before planning a pilot. The agent is still in preview, so its documented limits can change.
Scheduling Operations Agent vs Resource Scheduling Optimization
These are separate scheduling capabilities with different licensing arrangements.
Scheduling Operations Agent uses AI to suggest interactive or batch schedule changes. Dispatchers can review recommendations, and batch plans can be configured for automatic application. It is currently a preview feature and uses consumption-based billing.
Resource Scheduling Optimization (RSO) is a separately licensed Dynamics 365 add-on. It automatically creates optimised resource schedules using configured objectives and constraints.
The two should not be treated as interchangeable. In particular, the Scheduling Operations Agent does not support RSO-specific fields.
What Should Businesses Check Before Using AI Scheduling?
The agent depends on resource and requirement records being properly configured. Three areas deserve attention:
Resource records: Working hours, breaks, start and end locations, territories and technician characteristics. If an engineer has gained a refrigeration qualification but the resource record hasn't been updated, the scheduling process cannot use that information.
Requirement records: Job duration, priority, promised arrival windows, territory and required skills. An incorrect job duration can disrupt the rest of the day's schedule.
Booking rules: Which existing appointments can move, which must remain fixed and which statuses are eligible for optimisation.
Dispatchers should also review optimisation goals. A recommendation that reduces travel time but moves a priority customer outside their promised arrival window is not a successful outcome.
How Much Does Dynamics 365 Field Service Cost?
Microsoft's UK pricing separates user licences, resource scheduling and agent consumption.
| Cost component | UK list price or billing model |
|---|---|
| Field Service licence | £80.70 per user/month |
| Contractor licence | £38.40 per user/month |
| Resource Scheduling Optimization | £23.10 per resource/month |
| Standard Copilot assistance | Included for supported capabilities |
| Scheduling Operations Agent | Consumption-based Copilot Studio messages |
The licence prices are paid yearly and exclude VAT. The Contractor licence has a more limited feature set. The RSO price of £23.10 per resource/month is based on Microsoft's single-tenant pricing.
The Scheduling Operations Agent uses Copilot Studio messages for consumption-based billing. Microsoft calculates the messages used by an optimisation request according to the number of resources included. An optimisation involving more resources therefore consumes more capacity.
Businesses can use prepaid message capacity or pay-as-you-go billing. Prepaid capacity is used first when both models are configured. Pay-as-you-go requires an active Azure subscription linked to the Power Platform environment.
Standard Copilot assistance, the RSO add-on and Scheduling Operations Agent consumption are separate cost considerations. Using RSO does not automatically mean a business needs to purchase it to explore the agent.
See Microsoft's UK Field Service pricing for current licence details.
Preparing for a Copilot Implementation
Before enabling these features, review the information and processes they will use. A useful readiness assessment should cover five areas.
Work order and asset data: Check whether previous repairs, parts, service tasks and asset details are recorded consistently. Identify missing fields and incomplete notes.
Technician resources: Compare resource records with actual skills, certifications, territories, working hours and availability.
Scheduling configuration: Review requirement characteristics, job duration, priorities, booking statuses, fixed appointments and optimisation goals.
Mobile workflows: Examine the forms technicians use after a visit. Identify fields that cause repeated entry or are regularly left incomplete.
Licensing and security: Confirm UK feature availability, required licences, message capacity, security roles and administrator settings.
Start the pilot with a small group of technicians and dispatchers. Test work order summaries against previous jobs, check mobile update suggestions and run scheduling optimisations in review mode. Compare preparation time, record completion and manual schedule changes with the original process.
How Dynamics Square UK Can Help
Dynamics Square UK provides Dynamics 365 Field Service implementation and consulting services. For businesses considering Copilot, the first step is to assess whether their existing setup is ready.
The readiness assessment should produce five practical outputs:
| Assessment deliverable | What it covers |
|---|---|
| Data quality findings | Missing asset details, incomplete work orders and inconsistent service records |
| Scheduling review | Resource characteristics, requirement settings, booking restrictions and optimisation goals |
| Feature suitability matrix | Copilot capabilities that fit the business, including UK availability and preview status |
| Licensing breakdown | User licences, RSO requirements and estimated agent message consumption |
| Pilot recommendation | Suitable users, test scenarios, approval controls and success measures |
These findings give the business a clear view of what needs correcting, which features are suitable and whether RSO or the Scheduling Operations Agent fits its scheduling process.
For an initial discussion, prepare ten completed work orders, a sample of technician resource records and two examples of difficult scheduling changes. These will give the assessment a practical starting point.
Contact Dynamics Square UK to discuss a Field Service Copilot readiness assessment.
Frequently Asked Questions
It is Microsoft's AI assistance within Field Service. It supports work order summaries, natural-language assistance and selected updates. The Scheduling Operations Agent separately helps dispatchers optimise schedules.
It doesn't support Equipment, Pool or Facility resources, requirement groups, multiday requirements or fulfilment preferences. It also has limits on resources, jobs and optimisation windows.
No. The agent is a preview capability that uses consumption-based billing. RSO is a separately licensed add-on for optimising resource schedules.
The standard Field Service licence includes supported Copilot assistance. The Scheduling Operations Agent uses Copilot Studio messages, which are billed through prepaid capacity or pay-as-you-go.
No. Work order summaries are disabled by default in UK environments. Inspection template creation is currently unavailable in UK-hosted environments, and some capabilities remain in preview.
No. It assists with information and administrative tasks. Technicians remain responsible for repairs and confirming service records, while dispatchers manage customer commitments and scheduling decisions.