Managing Scheduling and Optimization28% of the exam
Dispatch strategies: drip feed and auto-dispatch
Choose between dispatching from the console, an Auto Dispatch scheduled job and drip feed; configure job territories, horizon and mentions, set drip feed rates per territory, and predict which memberships, statuses and events each mechanism uses.
Given a scenario, determine the appropriate dispatch strategy for an organization.
~7 min read · 6 practice questions ·
What the exam expects
- Recommend manual dispatch, an Auto Dispatch scheduled job or drip feed from how often the schedule changes and who should trigger dispatching.
- Configure a dispatch scheduled job: territories, run schedule, filter criteria, horizon, notified user and the Chatter mention option.
- Set the drip feed default and override it for one service territory.
- Predict what triggers the next drip-fed appointment and which appointments are eligible.
- Explain which territory memberships a dispatch job uses and which status it sets when it dispatches.
Key terms:
- Dispatch: sending a scheduled appointment to its resource, which moves it to the status mapped for "Service appointment is sent to its resource" (Dispatched by default).
- Auto Dispatch scheduled job: the provided job, editable under Field Service Settings, Dispatch, Scheduled Jobs, that dispatches appointments on a schedule.
- Drip feed: dispatching that keeps a set number of appointments in each worker's queue and sends the next one only when one finishes.
- Job horizon: the number of days in advance the job dispatches.
- Primary and relocation memberships: the service territory membership types a dispatch job considers.
Key facts
Settings location
- Detail
- Field Service Settings, Dispatch: Drip Feed and Scheduled Jobs
Job inputs
- Detail
- Territories, schedule, filter criteria, horizon, notified user
Resource selection
- Detail
- By territory membership, primary and relocation only
Status set
- Detail
- Scheduled to Dispatched, or the mapped custom statuses
Chatter mention
- Detail
- Optional; not supported for an automated process user
Drip feed override
- Detail
- A territory field overrides the default value
Drip feed trigger
- Detail
- Queue appointment becomes Canceled, Completed or Cannot Complete
Drip feed and jobs
- Detail
- Every scheduled job respects the drip feed value
Permissions
- Detail
- FSL Admin, FSL Dispatcher or Auto-Dispatch Service Resources permission set
Console naming
- Detail
- Scheduling Console replaces the Classic Dispatch Console as of Summer '26
- Why does drip feed reduce confusion when schedules change often?
- When does disabling drip feed require more work?
- Which user receives the job-run notification?
- What can start an async sharing job after every appointment status change?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Agentforce Field Service and Operations Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 38 lessons of the Agentforce Field Service and Operations Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (6 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both