Created with AI.
The planning assistant finds available resources that actually match the requirements of the assignment, instead of requiring the planner to search through the schedule board manually. It does not make the decision—but it eliminates options that are not feasible anyway.
You can start from the work order or from the schedule board, where the job appears as unscheduled. Both routes lead to the scheduling assistant, which works with the resource requirement associated with the work order.
The assistant displays resources that are available during the time window and meet the skill requirements. If you get no results, it is almost always due to one of three reasons: the time window is too narrow, the skill requirement is too strict, or no one has registered working hours that cover the period.
A technician may appear available on paper and still be the wrong choice because they would have to drive across the entire city. The assistant shows the travel distance—use it. This is also the argument for full optimization once the number of daily jobs increases.
When you confirm, a booking is created with the status Scheduled, and the work order's system status automatically changes from Unscheduled to Scheduled. The technician can see the assignment in the Field Service mobile app.
The schedule board color-codes the work order statuses, so you can see who is on their way, who is working, and who has finished. This is the tool for handling deviations throughout the day—provided that the technicians actually update their status as they go.
If an assignment is delayed, the booking can be moved on the board. Remember that a work order can have multiple bookings, and the work order is not considered closed until all of them have been completed or cancelled.
Ask a question or share what helped you.

Customer Service | Article
WEM MCP tools enabled time-off requests, shift swaps and shift bids in Service Agent. Administrators could enable each tool for a role, team or pilot group.

Automation | Article
Microsoft replaced twice-yearly release waves with continuous roadmap publication. Customer processes needed to track status from development through rollout to launch.

Customer Service | Article
Sales and Service Agent became generally available in Microsoft 365 Copilot. Dynamics described MCP actions across sales, service, field work and projects.

Customer Service | Article
Service Agent became generally available across Dynamics 365 and Microsoft 365. Workforce Engagement Management connected demand, staffing and quality work.

Sales | Article
Gartner found nearly five hours saved per seller each week, but many organisations did not reinvest the time. Dynamics wave 1 described connections across customer insight, sales, service and field work.

Field Service | Article
Microsoft published April news for manufacturing, Power Platform, Planner and Power BI. Together, the releases show how automation and analytics can support field work when project accountability, data quality and human control are clear.
Do you have a question or experience to share?
Be the first to contribute.