Certified Field Service Consultant: Salesforce Field Service Consultant

These two ways allow dispatching the appropriate technicians based on customer feedback, as they allow defining which resources are preferred or avoided by customers or accounts.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_resource_preferences.htm&type=5

Assets are records that represent products or equipment that customers have purchased or installed[174]. Related Assets are records that track the relationships between assets such as parent-child or swap[175]. Product Requests are records that track the products or parts that are requested, transferred, or returned for a service appointment[176]. Adding the Related Asset related list to the Asset Page and configuring the Product Request object would allow Universal Containers to track the Asset lifecycle when equipment has been swapped out by creating related asset records for swapped assets and creating product request records for transferring or returning assets[177]. Adding the field history tracking related list to the Asset Page would not track the Asset lifecycle when equipment has been swapped out. Field history tracking is a feature that allows tracking changes to specific fields on an object over time[178]. Configuring the Asset Relationship object would not track the Asset lifecycle when equipment has been swapped out. Asset Relationship is an object that defines the types of relationships between assets such as parent-child or swap[179].

Reference: https://help.salesforce.com/s/articleView?id=sf.asset.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_related_assets_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_product_requests_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_related_assets_swap.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.field_history_tracking.htm&type=5 https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_assetrelationship.htm

Service Resources are records that represent the people or equipment that perform field service tasks[53]. Permission Set Licenses are licenses that grant users access to specific features such as Field Service Dispatcher Console or Field Service Mobile App[54]. Creating one service resource and assigning the relevant permission set license would allow an employee at Universal Containers to perform both dispatcher and technician roles using one record and one license. Creating two skills records and assigning them to service resources record would not affect their roles or access to features. Skills are records that define specific abilities or qualifications that service resources have[55]. Creating two service resources and assigning them to the employee would create duplicate records and require two licenses for one employee. Creating one service resource and assigning the technician and dispatcher role would not work because roles are not fields on the service resource object.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_permission_set_licenses_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_skills_overview.htm&type=5

This option allows tracking each door lock as a unique product item with its own serial number and inventory location.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_product_items.htm&type=5

Enabling the sharing features in the Field Service settings in the Setup menu allows sharing dispatched service appointments with assigned resources regardless of the private record access model in sales, support, and field service organizations[50]. Creating a user territory for the technicians' primary and secondary territories would not ensure that they have access to the service appointments dispatched to them. Creating a process to change the owner of the service appointment to the assigned technician would not work if multiple resources are assigned to the same service appointment. Configuring a sharing rule to share dispatched service appointments with the assigned resource would not work if multiple resources are assigned to different crews or teams.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_sharing_overview.htm&type=5

Time sheet entries are records that track the time spent by a service resource on a work order or a work order line item[28]. Time sheet entries can be associated to work order line items or work orders using lookup fields[29]. Assigned resources are records that assign a service resource to a service appointment[30]. Service resources are records that represent the people or equipment that perform field service tasks[31]. Time sheet entries cannot be associated to assigned resources or service resources directly.

Reference: https://help.salesforce.com/s/articleView?id=sf.fs_time_sheets_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_time_sheet_entries_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_assigned_resources_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_service_resources_overview.htm&type=5