The Dispatcher Console assumes Field Service is enabled, technicians are configured, and at least one service territory is defined. Setup involves enabling the feature, assigning permissions, and configuring the console layout to fit your team''s workflow.
- Enable Field Service
Setup, then Field Service Settings, then Enable Field Service. The feature activates the underlying objects (Service Appointment, Service Territory, Work Order) and the Dispatcher Console.
- Assign the Field Service Dispatcher permission set
Setup, then Users, then assign the Field Service Dispatcher permission set to dispatch staff. This grants access to the console and the optimizer.
- Configure Service Territories
Setup, then Service Territories. Create territories matching your operational geography: city, region, or service zone. Each technician belongs to one or more territories.
- Add technicians as Service Resources
In the Field Service app, navigate to Service Resources and add each technician. Set their skills, territory assignments, working hours, and capacity. The optimizer uses these to match appointments to people.
- Open the Dispatcher Console
From the Field Service app, click Dispatcher Console. The Gantt, map, and appointment list load with today''s data. Drag and drop to assign appointments.
- Configure optimization policies
Setup, then Field Service Settings, then Optimization Policies. Define the objectives (minimize travel, respect SLAs, balance utilization) and the schedule horizon. The optimizer uses these when triggered.
Drag appointments onto technicians by hand. Best for small teams and dispatchers who know their crew.
Run the Lightning Schedule Optimizer to propose assignments. Best for large teams or complex scheduling constraints.
Run the optimizer for the baseline schedule, then manually adjust for edge cases. The most common production pattern.
Real-time: optimizer runs continuously as appointments change. Batch: runs nightly for the next day. Choose based on schedule volatility.
- Field Service is licensed separately. Service Cloud licenses do not include Field Service; check entitlements before deployment.
- Service Appointments and Work Orders are separate objects. Confusing them causes routing errors; the appointment is scheduled, the work order is the job description.
- The optimizer respects only what you configure. Forgetting to set a technician''s skill or territory leads to unfeasible assignments.
- The Dispatcher Console is browser-based and reasonably heavy. Slow internet or older browsers degrade the experience meaningfully.