---
title: "Dispatch"
url: "https://fieldcamp.ai/ai-dispatcher/salesforce/dispatch/"
date: "2026-08-17T09:21:27+00:00"
modified: "2026-08-21T12:30:30+00:00"
type: "WebPage"
resource: "https://fieldcamp.ai/ai-dispatcher/salesforce/dispatch/"
timestamp: "2026-08-21T12:30:30+00:00"
author:
name: "Jeel Patel"
word_count: 2070
reading_time: "11 min read"
summary: "Salesforce Field Service · AI Dispatch"
description: "AI dispatch for Salesforce Field Service. Automate appointment assignments, optimize dispatching, control overtime, and track technicians with FieldCamp."
keywords: "AI Dispatch for Salesforce Field Service"
language: "en"
schema_type: "WebPage"
---
# Dispatch
_Published: August 17, 2026_
_Author: Jeel Patel_
Salesforce Field Service · AI Dispatch
# AI dispatch for the Salesforce Field Service Dispatcher Console — *the board works itself.*
**The Salesforce Field Service Dispatcher Console is the nerve center — and the bottleneck: drag-and-drop the Gantt, chase rule violations, book one appointment at a time.** FieldCamp’s AI Dispatcher works with your Salesforce Field Service data — it assigns every service appointment by skill, location and availability with a confidence score and the reasoning, dispatches in Immediate or Queue mode, and keeps the board true as the day moves.
[Book a demo](https://calendly.com/jeel-fieldcamp/30min)Works on top of Salesforce Field Service. Part of FieldCamp’s [AI Dispatcher](/ai-dispatcher/).
Work the console — clear the appointment queue, keep every scheduling rule green. Dispatch board — West Bay territory FieldCamp live Salesforce FS · synced 7:55 AM Appointment queue 2 SA-4480 P1 · 2h Panel repair · Bay Point
needs a resource
SA-4482 P3 · 45m Meter swap · Harbor
needs a resource
AI-assigned 2 SA-4471 96% Fiber install · West Bay
DMDiego M.certified · 4 min away · window fits
SA-4473 92% Imaging PM · Mercy Clinic
PNAmara O.skill match · same site as SA-4470
**Rule violation resolved · Match Time** — SA-4478 (Filtration service) fell outside its arrival window. FieldCamp rebooked to 11:00, window restored, Renee C. still nearest. 0 broken windows. Diego M. en route → SA-4471 · Fiber install, West Bay ETA 9:12 · live GPS 28 assigned · 1 rule violation resolved · 2 in queue — reasons shown Review 2 Dispatch board ✓Salesforce Field Service
**The console, minus the busywork** — FieldCamp clears the appointment queue and keeps every scheduling rule green. The Dispatcher Console stays exactly where your team already works.
Dispatcher ConsoleScheduling PoliciesWork RulesGet CandidatesService Appointments
01 The console today
## The nerve center of field operations — *and where the day gets stuck.*
The Dispatcher Console pairs an appointment list with a Gantt and a map on one screen. Dispatchers assign, reschedule and drag appointments onto resources, run optimization, and [clear rule violations flagged in-line](https://docs.fieldcamp.ai/ai-dispatcher/how-ai-dispatcher-works-under-the-hood) — travel conflicts, skill mismatches, an appointment outside its arrival window — one at a time.
In Salesforce’s own Dreamforce 2025 Field Service keynote, the console is called **“the nerve center of your field operations”** — and the same keynote puts a dispatcher at **up to 15 minutes to schedule a single appointment**, with technicians losing **over a day a week** to admin. At scale, that’s days of dispatcher time gone to drag-and-drop and rule-clearing.
Sources: [Dreamforce 2025 Field Service keynote](https://www.youtube.com/watch?v=y1lg9rwTQgk) · [Salesforce Help — Work in the Dispatcher Console Gantt](https://help.salesforce.com/s/articleView?id=sf.pfs_gantt.htm&language=en_US&type=5)
Dispatcher Console — West Bay Salesforce Field Service manual SA-4480Panel repair · Bay Point unscheduled SA-4478Filtration service · Harbor rule: travel conflict SA-4473Imaging PM · Mercy Clinic rule: skill mismatch SA-4471Fiber install · West Bay scheduled 9:00 Every placement is a drag onto the Gantt, then clear whatever rule it trips — one appointment, then the next. 12 unscheduled · 4 rule violations · one at a time Drag to place Diego M. — day plan · West Bay AI pass complete Auto mode 8 9 10 11 12 1 2 3 4 5 Before — manual console4471447344784482 After — FieldCamp AI pass44714473447844824480 Idle gaps between jobs closed and SA-4480 pulled from the queue — every move carries its reason, nothing applied until you approve. 2h 45m idle recovered · 1 more appointment fits · 0 broken windows Approve plan 02 The board, worked for you
## FieldCamp works the board *so the dispatcher doesn’t have to.*
Instead of a person dragging bars across the Gantt to close idle gaps, FieldCamp reads the day from your Salesforce Field Service data and makes the calls: each service appointment matched to the right resource by skill, location, availability and priority — with a confidence score and the reason shown on the card.
Run it in **Auto** to book the confident calls and hand back a short review list, or **Assist** to approve each one. The AI pass compresses the wasted windows between jobs — the dispatcher starts the day approving decisions, not building a board from an empty Gantt.
03 Dispatch modes & guardrails
## Emergencies go now. Routine work goes in waves. *You set the policy once.*
On the console, an appointment is dispatched when a dispatcher decides to send it — there’s no dispatch policy, just people moving work on a Gantt.
FieldCamp gives dispatch modes: run **Immediate** [for emergency work](https://fieldcamp.ai/ai-dispatcher/emergency-job-handling/) — the assignment reaches the technician the moment it’s booked — and **Queue** for routine work, batched and released at the times you set. [An overtime cost guard](https://fieldcamp.ai/ai-dispatcher/overtime-management/) holds any assignment that would push a resource past their hours and flags it with the reason, instead of quietly booking the cost.
Emergencies dispatch instantly. Everything else goes out in the 7:00 and 12:30 waves. Dispatch modes policy active applies to all territories Immediate Emergency & P1 service appointments — the assignment reaches the technician the moment it’s booked.
Queue waves · 7:00 AM / 12:30 PM Routine work batches and releases on schedule — technicians get a plan, not a ping every few minutes.
PM visits Inspections Installs Recurring routes **Overtime cost guard** — hold any assignment that pushes a resource past 8.0 hrs; flag with the reason instead of booking the cost. 8.0 hrs Changes apply to the next dispatch — nothing in flight moves Save policy 04 Inside AI dispatch
## Field service dispatch software, *run on top of Salesforce.*
### AI assignment with per-appointment reasoning
Every service appointment matched to a resource by skill, location, availability and priority, returned with a confidence score and the reason — certified, distance, window fit, same site — shown on the card.
### Auto & Assist modes
Auto books the confident calls and hands the dispatcher a short review list; Assist proposes every assignment for a one-click approve. The console stays; the deciding gets automated.
### Immediate & Queue dispatch
Emergency work dispatches the moment it’s booked; routine work batches and releases at the times you set. Dispatch by policy, not by drag-and-drop.
### Overtime cost guard
Any assignment that would push a resource past their hours is held and flagged with the reason — labor cost becomes a dispatch constraint, not a payroll surprise.
### Rule violations resolved, not just flagged
Travel conflicts, skill mismatches and out-of-window appointments don’t sit on the board as red flags — FieldCamp proposes the fix and shows why it holds.
### A live board with GPS
En-route, on-site and complete statuses flow in live with GPS behind them. When a job runs long, FieldCamp proposes the re-plan in the moment and applies nothing until the dispatcher says so.
05 What the board gains
## A console is only as good *as the decisions on it.*
These aren’t opinions — they’re grounded in Salesforce’s own documentation and the way dispatch teams actually work the console, and the reason an AI dispatch layer earns its place on top.
01
### The dispatcher has to trust the schedule to run it
On the new engine, an optimization request doesn’t show a progress percentage from the Gantt, and Optimization Insights — the view that explained a run — isn’t available. Analysts describe the optimizer as a black box dispatchers hesitate to trust. FieldCamp shows the reasoning on every appointment in plain language, so the person working the console can see why a job landed where it did and override in one click.
Source: [Salesforce Help — Considerations for Enhanced Scheduling and Optimization](https://help.salesforce.com/s/articleView?id=service.pfs_enhanced_available_considerations.htm&language=en_US&type=5)
02
### Crews look scheduled, but the humans inside them aren’t
Per Salesforce’s documentation, when an appointment is scheduled to a crew the individual members’ absences and efficiencies aren’t considered, and a crew resource can’t be [capacity-based](https://fieldcamp.ai/ai-dispatcher/salesforce/capacity-planning/). The board says the crew is booked; reality on the truck can be different. FieldCamp schedules real crews as real people — each member’s availability, absences and skills count.
Source: [Salesforce Help — Considerations for Scheduling Service Crews](https://help.salesforce.com/s/articleView?id=service.pfs_service_crews_considerations.htm&language=en_US&type=5)
03
### Salesforce’s own AI dispatch is a metered layer on the stack
[Agentforce for Field Service](https://fieldcamp.ai/ai-dispatcher/salesforce/vs-agentforce-scheduling/) is real and shipping — but it’s a paid, consumption-metered add-on that rides the same rules-and-weights engine underneath, stacked on Dispatcher and Technician licenses. FieldCamp is one AI dispatch layer built for the dispatch outcome — assignment, dispatch modes, overtime guards and a live board — on top of the Salesforce Field Service data you already keep.
Source: [Salesforce — Agentforce for Field Service announcement](https://www.salesforce.com/news/stories/agentforce-for-field-service-announcement/)
06 Nearby in the cluster
## Dispatch is one door. *The whole cluster is here.*
Every scheduling, dispatch and routing question a Salesforce Field Service team asks has its own page — each one grounded in what the AI Dispatcher actually does.
[Salesforce Field Service](/ai-dispatcher/salesforce/)→
The pillar — AI scheduling & dispatch on top of SFS
[AI Scheduling](/ai-dispatcher/salesforce/scheduling/)→
Auto-assign every appointment beyond policy weights
[Route Optimization](/ai-dispatcher/salesforce/route-optimization/)→
Live-condition routing, not predictive-historical
[Dynamic Rescheduling](/ai-dispatcher/salesforce/dynamic-rescheduling/)→
Recover the day when a job runs long or cancels
[AI Dispatcher](/ai-dispatcher/)→
The dispatch brain — schedule, route, recover
[Workload balancing](https://fieldcamp.ai/ai-dispatcher/workload-balancing/)→
Spread the day evenly across the team
[Equipment dispatching](https://fieldcamp.ai/ai-dispatcher/equipment/)→
Route work by the tools and parts it needs
Salesforce, Salesforce Field Service, Agentforce and Field Service Lightning are trademarks of Salesforce, Inc. FieldCamp is an independent product and is not affiliated with or endorsed by Salesforce; references are for compatibility and comparison.
07 Salesforce Field Service dispatch FAQ
## Salesforce Field Service dispatch — questions, answered.
**What is the Dispatcher Console in Salesforce Field Service?**
The Dispatcher Console is the dispatcher’s cockpit in Salesforce Field Service — an appointment list, a Gantt chart and a map on one screen. Dispatchers assign, schedule, reschedule and drag-and-drop service appointments onto resources, run optimization, switch scheduling policies, and clear rule violations flagged in-line. FieldCamp’s AI Dispatcher works that board for the dispatcher: every appointment assigned with a confidence score and reasoning, dispatched by policy, on a board that stays live.
[Salesforce Help — Work in the Dispatcher Console Gantt →](https://help.salesforce.com/s/articleView?id=sf.pfs_gantt.htm&language=en_US&type=5)
**Why does it take up to 15 minutes to schedule one appointment?**
That figure comes from Salesforce’s own Dreamforce 2025 Field Service keynote, describing the manual work of placing a single appointment on the console — checking candidates, drag-and-dropping onto the Gantt, and clearing rule violations. FieldCamp assigns the whole day in one AI pass with the reasoning shown per appointment, so the dispatcher approves decisions instead of building each one by hand.
[Dreamforce 2025 Field Service keynote →](https://www.youtube.com/watch?v=y1lg9rwTQgk)
**How does FieldCamp dispatch on top of Salesforce Field Service?**
It works with your Salesforce Field Service data: unscheduled service appointments and service resources flow into FieldCamp’s dispatch engine, the AI matches each appointment by skill, location, availability and priority, and dispatches per your policy — Immediate for urgent work, Queued waves for routine work. Salesforce stays your system of record.
**Do I have to leave the Dispatcher Console or replace Salesforce?**
No. FieldCamp works on top of Salesforce Field Service — no rip-and-replace, no migration project. You keep Salesforce as the system of record and add the AI dispatch layer that works the board for you.
**What are Immediate and Queue dispatch modes?**
Immediate mode sends the assignment to the technician the moment an appointment is booked — built for emergency work. Queue mode batches routine assignments and releases them at the times you set, so technicians get a clean plan instead of a phone that pings all day. Both run with the overtime cost guard active.
**How is this different from Agentforce for Field Service?**
Agentforce for Field Service (Salesforce’s agentic AI layer, part of what’s now branded Agentforce Field Service) is real and shipping, but it’s a paid, consumption-metered add-on that rides the same rules-and-weights scheduling engine underneath and is stacked on Dispatcher and Technician licenses. FieldCamp is one AI dispatch layer built for the dispatch outcome — assignment with reasoning, dispatch modes, overtime guards and a live board — on top of the Salesforce data you already keep.
[Salesforce — Agentforce for Field Service announcement →](https://www.salesforce.com/news/stories/agentforce-for-field-service-announcement/)
**Does it handle rule violations like travel conflicts and skill mismatches?**
Yes. Where the console flags rule violations in-line for a dispatcher to clear one by one, FieldCamp proposes the fix — rebook to a valid window, reassign to a resource with the right skill and shortest travel — and shows why the fix holds before anything is applied.
[Salesforce Help — Work in the Dispatcher Console Gantt →](https://help.salesforce.com/s/articleView?id=sf.pfs_gantt.htm&language=en_US&type=5)
**Does it work with Field Service Lightning (FSL)?**
Yes. Field Service Lightning (FSL) is the legacy name for the same product now called Salesforce Field Service. FieldCamp’s AI Dispatcher works with your Salesforce Field Service data whichever name your org still uses.
**What does it cost?**
Book a demo and we’ll walk you through it against your own dispatch day.
**How do I get started?**
Book a demo — we’ll run the AI Dispatcher against a Salesforce Field Service dispatch scenario like yours: your service appointments, your resources, your console.
## Give your Dispatcher Console a dispatcher *that works the board for you.*
Book a demo. Bring a real dispatch morning — the appointment queue, the rule violations, the Gantt you keep dragging — and we’ll run it through the AI Dispatcher live.
[Book a demo](https://calendly.com/jeel-fieldcamp/30min)No demo deck. Your Salesforce day, our dispatcher.
---
_View the original post at: [https://fieldcamp.ai/ai-dispatcher/salesforce/dispatch/](https://fieldcamp.ai/ai-dispatcher/salesforce/dispatch/)_
_Served as markdown by [Third Audience](https://github.com/third-audience) v3.6.1_
_Generated: 2026-08-21 12:30:30 UTC_