Arrival Window Start and Arrival Window End are fields on the Service Appointment that indicate when a technician is expected to arrive at a customer site based on travel time and service duration calculations. These fields can be shared with customers to set expectations around upcoming appointments. Scheduled End and Scheduled Start are fields on the Service Appointment that indicate when a technician is scheduled to start and end their service based on their availability and assigned time slots. These fields are not accurate indicators of when a technician will arrive at a customer site, as they do not account for travel time and service duration variations. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_service_appointments.htm&type=5

Custom gantt filters are filters that allow dispatchers to view service appointments based on specific criteria such as status, priority, or custom fields[67]. Creating a custom gantt filter would allow providing a view of emergency work that is only visible to dispatchers by setting up criteria such as status equals emergency and sharing the filter with dispatchers only[68]. Custom lightning component is a component that allows developers to create custom user interfaces using Lightning Web Components or Aura Components[69]. Creating a custom lightning component would require coding and would not leverage the existing gantt chart functionality. Custom report in a private report folder is a report that allows users to view data based on specific criteria such as objects, fields, filters, or charts[70]. Creating a custom report in a private report folder would not provide a view of emergency work on the gantt chart and would not allow dispatchers to schedule or reschedule service appointments. Custom list view is a list view that allows users to view records based on specific criteria such as filters, fields, or sorting[71]. Creating a custom list view would not provide a view of emergency work on the gantt chart and would not allow dispatchers to schedule or reschedule service appointments. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_gantt_filters.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.fs_gantt_filters_create.htm&type=5 https://developer.salesforce.com/docs/component-library/documentation/en/lwc https://help.salesforce.com/s/articleView?id=sf.reports_builder_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.customize_listviews.htm&type=5

A quick action is used to create a record from another record with predefined field values. By defining a quick action to create a new service appointment from an existing one, the technician can easily create an additional visit to complete unfinished work.
Reference:
Work types are used to define the standard duration and skills required for a specific type of work. They can also include the required products that are needed for the work. By including the required products in the work type, the system can automatically add them to the work order when the work type is selected.

Multi-day service appointments are used when jobs can take longer than the available resources hours in a day or require consecutive days of work and can span over weekends. Jobs that need to be performed at the same site on the same day of the week or require multiple stages of work performed by different resources can be handled by single-day service appointments with appropriate scheduling policies and optimization rules. Reference: https://help.salesforce.com/s/articleView?id=sf.fs_multiday_service_appointments_overview.htm&type=5

Earliest Start Permitted is a field on the Service Appointment object that defines the earliest date and time that a service appointment can start[222]. Due Date is a field on the Service Appointment object that defines the latest date and time that a service appointment must be completed by[223]. Using Earliest Start Permitted and Due Date fields on Service Appointments would help ensure that they are completed within the agreed upon Service Level Agreement (SLA) with Universal Containers' customers by setting the boundaries for when a service appointment can start and finish according to the SLA terms[224]. Actual Start and Actual End are fields on the Service Appointment object that capture the actual date and time that a service appointment started and ended[225]. Using Actual Start and Actual End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers' customers because they are recorded after the service appointment is performed and do not enforce any SLA terms. Arrival Window Start and Arrival Window End are fields on the Service Appointment object that define the expected date and time range that a resource will arrive at a service appointment[226]. Using Arrival Window Start and Arrival Window End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers' customers because they only indicate when a resource will arrive and do not enforce any SLA terms. Scheduled Start and Scheduled End are fields on the Service Appointment object that define the planned date and time range that a service appointment will take place[227]. Using Scheduled Start and Scheduled End fields on Service Appointments would not help ensure that they are completed within the agreed upon SLA with Universal Containers' customers because they only indicate when a service appointment is scheduled and do not enforce any SLA terms. Reference: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_serviceappointment.htm https://help.salesforce.com/s/articleView?id=sf.fs_sla_overview.htm&type=5