The Exclude Technician from Geolocation Tracking permission allows disabling geolocation tracking for specific service resources by assigning them a permission set with this permission. Setting the Geolocation Update Frequency field to zero for contractors would not disable geolocation tracking, but would make it update less frequently. Unchecking the Geocoding field on the Contractor's profile or the Collect Service Resource Geolocation History field in Field Service Mobile Settings would not affect geolocation tracking, as these are not related settings. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_geolocation_tracking_permissions.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_geolocation_tracking_settings.htm&type=5

This option allows applying different prices for the same product based on the customer agreement, and avoids duplicating products that have standard prices. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_price_books.htm&type=5

Crew Management is a feature that allows creating and managing crews of multiple service resources who share the same service appointments[163]. The Preferred Resource service objective is ignored for active Crew Members because it only applies to individual resources and not crews[164]. Capacity-based scheduling is not supported for Service Crews because crews do not have capacity limits and can be assigned unlimited service appointments[165]. A service resource can be a member of multiple crews and can switch between them depending on their availability and skills[166]. Salesforce Field Service does not consider the Recommended Crew Size when assigning appointments because it only considers the Required Crew Size which indicates the minimum number of crew members needed for a service appointment[167]. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_limitations.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_crews_create_edit_delete.htm&type=5 https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment_requiredcrewsize.htm

This option allows tracking the return of a defective product and its replacement with a new one, if applicable. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_return_orders_overview.htm&type=5

Use all-or-none scheduling for related appointments is a setting in Field Service Settings that enables or disables the simultaneous scheduling of service appointments that have dependencies[232]. Dependency Type is a field on the Service Appointment object that defines the relationship between two service appointments such as Start After Finish, Start Before Finish, or Finish Before Start[233]. Same Resource and Same Day are fields on the Service Appointment object that indicate whether two service appointments with dependencies should be assigned to the same resource and scheduled on the same day[234]. Selecting the checkbox Use all-or-none scheduling for related appointments in Field Service Settings, setting the Dependency Type to Start After Finish and Same Day on the first service appointment in the dependency, and making sure the Same Resource and Same Day fields appear on the Service Appointments page layout would allow Universal Containers to ensure that a customer makes one appointment for the sales department, and another appointment for the service department, that should be handled on the same day, but should be created as separate appointments, where the Technician must complete one appointment before starting the next, and that these two appointments are scheduled together and in sequence by enabling simultaneous scheduling of dependent service appointments, defining the order and timing of the service appointments, and ensuring that the service appointments are assigned to the same resource and scheduled on the same day[235]. Creating a dependency between the two appointments and setting the start times to be the same would not work because it would not ensure that one appointment is completed before starting the next. Adding the Complex Work Visualforce page to the Service Appointments page would not work because it is not a feature of Salesforce Field Service. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_settings_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_appointment_dependencies_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_appointment_dependencies_create_edit_delete.htm&type=5