Google Map on Service Appointment or Service Territory Member record shows different location than in 'Dispatcher Console'

This can happen for one of two reasons:

1. The geocoding service used by Salesforce was not able to find an accurate match while Google Maps geocoding service was able to

The GeocodeAccuracy field on records will tell you how accurately Salesforce's geocoding service was able to geocode the given address.  It's possible that Google Maps geocoding service found a more accurate match.  To learn more about Geocode Accuracy please see this document: Geocode Information Fields

2. The address set on the record is irregular

This is a current limitation that is typically isolated to irregular formatted addresses.  The Google Map on the Service Territory Member record uses the Address field to determine the location whereas the Google Map on the Dispatcher Console uses the Longitude/Latitude fields of the Service Territory Member record to plot the location.

When an address is geocoded our geocoding service determines how accurately it was able to geocode the given address.  If the GeocodeAccuracy field on the Service Territory Member record is Zip, City, County, State you will see a different location on the Map within the Dispatcher Console when compared with the Map on the Service Territory Member record.

As a workaround, you may want to consider updating the address, so that it's format is recognized by Google Maps.  As an example, if you had the following address set on a Service Territory Member you'll notice that the maps differ:

If you update your Service Territory Member to use the correctly formatted address the geocode service will be able to more accurately determine the geolocation.