Preparation is therefore a strong place to apply AI. Microsoft’s Dynamics 365 Field Service documentation describes Copilot summaries of work orders. The next step is to connect that useful brief to the parts and permissions that determine whether the visit can finish.
Field note: identify the cause of the second visit
Different failures deserve different remedies. A missing spare needs a planning change; an uncertain diagnosis needs technical support. If site access failed, clearer customer coordination matters more than another document in the knowledge base.
Follow the service chain back from a repeat visit. Establish what information was missing and when it was needed to change the decision. An incorrect asset identifier can undermine both a concise summary and an apparently sensible parts recommendation.
This gives a copilot a precise purpose. It should bring the evidence that changes preparation into the dispatcher’s working view. The resulting job record can carry the verified asset identity and the unresolved question that needs attention before the appointment is promised.
Field note: put the evidence in the preparation brief
Choose a common job type and examine recent repeat visits. Identify which information would have changed preparation and whether it was available before dispatch. This creates a practical basis for deciding what a copilot should retrieve or flag.
Design the preparation brief to bring together the asset history, reported symptoms and relevant approved guidance. It should preserve uncertainty. If the description is inconsistent with the asset record, the brief should prompt verification rather than quietly selecting the most plausible interpretation.
The dispatcher or technician needs a way to inspect the sources. For consequential instructions, an attractive summary is insufficient. The service should point to the applicable approved procedure and make its revision clear. It should not invent a repair step to fill a gap in the records.
The prepared technician’s working day
Picture a technician opening tomorrow’s first job. The brief shows the asset’s repair history, the likely fault and the relevant approved procedure. A compatible spare is reserved, access has been confirmed and the remaining diagnostic question is visible. The technician can check the source before accepting the preparation.
That is the service standard worth designing for on every visit. The system connects the likely job requirement to available skills and parts before the appointment is confirmed. Dispatch gains a view of readiness, allowing it to resolve a missing dependency while there is still time to change the plan.
Begin with advice to the planner. A proposed assignment should explain the relevant constraints and any assumptions that remain unverified. The planner can then assess the trade-off between speed, travel and the likelihood of completing the work.
Where limited execution later becomes appropriate, the system should use established booking permissions and check that the transaction completed. An uncertain response should lead to verification, not repeated booking attempts. The customer should receive only a commitment that the operating system has accepted.
Field note: the completed job improves the next one
Technicians often leave with information that would help the next visit. Use a copilot to prepare a service record from permitted notes, with the person who performed the work checking the final account. The record needs to distinguish the observed fault from the suspected cause and the work actually completed.
This is also an opportunity to improve the knowledge base. Repeated discrepancies between guidance and field conditions should reach an owner who can review the approved material. Adding more text without that responsibility can make retrieval harder rather than more useful.
Evaluate the effect over complete jobs. Include repeat visits, correction effort and the time spent reviewing the assistant's output. The completed record should improve preparation for the next appointment, giving the team a growing body of checked operating knowledge.
Let technicians shape the next release
The technician’s corrections are valuable engineering input. If a recommended part repeatedly proves unsuitable, route that observation to the owner of the compatibility record. If the guidance misses a recurring fault, give the technical specialist a clear way to update the approved material.
We expect the strongest copilots to improve through this working relationship. Technicians receive a better preparation brief, while their checked findings improve the service the next colleague receives. Supervisors can see whether the organisation is becoming better at completing jobs, rather than simply faster at documenting them.
Investigate the repeat visit
This quarter, review one repeat-visit pattern with a dispatcher and an experienced technician. Establish which missing decision caused the return, then test the preparation brief against that gap.
Bring those job records to a NectarGlobal AI opportunity evaluation so the team can define the first field-service improvement worth proving.