MICROSOFT PRODUCT CAPABILITIES
Get the right work to the right technician.
Dynamics 365 Field Service supports service delivery from the initial request through scheduling, on-site work, and completion. Dispatchers and technicians work from the same job information, while asset history helps explain what needs attention.
Work orders and assets
Record the job, required tasks, products, services, and customer equipment. Keep service history attached to the asset.
Scheduling and dispatch
Match work to resource availability, skills, and location using scheduling tools. Resource Scheduling Optimization is a separate add-on for automated optimisation.
Technician mobile working
Provide job details, inspections, notes, and completion updates through the mobile application. Configure offline profiles for work with limited connectivity.
Parts and service agreements
Track parts used on jobs and support recurring work from service agreements, keeping delivery connected to operational records.
Design for the actual service territory
Device use, offline coverage, skills, travel, and scheduling rules matter as much as the work order. Establish the mobile and optimisation requirements when choosing the deployment.
Put it to work with Braintree.
Braintree connects the service process to your assets, stock, customer records, and financial systems, and tests the workflow with dispatchers and technicians before rollout.
Microsoft product guidance
From scheduled visit to service record
The field process extends beyond dispatch. Job status, costs, signatures, photographs and checklists can form a connected record of the work, giving operations teams a clearer basis for follow-up and customer communication.
✓
Define the workforce, service territories and scheduling rules.
✓
Map customer assets, maintenance requirements and service agreements.
✓
Confirm the mobile devices, offline data and inventory connections needed.
✓
Agree which evidence is captured before a work order is completed.
01
The work order connects the service visit
Field Service fits organisations that send people to install, inspect, maintain or repair customer equipment. The core operating record is the work order: it connects the service request, location, customer asset, tasks and resources needed to perform the work. That is a different responsibility from simply keeping a list of customer enquiries.
An illustrative equipment-repair workflow begins with a reported fault. The dispatcher checks the asset and service history, plans the visit and assigns a suitable technician. The technician records the work, parts and supporting evidence. A manager reviews completion, decides whether another visit is required and passes the agreed information into billing. The design must define what each status means and who may change it.
02
Scheduling requires more than an available person
Resource scheduling can consider skills, location and availability, but the quality of the result depends on the information maintained about the team and the work. An engineer with a free afternoon may still lack the certification, parts or travel time needed for a particular job. Those constraints must be represented in the scheduling process.
The practical evaluation should include a planned visit, an emergency job, an absent technician and a job that cannot be completed. It should demonstrate how the dispatcher sees the change, how the technician receives updated information and how the customer is informed. Optimisation features and their licence requirements must be scoped separately from assuming that every scheduling function is included.
03
Offline needs an explicit data profile
Microsoft documents a mobile offline profile that controls which tables and records reach the device and how they synchronise. The technician needs the relevant customer, work order, booking, asset and supporting information before losing connectivity. Downloading everything is not the same as designing an appropriate offline working set.
Test the exact mobile experience being proposed. Microsoft’s documentation notes that a newer mobile experience does not support offline work, while the supported offline experience uses configured profiles. Features available online may also behave differently offline. The acceptance test should include first synchronisation, work without signal, captured evidence and reconnection, not just a connected-office demonstration.
04
Define the service record and the financial handover
Braintree can configure the workforce, service territories, work-order process and integrations around your service model. Inventory and finance connections need clear ownership: recording that a part was used is only useful if the stock and billing process interprets it correctly.
Map customer assets, maintenance agreements, work types and required on-site evidence.
Define resource skills, availability, scheduling rules and escalation responsibilities.
Confirm mobile devices, supported offline experience and the data profile needed in the field.
Test consumption of parts, job review, follow-up work and the handover to billing.
BEFORE YOU DECIDE
