In this article, you will learn about the tags used in the creation of notification templates for recipients.
Tags are variables that are replaced with text at the time the notification is sent. You can see a preview of what these tags translate into at the bottom of the notification details view.
- - {recipientName} - The name of the recipient for this task
- - {workerName} - The driver assigned to this task
- - {eta} - The estimated time of arrival for the driver to reach the recipient
- - {vehicleDescription} - The year, make, and model of the vehicle used by the driver
- - {vehicleLicensePlate} - The driver's license plate
- - {workerPhone} - The driver's phone number
- - {taskShortId} - The Task ID, as seen from the Onfleet dashboard
- - {destinationAddressShort} - The recipient's street address (without city, state, or zip code)
- - {destinationAddressLong} - The recipient's street address (including city, state, and zip code)
- - {trakLink} - a link that the recipient can click on to track the driver's location in real-time (to customize this web view, see the recipient tracking page). Once a task has been completed, this link can be enabled to automatically convert into a feedback page
- - {creatorName} - The name of your organization, as specified in Admin settings
- - {executorName} - The name of the organization that has been delegated to complete this task (for use with connected organizations)
- - {merchantName} - The name of the organization that originally created this task (for use with connected organizations)
- - {signatureUrl} - a link for the recipient to provide a signature for their task through their personal device and removes the need for contact on the driver's device. The signature can be viewed within the completed task details.
We do our best to handle various circumstances appropriately, for example:
- If a task is started when the driver is within 150 meters of the destination and you have notifications set up with , and triggers, we will only send the notification.
- If the driver loses connectivity when the ETA is 12 minutes and re-gains it when the ETA is 6 minutes, but there is a 10 minute trigger set up, it will use the actual ETA (6 minutes) in the notification that gets sent, provided you used the appropriate tag rather than entering "10 minutes" directly into the notification text.