In this article, you will learn how to set up automatic SMS notifications, anonymize communications between driver and recipient, and set up dependency notifications (if applicable).
Notification Set-up & Triggers
The Communications tab allows an administrator to set up and customize any number of automated SMS messages that can be sent to a recipient based on varying driver actions and triggers.
Note: There can only be one notification per trigger. Below the notifications window, you will have the option to select the language in which you would like to communicate with your customers.
To add a new communication select the "+" symbol located at the bottom right of the notifications window. The exact messaging of these notifications can be completely customized along with task-specific tags.
Onfleet offers the following triggers for notifications:
- is triggered when the driver starts the task from the driver app.
- triggered when the ETA falls below a certain threshold, which you specify. Note that these ETAs are calculated only for the current task - for future tasks, use Predicted ETA.
- is triggered when the driver is within 150 meters (~500 feet) of the destination.
- is triggered when the driver completes the task from the driver app and marks it as succeeded.
- is triggered when the driver completes the task from the driver app and marks it as failed.
- dependent tasks linked to it. A notification will be sent out to all recipients attached to the dependent tasks. For more information, please review Dependency Notifications. is triggered when the driver has started a task that has
- is triggered when the driver has completed a task that has dependent tasks linked to it. A notification will be sent out to all the recipients attached to the dependent tasks.
- predicted ETA of a downstream unstarted task (i.e. not the current task) falls below the specified threshold. triggered when the
- triggered when the task is delayed by a certain threshold, which you specify.
If your organization would like to include any non-Onfleet hosted links in your communication to recipients, please contact the Onfleet support team.
Onfleet has an anti-spamming threshold of 10 seconds (10000 ms) in our notification system that applies to all automated SMS messages that are system-generated (driver-initiated SMS does not apply to this restriction).
If notifications are triggered too closely to one another the secondary notification will not be sent to the customer. For example:
Company A has a notification set for a `Dependency Completed` task - "Your order has been picked up from a restaurant!"
Company A also has a `Task Started` notification for its customer for when the driver begins the task.
If the driver starts the Task within 10 seconds of completing their `Dependency Completed`, then the `Task Started` notification will not be sent.