Enhanced Scheduling and Optimization: switch now?

An existing Field Service org should move to Enhanced Scheduling and Optimization, but territory by territory and after a check of its data, not in one go. New orgs have the enhanced engine on for all territories by default anyway, and the new Scheduling Console only works with it. The switch brings higher limits, such as 250 skills per technician instead of 100. It also removes scheduling recipes and changes how several work rules treat empty fields. In my view the right order is: clean the data, rebuild the recipes, switch one pilot territory, compare proposals for four weeks, then switch the rest.

What is Enhanced Scheduling and Optimization?

Enhanced Scheduling and Optimization, often shortened to ESO, is the newer engine behind scheduling in Salesforce Field Service. It does the same job as the older engine: it reads the scheduling policy, filters out technicians with work rules, ranks the rest with service objectives and books a slot. How that decision works is covered in how much Field Service scheduling should be automatic.

The Summer ’23 release notes1 describe the enhanced engine as available for new users by default. The current Field Service guide2 says it plainly: new orgs have Enhanced Scheduling and Optimization enabled for all service territories, and existing orgs can switch all territories or enable it per territory.

So the question is only open for orgs that went live with the older engine. For them nothing changes automatically. The engine keeps running as before until someone decides to switch, and without a deadline that decision tends to get postponed.

Higher limits for skills and optimized appointments

The limits for Enhanced Scheduling and Optimization3 in Salesforce Help list the numbers. These are the ones that matter for a machine or plant builder:

Limit	Enhanced Scheduling and Optimization
Skills per service resource	250, compared with 100 on the older engine
Optimized service appointments	50,000 per rolling 24 hours or 500 per Field Service Scheduling licence, whichever is higher
Horizon for absences and appointment changes	30 days; changes beyond it get no travel time or lunch break update
Service territories per scheduled job request	100, or 1,000 with Dynamic Scaling

The skills limit is the one I would look at first. A service technician at a machine builder often carries skills per machine series, per control system, per safety training and per language. With 100 skills that gets tight in larger product ranges. With 250 there is room.

The 50,000 appointments are rarely the bottleneck. A service organisation with 45 technicians stays far below that, and the figure applies until you have more than 100 scheduling licences. Consumption can be checked in Setup under Company Information.

The 30-day horizon matters for planned maintenance. If dispatchers book annual maintenance visits two months ahead, those bookings sit outside the window where the engine updates travel time. That is fine as long as optimization rearranges the plan once the appointments come into range.

According to the considerations for Enhanced Scheduling and Optimization4, travel is calculated with point-to-point predictive routing, which needs map coverage in the regions where your technicians work. Optimization also needs no separate activation step, because it runs with a Platform Integration User.

What disappears and what behaves differently?

Two things go away. Scheduling recipes, the automations that certain events trigger to solve overlaps in the schedule, are not available. Salesforce Help names the Fix Schedule Overlaps automated flow as the replacement. Optimization Insights is replaced by the Optimization Hub. If your dispatchers rely on recipes today, the replacement has to be designed and tested before the switch, not after it.

Then there are work rules that give different results with the same data. The same Help article lists them.

For admins

Which work rules behave differently?

• Match Fields and Extended Match handle empty fields differently.
• Match Boolean is not applied if the Boolean field on the service resource is empty.
• Match Territory treats an appointment with an empty territory field as open to resources from all territories.
• Working territories: secondary territory memberships are handled differently.
• Match Skills gets an additional "at least one skill matches" option.
• Capacity-based resources lose support for absences and resource efficiency.
• In-day optimization has a different run time.

Most of these points have one thing in common: empty fields. An appointment without a territory, a resource without a value in a checkbox field, a work order with a missing match field. On the older engine these gaps may have been harmless by accident. On the new one they lead to different candidates. That is why the switch is first a data project, and why I would start with the checks from what data Field Service scheduling needs.

One change helps manufacturers directly. Appointments that violate a rule could not be optimized on the older engine. With the enhanced engine, optimization can find an acceptable slot for them or drop them from the schedule.

The new Scheduling Console needs the enhanced engine

Salesforce now has two dispatcher screens: the Classic Dispatch Console with the familiar Gantt, and the new Scheduling Console. According to Trailhead5, the Scheduling Console is available only with Enhanced Scheduling and Optimization.

That links two decisions that look separate. An org that stays on the older engine also stays on the Classic Dispatch Console. New console features, such as AI explanations for proposed slots or multiday jobs shown as one connected job in Winter ’27, then stay out of reach. Whether dispatchers should move now is covered in the Field Service Scheduling Console: move dispatchers now?.

Worked example: one pilot territory first

Assume a machine builder with 45 technicians in five service territories, Field Service live since 2021 on the older engine, four dispatchers and two scheduling recipes for late appointments. All numbers are assumptions to show the method.

1. 01

   Data check

   2 weeks

   A report lists appointments without a territory, resources with empty fields used in Match Fields or Match Boolean rules and technicians with secondary territory memberships. The result: 6 percent of open appointments have no territory, mostly breakdowns created from cases.

2. 02

   Rebuild recipes

   2 weeks

   The two recipes get rebuilt with the Fix Schedule Overlaps flow and tested in a full sandbox.

3. 03

   Pilot

   4 weeks

   One territory with nine technicians switches to the enhanced engine. Dispatchers note every proposal they change and why, as they did when automation was introduced.

4. 04

   Comparison

   If the share of changed proposals in the pilot territory is no higher than in the others, the remaining territories follow one per week.

The configuration for this, the territory setting, scheduling policies and work rules, consists of records rather than metadata. It belongs in the pipeline as described in the DevOps masterclass chapter on data and configuration, otherwise the tested sandbox state and production drift apart.

List appointments without a territory, work rules and recipes

Start with three lists: appointments without a territory, work rules that read fields which are often empty, and recipes in use. They show how much work the switch is. Then pick the territory with the cleanest data as the pilot. How the engine fits into dispatching as a whole is covered in the masterclass chapter on scheduling and dispatch.

Sources5

1. 1Summer ’23 release notes (opens in a new tab)resources.docs.salesforce.com
2. 2Field Service guide (opens in a new tab)resources.docs.salesforce.com
3. 3limits for Enhanced Scheduling and Optimization (opens in a new tab)help.salesforce.com
4. 4considerations for Enhanced Scheduling and Optimization (opens in a new tab)help.salesforce.com
5. 5Trailhead (opens in a new tab)trailhead.salesforce.com