A confirmed December delivery

Microsoft confirmed on 18 December that Copilot Summary and Update were available that day in the new Field Service mobile experience, which remained labelled Preview. An administrator had to enable the capabilities in Field Service Settings. That timing matters: the November announcement described a planned December release, while the December post documented that teams could start using it.

Copilot can summarize a work order before a visit and propose form changes from a technician's text or speech after the job. Examples include completing a booking, closing service tasks and recording consumed products. Every proposed change is shown to the technician, who can exclude or accept it. Human review is therefore built into the workflow rather than added outside the system.

Product boundaries inform management

The preview could update booking status and times, mark tasks complete, consume estimated products, and complete services and service tasks. Microsoft also stated that updates were limited to forms in the new mobile interface. Managers should identify local fields, mandatory controls and integrations that sit outside that scope before beginning a pilot.

The release connects field service, automation and AI with collaboration between technicians and the back office. Faster input has little value if inventory, billing or the next shift receives incomplete records. A pilot should compare completeness before and after, count suggestions that users edit or reject, and test whether speech works in the real operating environment.

Organize adoption around the work order

Start with one job type that has a clear data model and a small technician group. Agree who reviews exceptions and retain an easy route to manual entry. Treat the pre-visit summary and the post-job update as separate uses because their value and risk can differ.

Management should also monitor elapsed time from completed work to approved work order, the share of complete product lines and the number of back-office corrections. This ties the assessment to the full delivery chain. The December release offers a concrete way to move documentation closer to the work, with an explicit check before the information becomes part of the company's operating record.

Training should use realistic technician language and show what the system does not understand. When one instruction affects time, product and status, the team should verify that all three proposed changes are visible before approval. This provides better evidence about the interaction between the language model and the structured work order. Support staff can record recurring expressions that lead to errors and improve guidance without concealing preview limitations. Technicians should take part in the review because they can judge whether the mobile flow works in the physical setting and customer situation where the record is created.

Sources

Microsoft Dynamics 365 Blog, “Experience the power of Copilot in Dynamics 365 Field Service in the mobile application,” 18 December 2023

Microsoft Dynamics 365 Blog, “Streamline Field Service Operations with new Copilot capabilities,” 15 November 2023

Join the discussion

Where do misunderstandings most often occur between planning and delivery in your team? Share an example from an assignment.