field-service-consultant Sample Questions & Answers

The Service Resource Skill object is the junction between a Service Resource and a Skill. It includes Start Date and End Date fields specifically for time-based qualifications like certifications. By populating these fields, the 'Match Skills' work rule will automatically check not only if the technician has the skill, but also if the Service Appointment's date falls within the valid date range of the certification. This is the standard, out-of-the-box way to handle expiring skills without needing custom automation.

Salesforce Field Service Maintenance Plans are designed to handle this exact scenario. A single Maintenance Plan can have multiple Maintenance Work Rules associated with it. To meet the requirement, the consultant should create one rule based on time (recurrence period of 6 months) and a second rule based on usage (tracking the mileage field on the Asset). The system will then generate a Work Order when either the time-based or usage-based threshold is met first.

The 'Get Candidates' action is specifically designed for this purpose. It evaluates the selected Service Appointment against the available Service Resources and the active scheduling policy. It then presents the dispatcher with a ranked list of suitable technicians, showing their travel time and how well they match the policy's rules and objectives. This allows the dispatcher to make an informed, manual assignment decision. The 'Schedule' action typically attempts to schedule automatically without presenting a list of choices first.

Product Consumed records the use of a part on a Work Order, which is the trigger for decrementing inventory.

Product Item tracks the quantity of a specific Product at a specific Location (like a technician's van). This is where stock levels and thresholds are managed.

Product Request is the object used to formally request the movement or replenishment of inventory between locations, such as from the depot to a van.

The header of a record's detail page in both the Salesforce mobile app and the Field Service mobile app is controlled by the object's Compact Layout. To change the fields displayed for the Work Order in this context, the consultant must modify the Work Order object's Compact Layout and ensure it is assigned as the primary compact layout for the relevant user profiles. The Service Appointment page layout controls the detail section of the page, not the compact header.

This is false. By default, the optimizer can move appointments with a 'Dispatched' status. To prevent a dispatched (or any other status) appointment from being moved by the optimizer, the appointment must be 'pinned'. This is typically done by checking the 'Pinned' checkbox on the Service Appointment record. The status alone does not lock the appointment in place for the optimizer.

Entitlement Management is the standard Salesforce feature for managing Service Level Agreements (SLAs). An Entitlement Process should be created to define the required steps and time limits (Milestones). You would create two separate processes, one for the 4-hour SLA and one for the 24-hour SLA. Then, when a customer purchases a contract, they are given the corresponding Entitlement record, which links them to the correct process. When a Work Order is created, Salesforce automatically applies the correct Entitlement Process and starts tracking time against the milestones.

Since the Work Order was generated from a Case, it has a direct relationship. Using Chatter is the most efficient and collaborative method. The technician can navigate to the parent Case from the Work Order in the mobile app and post an update, @mentioning the support agent. This provides a time-stamped, contextual record of the communication directly on the object the support agent is monitoring (the Case), ensuring visibility and quick action.

Salesforce provides standard permission sets tailored to Field Service roles. The 'Field Service Dispatcher License' grants access to the necessary objects and features, and the 'FSL Dispatcher Permissions' permission set provides the specific CRUD permissions needed to perform dispatching duties without granting administrative access to modify the underlying scheduling logic (like Work Rules and Policies). This aligns with the principle of least privilege.

This requirement needs several settings. The 'Frequency' of 3 months on the Maintenance Plan handles the quarterly aspect. The 'Generation Timeframe' of 30 days ensures Work Orders are created 30 days in advance. Crucially, the 'Maintenance Window' on the associated Maintenance Asset record defines the valid period for the service to be performed (the 15-day window). The generated Work Order's 'Earliest Start Permitted' and 'Due Date' will respect this window. The 'Date of the first Work Order in the next batch' anchors the entire schedule.