Configure Field Service Dispatch Operations

1. Plans the dispatch scenario and asks for approval before building. One run stopped at this step and never built anything.
2. Creates Field Service data: service resources, service territories, work orders and service appointments.
3. Reworks scheduling data by shifting appointments and work orders and fixing territory assignments, so the dispatcher view reads correctly.
4. Adds supporting pieces such as a dashboard component fed by Data 360 IoT data and a Data Capture Flow for the mobile app.
5. Turns on location tracking in the mobile settings, seeds heartbeat data on service resources, and deploys an Apex scheduler class and Scheduled Flows for location-based alerts.
6. Tests the result by generating alert records across every alert type.

When the scheduling console misbehaves, the next step is Diagnose Field Service Scheduling Errors.