Geofencing ensures that drivers are at the required location when they complete a stop.

When you enable geofencing, the current location of a driver will be checked against the requested location of the stop. A driver will only be able to update the status of a stop if they are in close proximity of where they need to be.

Validating the location of the driver when updating a stop status can increase the data quality and improve the customer experience. Metrics related to driver performance and customer facing notifications will be more accurate when the underlying data quality is high.


Step-by-step guide to implement geofences

  1. When creating or updating a booking via API, you can define the maximum distance in meters per stop.
  2. When the maximum_driver_distance_meters attribute is set, a stop is only allowed to be marked as arrived within the MotionTools app when the driver is within the defined meter-radius around the stop location.

  3. If the driver is not in the expected radius, the app will show the following error message.


Manually or programmatically enabling geofencing

Once a stop is created, is is possible to enable geofencing in the dashboard as a dispatcher. Alternatively a customization can be built or requested from the MotionTools Support team that enables this automatically.


Future improvements

  • Ability to enable geofences in the service configuration directly in the dashboard
  • Admins and Org managers will be able to force-end the stop on behalf of the driver. This can be helpful, if in some cases the driver won’t be able to perform the action due to poor GPS signal or internet connection. As a workaround for now, Admins can force-end the entire Tour.
War dieser Beitrag hilfreich?
0 von 0 fanden dies hilfreich

Beiträge in diesem Abschnitt