Auto-arrive geofence automatically updates a task’s state when the driver reaches the stop’s location.

To enable it, go to Configuration ⇒ Driver App ⇒ Auto-arrive geofence.

You can also set the radius at which auto-arrive triggers. For example, with a 100-meter radius, the task state changes to Arrived as soon as the driver is within 100 meters of the delivery location.

Click Save once the changes have been added.

If you’ve set up email or SMS notifications that trigger when a task’s state changes to Delivery Arrived, they’ll also be sent when auto-arrive switches the state automatically.

Auto-arrive delay when already at the location - When a driver starts a Task while already inside its geofence (for example, because the previous stop was nearby), this setting controls how long the app waits before automatically marking them as arrived.

The Task is only auto-arrived if the driver is still inside the geofence once the delay has passed. This prevents false arrivals when stops are close together, and gives the driver time to tap Navigate and head to the actual stop.

The default delay is 60 seconds. Set it to 0 to turn off auto-arrive for tasks started inside the geofence.

Disabling Drivers from updating Task state updates outside of the Task location radius can be done in Configuration ⇒ Driver App ⇒ Prevent task status updates based on geofence.

Prevent state update geofence radius - This prevents Drivers from setting the Task state to "Arrived" if they are not within the geofence radius around the Task location. Prevent state update geofence radius can also be defined. The radius range can be set from 200m to 2000m, and the default is 200m

It's also possible to allow the Driver to update the Task state regardless, but this will prompt a confirmation dialogue box before the update is made.

For more flexibility over how the geofence works, you can let drivers override the geofence restriction by enabling the Geofence override option.

This option is only available when Prevent update outside of geofence is also enabled. Every geofence override is recorded in the Task history.