Dispatcher Console
The Dispatcher Console is the central scheduling interface in Salesforce Field Service.
Definition
The Dispatcher Console is the central scheduling interface in Salesforce Field Service. Dispatchers use it to view, assign, and optimize service appointments across a team of mobile workers. The console presents work orders on a Gantt chart timeline, a map of technician locations, and a list of unassigned appointments waiting to be scheduled. From there, a dispatcher can drag appointments onto technicians, trigger an optimization run, monitor live status updates from the field, and respond to schedule disruptions.
Field Service (formerly Field Service Lightning) is one of Salesforce's Service Cloud add-ons, designed for industries with mobile workforces: home services, utilities, healthcare home visits, telecommunications, equipment maintenance. The Dispatcher Console is the cockpit; the Field Service Mobile App is the cab. Dispatchers see what is coming, what is in progress, what is delayed, and which technician is best positioned for the next appointment, all in one screen.
What the Dispatcher Console provides to a Field Service dispatcher
The three core surfaces: Gantt, map, and appointment list
The Dispatcher Console arranges three views. The Gantt chart shows each technician as a row with their scheduled appointments along a timeline; the dispatcher can drag appointments to reschedule. The map shows technician locations in real time alongside the addresses of pending and in-progress appointments. The appointment list shows unassigned work, grouped by territory or service type, ready to drop onto a technician.
Service appointments as the unit of work
In Field Service, a Service Appointment is the schedulable unit, distinct from a Work Order (the customer-facing job description) and Work Order Line Items (the tasks). The Dispatcher Console operates on Service Appointments: assigning, rescheduling, splitting, and merging them. Each appointment carries a status (Scheduled, Dispatched, In Progress, Completed, Canceled) that drives both the Gantt color and the routing engine''s behavior.
The optimizer and how scheduling decisions get made
Field Service ships with an optimizer (Lightning Schedule Optimization) that can assign appointments based on a configurable set of objectives: minimize travel time, maximize technician utilization, respect skill requirements, honor SLAs. The dispatcher runs the optimizer manually or on a schedule. The result is a proposed schedule; the dispatcher reviews and accepts (or overrides) before the changes go live.
Real-time status updates from the field
Field technicians use the Field Service Mobile App on Android or iOS. Status changes (arrived on site, started work, paused for lunch, completed) flow back to the Dispatcher Console in real time through the Salesforce platform. The dispatcher sees a paused technician and can decide to reroute the next appointment to a different person. The communication is bidirectional: dispatcher updates push to the mobile app and vice versa.
Capacity, skill, and territory matching
Each Service Appointment has required skills, required equipment, and a territory. Each technician has a skill set, a service territory, and a current capacity. The optimizer and the dispatcher both filter by these constraints: a plumbing appointment in San Francisco only routes to technicians with the Plumbing skill assigned to the San Francisco territory. Mismatches surface as warnings before the schedule commits.
Customer notifications and the appointment experience
Field Service can send automated notifications to the customer at each status change: Your technician is on the way (when status transitions to Dispatched), Your technician has arrived (Arrived on Site), Your service is complete (Completed). These notifications use Marketing Cloud or Email Studio templates and are configured per service type. The Dispatcher Console shows whether notifications are being sent for each appointment.
Common dispatcher workflows in practice
Morning: review yesterday''s completion rate and today''s pending appointments. Mid-morning: handle no-shows and reschedule. Afternoon: respond to mid-day disruptions (equipment failures, customer cancellations) by rerouting nearby technicians. End of day: run optimization for tomorrow''s schedule based on confirmed appointments. These workflows are why the Dispatcher Console is the dispatcher''s home screen for an entire shift.
How to set up the Dispatcher Console for a Field Service deployment
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.
Trust & references
Straight from the source - Salesforce's reference material on Dispatcher Console.
- Dispatcher Console for Field ServiceSalesforce Help
- Field Service Schedule OptimizationSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is the Dispatcher Console?
Q2. What does Dispatcher Console show?
Q3. What pairs well with Dispatcher Console for routine assignments?
Discussion
Loading discussion…