Skip to main content

Create Alerts [Legacy]

Configure real-time behavior alerts. Select equipment, set triggers and schedules, and assign project-based recipients for instant notifications.

Introduction:

The Create Alerts [Legacy] page is a split-screen interface designed to push real-time behavior-correction notifications to equipment. The core logic of this page is that the configuration visible on the left side is saved to (or deleted from) all assets selected on the right side.

Navigation

  • Path: Manage > Alerts > Create Alerts [Legacy].

    • Note: All customers see the "[Legacy]" label. Users with the new Notifications feature flag enabled will see both options in the menu.

Setting Up an Alert

  1. Target Equipment First: On the right panel, use the searchable filters (Companies, Asset Types, Equipment, Eq Types, or Projects) to find your assets. Check the boxes next to the names so they appear in the list with a blue checkmark.

    1. Tip: Keep selections to 50 or fewer assets at a time for the best performance.

  2. Select Alert Type: Now move to the left panel and click Create New Alert. Select the desired trigger from the list (e.g., Excessive Idle).

  3. Configure Parameters: Enter your specific thresholds (speed, time, or temperature).

  4. Define Recipients: Assign Recipients 1–4, add an external email for Recipient 5 if needed, or select Project Management roles.

  5. Set Schedule: Click the blocks to toggle them Red (ON) or White (OFF). Use the (+) to expand for 15-minute granularity.

  6. Save: Click Save Alert and stay on the page until the Completion Percentage Graph at the top reaches 100%.

Efficiency Tip: Use Role-Based Recipients For project-specific alerts (e.g., Excessive Idle, Speeding), it is best practice to use the Project Management checkboxes (Foreman, Superintendent, etc.) rather than the individual Recipient slots.

  • Why? If a staff member leaves or changes projects, you don't have to edit the alert. You simply update the personnel assigned to that Project in FleetWatcher, and the Legacy Alerts will automatically follow the new person assigned to that role. This saves significant administrative time compared to manually updating recipient names across dozens of individual alerts.

Deleting Alerts (Individual or Batch)

The deletion process requires "selecting" the alert type from an existing asset first:

  1. Select Assets: Use the filters on the right to find the equipment. Ensure all assets you want to affect have a blue checkmark next to their name.

  2. Open Alert List: Click on the name of one of the assets. A popup window will display all alerts currently assigned to that specific piece of equipment.

  3. Target the Alert: Click the Alert Title (e.g., "Low Battery") in the popup. That alert’s configuration will now load into the left-side panel.

  4. Execute Deletion: Click the red Delete Alert button at the bottom of the right-side panel.

    • Result: The alert will be removed from every asset that was checked in the right-side list.

    • Visual Confirmation: The alert configuration will disappear from the left panel. For batch deletes, a progress bar will indicate the status until complete.

Alert Behavior & Specific Triggers

  • Behavior Correction: Most alerts send an email with every unit transmission until the issue stops.

  • Snoozing: Recipients 1–4 and Project contacts can snooze alerts if the "Can Snooze" checkbox is selected. Recipient 5 cannot snooze unless their email matches an account with the Manage Alert ACL.

  • Escalation Tiers / Auto-Snooze: Alerts like Excessive Idle use up to three tiers. These auto-snooze for the duration of the tier (e.g., a 20-minute tier 1 triggers one alert and then snoozes for 20 minutes), overriding the high-frequency email behavior.

  • Temperature: Values are stored in Celsius and rounded. Entry in Fahrenheit may fluctuate by $±1$ due to this conversion.

  • Manual Snooze (Unauthorized Use): This is the only alert where the email contains a Snooze Hyperlink instead of a map link. Users must have a FleetWatcher login and the Manage Alert ACL to use this link.

  • One-Time Alerts (Driver Not Authorized): Triggered and sent only once when an unauthorized driver is assigned.

  • Repetitive Alerts (Driver Not Assigned): Resends every 10 minutes while the equipment is active without an operator (Note: specific interval logic requires further verification).

📞 📬 Need Help?

Contact: support@fleetwatcher.com

Did this answer your question?

Related Articles