Why “Schedule Over Lower Priority” in Salesforce Field Service Still Needs Careful Design
In this Office Hours Insight session, Leigh-Anne Nugent and the group continue testing one of the trickier scheduling behaviors in Salesforce Field Service: how “schedule over lower priority” actually works in practice. The result is a much clearer picture of what is causing the behavior, what changes when Enhanced Scheduling & Optimization is enabled, and why the technically correct product behavior may still fall short of the customer experience a business actually wants.
LESSONS YOU CAN TAKE FROM THIS:
1. Sometimes the issue is not the feature, it is the rule setup around it
A major breakthrough in this session came from a small but important change: enabling the work rule option to pass empty values. That resolved the gap where arrival windows were being set for appointment slots, but the scheduled time was landing outside the expected slot behavior. It is a strong reminder that field service features often depend on surrounding rule configuration just as much as the headline capability itself.
2. Classic optimization and Enhanced Scheduling & Optimization do not behave the same
The team was able to confirm a meaningful difference between the two scheduling experiences. With Enhanced Scheduling & Optimization enabled, scheduling over a lower-priority appointment results in replacement behavior, the other appointment effectively drops off the board. With it turned off, the classic behavior allows the overlap the customer was expecting. That difference is not minor. It directly affects whether overbooking feels usable or disruptive.
3. Pinned or dispatched work changes what the platform will even offer
Another useful discovery was that once an appointment is dispatched or considered pinned, Salesforce no longer offers that slot for this kind of scheduling experiment. In other words, the booking logic is not only looking at priority. It is also looking at whether the appointment is still movable. That matters because businesses may assume overbooking is always available when, in reality, appointment state changes the available options significantly.
4. The product may work, but still not match the customer experience you want
This session lands on a smart design conclusion: yes, Salesforce can be made to overbook in some scenarios, but that does not necessarily mean it should be the final solution. In a healthcare-style use case, the group preferred a waitlist experience where patients are told the current slot is full but can opt in to an earlier opening if someone cancels. That creates a much cleaner customer experience than silently replacing or overlapping confirmed appointments.
KEY TAKEAWAYS:
A work rule setting like passing empty values can materially affect booking behavior.
Enhanced Scheduling & Optimization replaces appointments where classic behavior can create an overlap.
Dispatched and pinned appointments are treated differently during scheduling.
“Schedule over lower priority” can work technically while still creating a poor customer experience.
A waitlist design may be the better long-term solution when cancellations are common.
