Introduction

Completed

A service organization maintains air-conditioning equipment at customer sites. Its dispatchers need to assign appropriately skilled technicians. Technicians need clear work instructions and parts information. Service managers need accurate records for review and billing.

Dynamics 365 Field Service connects those responsibilities through shared service records, scheduling, and a mobile app. Configuration determines whether the team receives useful work details, realistic scheduling information, and the right access to customer data. It also establishes the source information that Copilot uses to summarize service work.

Connect the records behind a service visit

Before configuring the app, distinguish the records that describe a customer, the reusable work details, the individual job, and its assignment:

Record Purpose
Account Identifies a customer organization or service site. The service account identifies where service takes place; the billing account identifies who pays.
Customer asset Identifies an individual item of equipment, such as an air-conditioning unit, rather than every unit of the same model.
Work order Describes an individual service job, including its location, tasks, products, services, and customer or equipment references.
Work order type Classifies the overall job, such as repair, inspection, or installation, and can define required information when a work order is created.
Incident type Provides a reusable template for a service request or procedure, including its products, services, tasks, and skill requirements.
Service task type Defines a reusable checklist step. A work order service task is the step the technician completes on an individual job.
Resolution Describes a reusable corrective action, such as Replace air filter, that technicians can select to describe a visit's outcome.
Bookable resource Represents a person, equipment, or another resource that the organization schedules.
Resource requirement Describes what a job needs for scheduling, such as skills, duration, location, and a time window.
Booking Assigns a resource to work at a particular time. Creating a work order doesn't by itself confirm a technician appointment.

For the air-conditioning organization, Repair is a work order type and Reduced airflow is an incident type for a recurring complaint. A work order identifies the particular customer site and equipment needing attention and uses the template's relevant work details. Its resource requirement describes the scheduling need; a booking assigns a technician to a visit. The technician completes the visit's service tasks and selects a resolution that reflects the actual outcome.

Field Service uses Microsoft Dataverse to store its business records. Universal Resource Scheduling supplies the scheduling capabilities and is installed with Field Service.

Follow the work from request to review

Plan configuration around the service process rather than treating each setting as an isolated choice. Confirm where requests originate, which details make a job ready for dispatch, and who approves completion and charges.

Stage What the team needs Configuration that supports it
Create the work A clear customer request and scope of service. Customer accounts, work order types, reusable incident templates, products, and services.
Schedule and dispatch Suitable resources, realistic travel estimates, and appointment windows. Resource working hours, skills, locations, territories, and scheduling parameters.
Deliver the service Accessible instructions and a way to capture the work performed. Service tasks, mobile access, and appropriate security roles.
Review and close Reliable completion details and an agreed billing process. Statuses, resolutions, pricing, and account defaults.

These stages depend on one another. A dispatcher can't make a reliable assignment from missing skills or an incorrect service address. A technician's completion notes also need to reach the records that service managers review. Start with a representative request and check whether standard records and forms support it before introducing custom columns or processes. Identify who owns decisions about pricing, service procedures, and dispatch rules. For a guided setup sequence, see Get started with Field Service.

Prepare both application access and scheduling data. A technician's user account provides app access; the bookable resource supplies working hours, skills, and start and end locations. Creating one doesn't configure the other. Check usable latitude and longitude values for service and resource locations, not just completed address fields. Before enabling automatic geocoding or maps, confirm approval for sharing addresses and coordinates with the provider. See Set up bookable resources and Enable location and map settings.

Each app user needs an appropriate license, environment access, and security roles. Use the predefined roles as a starting point:

Security role Intended responsibility
Field Service - Resource Perform assigned work and capture service details in the mobile app.
Field Service - Dispatcher Schedule jobs and assign work to frontline workers.
Field Service - Administrator Configure Field Service and manage operational settings.
Field Service - Inventory Purchase Manage inventory, purchasing, and product returns.

Scheduling skills don't grant application access. Security roles govern access to tables and records; column-level security profiles add control over sensitive columns. Test access with the intended dispatcher and resource roles, not only an administrator account. For setup and permissions, see Set up users, licenses, and security roles and Security roles and column-level security profiles.

Plan AI and scheduling capabilities

Copilot work order summaries help a dispatcher or technician understand a work order and its related records. Depending on the work order stage and summary configuration, the summary can surface status, required parts, activities, and asset service history.

Use the following overview to identify capabilities that support your service process and the configuration decisions behind each one:

Capability Purpose Configuration decision
Copilot work order summary Summarize accessible work order and related data. Which fields and relationships provide useful service context?
Schedule assistant Recommend resources and times that match a requirement. Are requirements, skills, working hours, and locations accurate?
Resource Scheduling Optimization Automatically schedule and optimize work within a configured scope. Is the separately licensed add-in configured for the intended work?
Scheduling Operations Agent (preview) Suggest schedule changes interactively or run configured batch optimizations. Which scope, goals, and review or automatic-application settings govern the changes?

The Scheduling Operations Agent supports interactive suggestions that a dispatcher reviews before applying. Its batch plans can instead apply changes automatically when configured to do so. For current behavior, see Universal Resource Scheduling overview and Scheduling Operations Agent overview (preview).

Important

Scheduling Operations Agent is a preview feature. Preview features aren't intended for production use and can have restricted functionality.

Copilot summaries use the generating user's permissions and aren't saved as permanent service history. Review their source references before acting on them, and correct incomplete source records rather than expecting AI to repair the underlying data.

Work order summaries require a paid Field Service environment and aren't available in trials. Check regional availability and feature settings; web and mobile enablement have different requirements. Use the default summary as a baseline before choosing custom inputs. Work order and booking summary configurations are separate. See Enable work order summary with Copilot.

Validate one service flow before expanding

Use one representative repair to test the configuration from request through review:

  1. Check that the job contains the customer site, equipment, planned tasks, parts, and estimated labor.
  2. Confirm that the dispatcher can find the requirement and assign a suitable resource within the intended time window.
  3. Verify that the technician can access the instructions and capture actual work details in the mobile app.
  4. Check that the reviewer receives useful completion information and the expected customer charges.
  5. Compare a Copilot summary with its source records under the intended user's permissions.

Resolve missing data, access problems, and unclear review responsibilities before applying the same configuration more broadly. The remaining units develop this foundation through products and pricing, work classifications, reusable tasks, resolutions, customer defaults, operational settings, and Copilot summary configuration.