Alerts and notifications
What an alert is for
Section titled “What an alert is for”Roudiy records everything, but nobody can watch the dashboard all day. Alerts bring the important moments to the right people: Who gets notified, and how, when something happens in the fleet.
Anatomy of an alert rule
Section titled “Anatomy of an alert rule”Every rule is built from the same parts. Read them as one sentence.
| Part | What it decides | Example |
|---|---|---|
| Trigger | What starts the alert. | Safety event |
| Conditions | Which cases of that trigger count. | Severity Critical or High; types: Phone call |
| Applies to | Which part of the fleet. | Groups: Dallas North |
| Active hours | When the rule is on. | Mon–Fri, 6:00–20:00 |
| Recipients | Which roles are told. | Safety Manager |
| Channels | How they are told. | In-app, Email |
| Cooldown | How long to stay quiet before repeating. | 10 minutes |
Trigger and conditions
Section titled “Trigger and conditions”- Safety event: pick severities and, optionally, event types. None picked = all types. Speeding events arrive later than others: Speeding alerts arrive after the trip ends.
- Kit offline: fires when a kit has been offline for 24 hours. The time is fixed.
- New fault code: fires when a new engine fault code of the levels you pick appears: Critical, Warning, Info. Alert history lists these alerts as Fault code. This needs the KD032 gateway.
You cannot change a rule’s trigger after you save it; create a new rule instead.
Applies to and active hours
Section titled “Applies to and active hours”A rule can cover All of the fleet, or chosen Groups, Vehicles or Drivers (Drivers is not available for kit offline). Active hours are Always or chosen days and hours, evaluated in the company time zone.
Recipients and channels
Section titled “Recipients and channels”You choose recipients by role, not by name. Each person only gets alerts for the trucks in their own groups: a Safety Manager in Dallas South is not told about a Dallas North event, even if the rule covers all trucks. Channels are In-app and Email; there is no SMS.
Cooldown
Section titled “Cooldown”Cooldown (minutes), from 0 to 1,440: No repeat alert for the same vehicle within this time. It counts per rule, per vehicle and per event type (for fault codes, per code); kit offline sends one alert per offline period. In a rule for close following with the default 10 minutes, five close-following events on TRK-105 within ten minutes send one alert, not five. Collision and SOS alerts ignore cooldown.
Default rules
Section titled “Default rules”Every company starts with two rules, marked Default. They cannot be deleted, but you can edit them or switch them off.
- Critical and high severity safety events: tells Company Admins and Safety Managers, in-app and by email, with a 10-minute cooldown.
- Kit offline for 24 hours: tells Company Admins, in-app and by email, when a kit has not reported for a day.
Company rules and my rules
Section titled “Company rules and my rules”- Company rules apply to everyone the rule names. Only users allowed to manage all rules can create them. A company can have up to 200 rules.
- My rules are personal: the recipient is always Only you. Each user can have up to 20.
A dispatcher who wants to know about every harsh-braking event on TRK-102 can set a personal rule without changing anything for the rest of the team. Harsh braking events are Medium severity, so the dispatcher ticks Medium (a new rule starts with Critical and High).
Alert history
Section titled “Alert history”Alerts your rules fired and who was notified. Each alert has a status:
- OpenFired, nobody has responded
- AcknowledgedSomeone is on it (optional note)
- ResolvedKit offline only, on its own
Safety and fault code alerts never become Resolved, and nobody can resolve an alert by hand.
History shows the last 7 days by default and up to 92 days. Company Admins see every alert; other users see the alerts sent to them.
How notifications show up
Section titled “How notifications show up”- In-app: in the bell in the top bar and on the Notifications page.
- Email: a message in your inbox. Collision and SOS emails start with [COLLISION] or [SOS] in the subject so they stand out.