A Dispatcher at Universal Containers has just been informed that one of their field employees,...

For this scenario, Salesforce Field Service should use a Resource Absence plus Fix Overlaps. Recording the sickness as a Resource Absence accurately removes the technician ' s availability. Fix Overlaps can then identify appointments that conflict with the absence and attempt to reschedule them to suitable resources under scheduling rules.

In scheduling design, it is important to distinguish eligibility from preference. Work Rules filter candidates that do not satisfy hard constraints such as territory, availability, skills, or boolean conditions, while Service Objectives rank the remaining options. Dispatcher Console actions then use that policy logic to place, move, or dispatch appointments in a controlled way.

The alternatives address different parts of the Field Service model. Changing the global policy to High Intensity does not model the absence, and manually dragging or calling customers creates avoidable administrative work before the scheduling engine is given a chance to resolve the disruption.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Scheduling and Optimization — Resource Absence; Fix Overlaps; disruption management.