Field Service Scheduling Console: move dispatchers now?

Dispatchers should move to the Field Service Scheduling Console step by step: first a small group in one territory, then the rest once the functions they use daily are there. The Scheduling Console puts the Gantt, the appointment list and the map on one screen, explains proposed slots with AI and keeps the customisations of the Classic Dispatch Console. It only runs with Enhanced Scheduling and Optimization, and according to Salesforce the two consoles are not fully at parity yet. As of October 2026 I see no retirement date for the old console, so there is no reason to switch everybody on one day.

What is the Scheduling Console?

The Scheduling Console is the new dispatcher workspace in Salesforce Field Service. According to the Trailhead unit Get to know the Scheduling Console1, it opens as a tab in the Field Service app, where dispatchers also reach accounts and service resources. It is built on Lightning Web Components and uses server-side filtering and lazy loading, so it stays responsive with large data volumes.

The screen has three parts:

• Gantt. Service resources as rows, their appointments as blocks. Dispatchers filter resources by name, type or skill, move appointments, assign absences and widen the view to several days.
• Service appointment list. Open and scheduled appointments in a standard Salesforce list view with custom columns and filters. Appointments are dragged from the list onto the Gantt.
• Map. Resources and appointments in real time, with layers for planned routes, traffic and exact appointment locations, kept in sync with the Gantt and the list.

The old console now has a new name. According to a Salesforce knowledge article2, the managed package tab was renamed to Classic Dispatch Console with version 262 (Summer ’26), to separate it from the new Scheduling Console.

The new console explains its proposals

The biggest change for dispatchers is candidate search. According to the Trailhead unit Dispatch smarter with the Scheduling Console3, the console shows readable recommendations instead of numeric grades. A Why? next to a candidate gives an AI-generated explanation of why that slot was suggested.

That matters more than it sounds. In the Classic Dispatch Console a dispatcher sees a grade and has to guess which service objective drove it. An experienced dispatcher who overrides proposals because they do not trust the grade is exactly the pattern I describe in how much Field Service scheduling should be automatic. An explanation in plain words makes it easier to see whether the engine is wrong or whether data is missing.

Trailhead names further changes:

• Drag and drop from the list to the Gantt, also across two monitors.
• Global search for appointments across territories, date ranges and list filters, with results in a temporary list of up to 50 records.
• Hover details on appointments, resources and absences, without opening the record.
• Live updates when the list is synced with the Gantt’s territories, so no manual refresh.

For Winter ’27, Salesforce lists Scheduling Console Enhancements4: appointments that span several visits or days appear as one connected job and move with a single drag. For machine builders with commissioning or overhauls over several days, that is the most useful addition so far.

The Scheduling Console needs the enhanced engine

The first requirement is the engine. The Scheduling Console is available only with Enhanced Scheduling and Optimization. Orgs that went live on the older engine have to switch first, and that switch has its own homework: scheduling recipes disappear and empty fields are treated differently by several work rules. The details are in Enhanced Scheduling and Optimization: switch now?.

The second requirement is setup. According to Trailhead, the console is switched on automatically when Agentforce Field Service is enabled through Salesforce Go. Dispatchers still need access: in Salesforce Go an admin gives dispatchers Scheduling Console access and assigns the permission set that the system creates. That makes it easy to start with a small group, because only the users with the permission set see the new console.

What carries over, and what is still missing?

Trailhead calls the move low risk: customisations applied to the Classic Dispatch Console continue to work in the Scheduling Console, and the Gantt state and user settings carry over. I would still test every custom action and every Visualforce page in a sandbox, because custom code is where surprises show up first.

Both consoles are not identical yet. In a Trailblazer Community thread5 from May 2026, a customer reported after the Summer ’26 upgrade that colour palettes were missing and that the new console offered views from one day to one week, while the classic Gantt also had views such as Utilization and Long-Term. A Salesforce team member answered that both consoles are not 100 percent at parity yet and that these features are not forgotten, without a date.

For a manufacturer this is the important point. Dispatchers who plan annual maintenance weeks ahead or watch utilization across a whole territory work in exactly those long views. Dispatchers who mostly handle breakdowns for today and tomorrow barely miss them. Which group you have decides how fast the move can go.

Worked example: two dispatchers test first

The figures are assumed. A component maker with four dispatchers and three service territories already runs Enhanced Scheduling and Optimization. All numbers are assumptions to show the method.

1. 01

   Inventory

   1 week · admin and dispatchers

   The admin lists every customisation of the Classic Dispatch Console: custom actions, Visualforce pages, filters, colour rules. Each dispatcher writes down which Gantt views they use every day.

2. 02

   Pilot

   6 weeks · two dispatchers

   Two dispatchers get the permission set and plan one territory in the Scheduling Console. The other two stay on the Classic Dispatch Console for the remaining territories.

3. 03

   Weekly check

   weekly · pilot dispatchers

   The pilot dispatchers note what they could not do in the new console and had to do in the old one, and how often they used Why? to understand a proposal.

4. 04

   Decision

   If nothing on the list blocks daily work, the other two dispatchers follow. If long-range views are still missing, the planner for preventive maintenance keeps the Classic Dispatch Console for that task.

The note on Why? is worth collecting. If dispatchers use it often and then change the proposal anyway, the explanation points to missing data or a policy that does not fit, which is useful input long before any AI agent schedules on its own. Which agents work for dispatchers today is covered in AI agents in Field Service: what works today?, and the wider picture in the AI masterclass chapter on AI agents in manufacturing.

First step: check which engine you run

Check the engine first. If it is still the older one, the console question waits until the switch to Enhanced Scheduling and Optimization. If it already is the enhanced engine, give two dispatchers the permission set and let them plan one territory for a few weeks. Engine, console and policy owner are the three decisions of the masterclass chapter on scheduling and dispatch.

Sources5

1. 1Get to know the Scheduling Console (opens in a new tab)trailhead.salesforce.com
2. 2Salesforce knowledge article (opens in a new tab)help.salesforce.com
3. 3Dispatch smarter with the Scheduling Console (opens in a new tab)trailhead.salesforce.com
4. 4Scheduling Console Enhancements (opens in a new tab)trailhead.salesforce.com
5. 5Trailblazer Community thread (opens in a new tab)trailhead.salesforce.com