Notifications Placeholders for SMS & Email Customer Notifications
In addition to the custom text in your notification messages, you can also use multiple informative placeholders that retrieve data from particular Route4Me fixed attributes (i.e., order numbers, customers’ names, estimated arrival times, geofence-entered/departed timestamps, etc.) and automatically insert this data into your notifications as text. Thus, you do not need to waste valuable time on finding, copying and pasting a particular order number or customer’s name into each notification. All you need to do is insert one or multiple preferred placeholders into a particular notification, and the route optimization system will automatically generate a personalized message for each customer, containing the custom text and the data pulled from the corresponding fixed attributes.
All notification types (E-Mail and SMS) are sent to the customers/prospects whose contact information is defined in the Customer section of the corresponding route stops. The Customer section of each route stop can be accessed and modified using the Route Editor in real-time.
Below, you can find all available placeholders that can be used for retrieving data from Route4Me fixed attributes and inserting this data into your Customer Notifications.
Placeholder | Route4Me Fixed Attribute | Description | Example of Retrieved Data |
---|---|---|---|
{{address}} | Address | Street address of the customer associated with the corresponding stop. | 405 Lexington Ave, New York, NY 10174, USA |
{{alias}} | Alias | A user-defined name assigned to a customer/stop for internal use. | Customer 001 |
{{lat}} | Lat, Lng | Latitude coordinates of the customer’s location. | 40.751868 |
{{lng }} | Lat, Lng | Longitude coordinates of the customer’s location. | -73.975554 |
{{address_stop_type}} | Address Stop Type | The type of the corresponding stop on the route. | Pickup, Delivery, Break, Meetup, Visit, Service, or Drive By. |
Placeholder | Route4Me Fixed Attribute | Description | Example of Retrieved Data |
---|---|---|---|
{{now_date}} | Address Visit Details | The current date when the corresponding notification was triggered and sent to the customer. The format of this date can be adjusted in the advanced settings | 10.10.2019 |
{{now_time_formatted}} | Address Visit Details | The current time when the corresponding notification was triggered and sent to the customer. The format of this time can be adjusted in the advanced settings | 04:10 PM |
{{geofence_detected_visited_timestamp}} | Detected as Visited | The timestamp that was automatically generated by the system when the driver entered the geofenced area set around the address. | 07/07/2019 05:00 PM |
{{geofence_detected_departed_timestamp}} | Detected as Departed | The timestamp that was automatically generated by the system when the driver left the geofenced area set around the address. | 07/07/2019 05:00 PM |
Placeholder | Route4Me Fixed Attribute | Description | Example of Retrieved Data |
---|---|---|---|
{{order_no}} | Order No | The order number associated with the stop. | QA000007188 |
{{cost}} | Cost | The cost of visiting and servicing the stop. | 100 |
{{cube}} | Cube | The cubic volume of the cargo/order that is being delivered to or picked up at the stop. | 0.5 |
{{invoice_no}} | Invoice No | The order invoice number associated with the stop. | ALT12341 |
{{pieces}} | Pieces | The number of pieces (items) that are being delivered to or picked up at the stop. | 20 |
{{reference_no}} | Reference No | The order reference number associated with the stop. | 789 |
{{revenue}} | Revenue | The revenue that is expected to be generated from visiting and servicing the stop. | 1000 |
{{weight}} | Weight | The weight of the cargo/order that is being delivered to or picked up at the stop. | 100 |
{{sequence_no}} | Priority | The sequence number/position of the stop on the corresponding route. | 1 |
{{tracking_number}} | Tracking Number | The tracking number that is automatically assigned to the order by the system. Tracking numbers can be used by customers for checking their orders on the customer tracking portal. | E27YMNGK |
Placeholder | Route4Me Fixed Attribute | Description | Example of Retrieved Data |
---|---|---|---|
{{name}} | First Name + Last Name | Full name (first name and last name) of the customer/prospect associated with the stop. | John Smith |
{{first_name}} | First Name | First name of the customer/prospect associated with the stop. | John |
{{last_name}} | Last Name | Last name of the customer/prospect associated with the stop. | Smith |
{{email}} | Contact e-mail address of the customer/prospect associated with the stop. | [email protected] | |
{{phone}} | Phone | Contact phone number of the customer/prospect associated with the stop. | +1 212-682-3070 |
{{customer_po}} | Customer PO | Purchase order of the customer/prospect associated with the stop. | PI000347 |
Placeholder | Route4Me Fixed Attribute | Description | Example of Retrieved Data |
---|---|---|---|
{{time_window_start}} | Time Window Start | The start of the stop’s time window (normally used for opening hours). | 09:00 AM |
{{time_window_end}} | Time Window End | The end of the stop’s time window (normally used for closing hours). | 09:00 PM |
Placeholder | Route4Me Fixed Attribute | Description | Example of Retrieved Data |
---|---|---|---|
{{arrival_time_formatted}} | Planned Arrival Time | The estimated time when the driver is expected to arrive at the stop. The format of this time can be adjusted in the advanced settings. | 4:10 PM |
{{arrival_date_formatted}} | Planned Arrival Date | The estimated date when the driver is expected to arrive at the stop. The format of this date can be adjusted in the advanced settings. | 07.07.2019 |
{{earliest_time_formatted}} | Planned Arrival Time with ETA Padding | The estimated time of arrival minus 50% of the defined “ETA Padding” value (i.e., minus 5 minutes from the estimated arrival time). The format of this time can be adjusted in the advanced settings. | 2:10 PM |
{{max_arrival_time_formatted}} | Planned Arrival Time with ETA Padding | The estimated time of arrival plus 50% of the defined “ETA Padding” value (i.e., plus 5 minutes to the Estimated Arrival Time). The format of this time can be adjusted in the advanced settings. | 1:50 PM |
Custom Data Notifications Placeholder
The Custom Data notification placeholder allows you to automatically attach Custom Data to your SMS and Email notification messages. To use the Custom Data Placeholder, first, add the preferred Custom Data fields and values to one or multiple route destinations.
Next, insert the Custom Data placeholder into the preferred SMS or Email Notification Type message. The first part of the placeholder “{{custom_fields.” should be unchanged, and the second part of the placeholder should contain the name of the Custom Data Field that contains the value which you want to attach to the message, i.e., “item_1}}”.
Placeholder | Route4Me Attribute | Description | Placeholder Example |
---|---|---|---|
{{custom_fields.}} | Custom Data | Custom Data attached to route destinations. | {{custom_fields.item_1}} |
In the example below, if you use the following Custom Data placeholder: “{{custom_fields.item_1}}” the value (Custom Data 1) from the corresponding Custom Data field (item_1) will be attached to the message.
- Sample message with placeholder: Your order will include {{custom_fields.item_1}} and {{custom_fields.item_2}}
- Received notification message: Your order will include Custom Data 1 and Custom Data 2
Use an underscore to separate words in Custom Data values.
Placeholders by Notification Type
The table below provides the list of all placeholders that are supported for the corresponding notification types.
Placeholder | Route Scheduled | Geofence Entered | Geofence Departed | Visit Completed | Notify Next Customer |
---|---|---|---|---|---|
{{now_date}} | |||||
{{now_time_formatted}} | |||||
{{arrival_time_formatted}} | |||||
{{arrival_date_formatted}} | |||||
{{earliest_time_formatted}} | |||||
{{max_arrival_time_formatted}} | |||||
{{address}} | |||||
{{first_name}} | |||||
{{last_name}} | |||||
{{name}} | |||||
{{tracking_number}} | |||||
{{customer_po}} | |||||
{{invoice_no}} | |||||
{{reference_no}} | |||||
{{order_no}} | |||||
{{weight}} | |||||
{{distance_to_next_destination}} | |||||
{{alias}} | |||||
{{lat}} | |||||
{{lng}} | |||||
{{address_stop_type}} | |||||
{{cost}} | |||||
{{cube}} | |||||
{{pieces}} | |||||
{{revenue}} | |||||
{{sequence_no}} | |||||
{{email}} | |||||
{{phone}} | |||||
{{geofence_detected_departed_timestamp}} | |||||
{{geofence_detected_visited_timestamp}} | |||||
{{timestamp_last_visited}} | |||||
{{timestamp_last_departed}} |
Visit Route4Me's Marketplace to Check out Associated Add-Ons:
- Notifications & Alerts
Route Scheduled
- Notifications & Alerts
Geofence Entered
- Notifications & Alerts
Geofence Departed
- Notifications & Alerts
Visit Completed
- Notifications & Alerts
Notify Next Customer