Travel Time Is Not Considered in Salesforce Field Service Appointment Booking Requests

To resolve travel time not being considered in appointment booking, verify and correct the following:

1. Ensure GeoCoding is Complete: Geocoding is the process of converting a street address into latitude and longitude coordinates. In Salesforce Field Service, Data.com is responsible for geocoding records, and this is an asynchronous process (it does not happen immediately). All Service Appointments must be fully geocoded — meaning they must have valid Latitude and Longitude values populated — before calling the Get Slots API method (getSlots).
2. Verify Latitude and Longitude Data on the Service Appointment: If a Service Appointment is created from another Salesforce object (such as a Work Order or Account), the latitude and longitude values should be copied from that parent object to the Service Appointment before making the Get Slots API call. If the Service Appointment has null or empty values in the Latitude and Longitude fields, travel time cannot be calculated.
3. Confirm Address Data on All Relevant Objects: Ensure that all objects involved in appointment booking — including the Service Appointment, Work Order, and Account — have valid and complete address details. Accurate address data enables the geocoding service to produce valid coordinates, which in turn enables accurate travel time and distance calculations during appointment slot generation.

By ensuring valid geolocation data is present on the Service Appointment before invoking the appointment booking flow, the system correctly considers travel time in slot availability, prevents scheduling conflicts, and supports optimized route planning for field service engineers.