Managing and configuring notification rules for your account

You can create customized notification rules that alert you when you need to take action. Whether it's for a shipment that's running late, costs that were updated by a carrier, a task you’ve been assigned, or more.

Note: The user profile page's Notifications tab discussed in this article was previously called the Rules tab.

You can create notification rules for the following entities:

  • Shipments
    • Shipment exceptions
    • Auto re-rate
  • Orders
    • Order exceptions
  • Inventory
    • Inventory exceptions
  • Messenger
  • Tasks

This article covers:

Note: Turvo also offers Admin users and above the ability to configure default notification rules that apply to all users with certain roles. However, this is a limited release feature and is not available to all Turvo tenants. See our Configuring default notification rules for all users with a specific role article to learn more about this feature.

Accessing your Notifications tab to manage or create rules

Navigate to your User profile by clicking on your profile icon in the top right corner of Turvo, then click on your name or profile picture.

Note: The Notifications toggle turns Web app notifications on and off. Learn more about Web app notifications in the create a rule section below.

Profile_icon_-_name.png

On your User profile page, select the Notifications tab.

2024-02-08_13-09-37.png

Managing existing rules

In the Notifications tab of your User profile, click on each section (Shipments, Orders, Messenger, Items and Inventory, Tasks, and Offers) to expand or hide the rules for each. If you’ve previously set up notifications in Turvo, those are included here. If you haven’t, your Notifications tab is pre-populated with a few rules to get you started. These rules are in the Disabled status and do not trigger notifications until you configure them for your workflow and change them to Enabled.

Note: Exception rules are housed under their corresponding block. For example, shipment exception rules are found under the Shipments block. 

To manage an existing rule, hover over the row and click the three vertical dots on the right side to open the More actions menu.

NotificationsTab_2023R4.png

  • Enable or Disable: Enable/Disable allows you to change the status of the rule.
    • Disabled rules do not trigger notifications.
    • Enable a rule to start triggering notifications based on that rule.
  • Edit: To edit a rule, select Edit to make changes.
  • Delete: To remove a rule from your profile, click Delete.
    • Note: Deleted rules cannot be recovered.

Creating a rule

To create a new rule:

  1. Click + Create rule in one of the sections under the Notifications tab in your user profile.
  2. The Create rule modal appears.

  1. Fill in all of the fields needed to create your rule, outlined in the sections below.

Note: Notification rules follow the same When/If/And/Then logic used by Autopilot rules. See our Autopilot: Understanding rule creation logic article to learn more about the basic rule logic used in Turvo.

Rule name

  1. The Rule name can be anything that helps you identify the rule in the list of all your notification rules.

Entity

  1. The Entity field controls what type of notification rule you’re creating. This is set automatically based on which section you were in when you clicked + Create rule (either Shipments, Orders, Messenger, Items and Inventory, Tasks, or Offers).

When

  1. Use the When field to select what event you want to be notified about from the When drop-down menu. The available options are applicable to the chosen Entity.
    1. For example, if you want to be notified when someone posts an update to a shipment, create a rule from the Shipments section, then select Someone posts an update on a shipment from the When drop-down menu.

If (required)

  1. If you’re creating a rule for Shipments, Orders or Exceptions, the Visibility Groups field appears after choosing a When option, and is required. This is populated automatically with your current user groups but you can remove or add groups as needed. You can also choose to exclude a set of groups instead by clicking Is not.

Note: The Visibility Group is also required for a subset of Task notification events. The example below shows how the If (required) section with the Visibility Group field appears when Someone posts an update on a shipment is selected.

CreateNotificationRule_2023R4.png 

+ Add criteria

Optionally add additional criteria to further customize your rule. This allows you to only receive the notification if certain conditions are met along with the event chosen from the When drop-down. 

  1. Once you’ve selected the When event that you want to be notified of, you can start applying additional criteria to customize the rule to your workflow. Click + Add criteria.

AddCriteria_2023R4.png

  1. Use the drop-down to select the criteria that you want to apply.

AndOptional_2023R4.png

  1. Click Is or Is not to determine whether you want the criteria to be added as an include or an exclude condition.
    1. An Is condition means the notification only fires if the criteria is met.
    2. An Is not condition means the notification only fires if the criteria is not met.
  2. Next, enter the relevant criteria, such as a specific customer account.

Note: If you add multiple attributes to one criteria row, it is considered an OR rule. This means the notification fires if either of the criteria attributes are met. For example, in the screenshot below, the rule is set up to notify the user if someone posts an update on a shipment that belongs to the Regression Broker group and is for the customer Anchor Brewery OR Claudio’s Cacao Farm.

CustomerIsCriteria_2023R4.png

  1. You can continue to add more criteria to your rule using the + Add criteria button.

Note: If you add multiple different criteria types, they are considered “AND” rules in relation to the other criteria. This means the notification fires only if all of the conditions are met. For example, in the screenshot below, Web app and Email notifications occur if someone posts an update on a shipment that:

  • Belongs to the Regression Broker group, and;
  • Is for the customer Anchor Brewery OR Claudio’s Cacao Farm, and; 
  • Is tagged #HotShipments.

SAVERule_2023R4.png

  1. In the Actions section, select the notification method(s) that you want to be notified by. Click the box next to each method. 
    1. You can add any combination of notification methods to the notification rule. 
    2. The notification methods are described in the section below.
  2. Once you've applied all of your necessary changes, click SAVE to save your changes.

Notification Methods

The Action for a notification rule is always Send notification. If you want to receive the notification anytime the When event occurs, use the checkboxes shown under Notification method to select the methods that you want to be notified by. There are four possible notification methods, described in the subsections below.

Web app

If you check the Web app checkbox, Turvo sends a notification to your user account in the Turvo web application. A small number appears on top of the bell icon in the top right corner to indicate a new notification. Click the bell icon to open the notifications sidebar and see all of your web app notifications.

Bell_icon_notification.png

Email

When you select Email as a notification method, Turvo sends an email notification to your primary email address with the details of the shipment change or the exception created.

For shipment exception notification emails with the following exception types, the email includes the customer name and location name to which the exception applies:

  • Appointment issue
  • Appointment not scheduled
  • Border issue
  • Carrier issue
  • Customer issue
  • Delivery issue
  • Dwell time exceeded
  • Equipment issue
  • Held at Customs
  • Location issue
  • Missed appointment
  • Missing arrival
  • Missing departure
  • Pickup issue
  • Potential exception
  • Running late*

*For Running late exception emails, the notification email also includes the following (along with the customer location names):

  • The shipment customer’s preferred secondary ID, if available.
    • If the customer account is not configured for a specific secondary ID type, or an ID of that type has not been added to the shipment, the tenant-default is used.
    • If the tenant default secondary ID type is not configured, or an ID of that type has not been added to the shipment, no secondary ID is included.
  • A map that displays the shipment route up to the location to which the shipment is running late.
  • A list of other pickup and delivery locations on the shipment for the affected customer which may be affected by the shipment running late to the named location.

Mobile app

If you select Mobile app, notifications are sent to your user account within the Turvo app on your mobile device. Learn more about Turvo Mobile.

Text message

If you select Text message, Turvo sends an SMS text message to the mobile phone number in your user profile containing information on the changes made and a link to the shipment

Note: If there is not a phone number designated as Mobile in your profile, then you cannot receive a text notification. Go to the Details tab of your user profile to edit your phone numbers.

Once your rule is complete, then click SAVE. To customize the rule further, continue on to the next section about adding criteria.

Was this article helpful?

4 out of 4 found this helpful