The Notifications feature in FleetWatcher allows you to send real-time alerts based on equipment behavior, helping your team respond quickly to issues like unauthorized use, excessive idling, or maintenance needs. This guide walks through how to create a new notification using the redesigned Add/Edit Notification page, including setting the trigger type, selecting recipients and equipment, and configuring optional features like schedules, custom messages, and conditions. Notifications can be as simple or detailed as you need. Start with defaults, or tailor them to match your specific workflow.

Go to Manage > Alerts > Create Notifications to open the Add/Edit Notification page.

At the top of the Add/Edit Notification page, you’ll select the Company for which this notification will apply. This is a required field and determines which users and equipment are available to configure the rest of the form.

If no users are assigned to the selected company, both the Email Recipients and SMS Recipients fields will appear grayed out and unavailable. You must assign users to that company in the system before they can be added as notification recipients.

Note: You can assign multiple types of recipients later in the form, but all recipient options are scoped to the company you choose here.

Once you’ve selected a company, the next step is to define whether the notification is active and give it a clear, descriptive name.

Use the Active switch to control whether this notification is currently enabled.

You can create and save notifications in an inactive state, which is useful for drafting or preparing tiered alerts that should go live later.

Enter a name that clearly describes the purpose of the notification. This is how it will appear in the Notifications list and helps distinguish between similar alerts.

Best practices:

The Notification Type determines the condition or behavior that will trigger the alert. This field is required and directly affects what configuration options appear below it.

Some Notification Types require additional setup, while others do not. Make sure to review the options that appear after you choose a type — these may include:

The Repeat Interval field defines how often a notification will re-trigger while the condition is still true. This prevents the system from sending too many alerts in a short period.

Example: If you set a Repeat Interval of 5 minutes for a Low Battery notification, recipients will receive an alert every 5 minutes while the low battery condition remains active.

This section defines who will receive the notification when it is triggered. You can assign one or more recipients across several channels and roles.

Each recipient type is represented by a checkbox. You can mix and match to ensure the right team members are alerted.

If no users are assigned to the selected company, Email Recipients and SMS Recipients fields will appear grayed out.

You can optionally define which users are allowed to snooze this notification — temporarily disabling it from sending alerts for a period of time.

Optional Feature:

You do not need to enable this to send notifications. Each Notification Type includes a default email and/or SMS message that will be sent automatically.

Use the custom message options only if you want to personalize the subject line or body with additional detail.

By default, FleetWatcher will send a standard system-generated message when a notification is triggered. If you want more control over how these messages are worded, you can enable the Custom Email or Custom SMS options.

These features let you write your own subject lines and message bodies — with or without dynamic fields.

Toggle Use Custom Email to ON if you want to define your own subject line and body for the email notification.

Toggle Use Custom SMS to ON if you want to customize the body of the SMS alert.

To personalize messages with data from the equipment or notification, click Custom Email Properties or Custom SMS Properties above the message editor.

This will open a popup with available dynamic fields, such as:

How to use them:

Repeat as needed — there is no limit to how many fields you can use.

Tip: These fields will automatically populate with live data when the notification is sent.

Each notification must be assigned to one or more pieces of equipment. This determines which assets will be monitored for the condition you’ve selected.

Note: Notifications are tied to the equipment name, not the physical GPS device. If the tracking unit is replaced, the alert will still apply as long as the equipment name stays the same.

You can use filters at the top of the section to narrow the list:

Bulk actions:

Use the Schedule grid to control when the notification is allowed to send alerts. This is useful if the alert should only apply during work hours or on specific days.

If a behavior occurs during a white (OFF) block, the alert will be suppressed — no message will be sent.

You can click individual blocks or use quick tools to adjust entire rows/columns:

Tip: If you’re unsure, leave the default schedule active (24/7) to start. You can fine-tune it later if needed.

Once you've completed all required fields for the notification, click Submit to save it.

Your newly created notification will appear on the View Notification page with the following details:

You can return at any time to edit a saved notification or toggle its active status.

Advanced Option

Most users do not need to add conditions. Use this feature only if you want to further narrow when an alert should trigger, beyond the basic Notification Type settings.

Conditions allow you to create rules that must be met for the notification to fire — based on things like speed, project assignment, or other equipment activity.

Example:

You’re creating a “Not Moving” alert, but only want it to trigger if the equipment is assigned to a specific project and running longer than 15 minutes.

You can build both conditions into the alert.

You can remove any condition at any time using the trash can icon.

Reminder:

A notification must still have at least one piece of equipment selected for any conditions to apply. If no equipment is selected, the notification will not trigger — even if all conditions are true.