Loading
Prepare for Email to Become the Default Login ExperienceRead More
Workforce Scheduling for Agentforce Public Sector
What’s Workforce Scheduling Optimization?

What’s Workforce Scheduling Optimization?

Workforce Scheduling optimization automatically generates the ideal schedule by applying your scheduling policy and appointment priorities. Optimization is relevant to field work only.

Required Editions

Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions

Workforce Scheduling offers three optimization types — Global Optimization, In-Day Optimization, and Resource Schedule Optimization (RSO). Each has a different scope, runtime, and best-fit situation. Choose the type that matches the scheduling problem you’re solving.

Optimization Types

Workforce Scheduling provides the tools to maintain schedule quality throughout the lifecycle of your service appointments. From initial creation through execution and closure, you have the flexibility to define the scope of optimization, whether it’s for a single service resource’s schedule, for an entire service territory, or for several service territories.

Global Optimization
Optimize your team’s schedule for one or more service territories across a specified range of days. You can configure it to run regularly in the background, for example, every night, or you can run it manually as needed via API. Global Optimization is the most thorough optimization type and the primary lever for long-term schedule quality. It rebalances the entire plan across the selected service territories against your scheduling policy, so the schedule stays aligned with your priorities and business goals as work is added, completed, and updated over time. Because the search space is large, Global Optimization takes the longest to run — schedule it during off-hours, when scheduling activity is quiet, so it can rebalance the schedule uninterrupted.
In-Day Optimization
Navigate last-minute schedule changes by rapidly optimizing your team’s schedule for one or more service territories on the day of service and the days that follow, via API. In-Day Optimization handles disruptions as they happen during the service day — cancellations, urgent same-day appointments, resources running late — by rebalancing the plan around the change while honoring any work that’s already in progress or dispatched. Because the runtime is capped at a few minutes, keep the date range to one or two days. In-Day Optimization needs to complete as quickly as possible, and more data means longer runtime — a tight scope keeps the run short. Speed matters because In-Day Optimization runs alongside live scheduling activity: urgent work coming in, dispatchers making changes on the Gantt. The faster the run finishes, the less it conflicts with those in-flight changes.
Resource Schedule Optimization (RSO)
Optimize an individual service resource’s schedule on the day of service. Use RSO when one resource’s schedule needs a reset — a shift change, a series of cancellations, or a long unexpected block of unavailability — without touching the rest of the team. The run honors the resource’s working hours, skills, and any pinned appointments.

Compare Optimization Types

Every optimization type uses your scheduling policy and the priority stored on each appointment. The policy’s work rules define which resource, time, and appointment combinations are valid, and its service objectives guide the engine toward a schedule that reflects your business goals — the objectives themselves define what “high quality” means. Appointment priorities matter when capacity is tight. If the engine can’t schedule every appointment, it favors the higher-priority ones over the lower-priority ones.

Type Scope Runtime Best For
Global Optimization One or more service territories, up to a 30-day date range Typically overnight (session timeout usually at least two hours) Rebalancing the whole schedule after new work lands, resources change, or policies are updated
In-Day Optimization One or more service territories, current day plus the day that follows A few minutes Recovering from same-day disruptions: cancellations, delays, resource callouts, jobs that run long
Resource Schedule Optimization A single service resource, a single day Seconds to a minute Handling changes like cancellations, fixing overlaps and filling gaps, without affecting the rest of the team
 
Loading
Salesforce Help | Article