Alerts

The Alerts inbox shows what is happening now: lateness, vanishing GPS, idleness, low battery, a driver report, a plan payment problem, a new catering enquiry. It is not for browsing history and it is not mail.

On the Dashboard you see the most important open alerts in the Needs attention card.

Severity

The colour says how urgent an alert is. It does not mean the alert was read. More: alert severity. Severity comes from the alert’s rule and cannot be changed.

• Urgent (red): happening now — a driver vanished from the map, reported a problem from their phone, or there is a plan payment problem.
• Risk (amber): about to be too late — the arrival will miss the promised ETA window.
• Operational (grey): to handle during this shift — an idle driver, a weak battery, an order without an assigned driver, a new catering enquiry.

A grey alert you have read is still operational until someone closes it. Acknowledging does not turn it green.

Acknowledge, snooze, resolve

You have three actions. For each we record who did it and when.

flowchart TD
  open["Matter alive"] --> ack["Potwierdz: seen"]
  open --> snooze["Drzemka: hide for a while"]
  open --> done["Rozwiaz: closed"]
  ack --> open
  snooze -->|"time passed"| open
  done --> closed["Does not return as unread"]

Repeated alerts about the same thing (the same driver, the same signal loss) combine into one card, so you close one problem once.

Where they come from

Alerts about drivers (vanishing GPS, idleness, battery, a report from the phone) come from Fleet data. When Fleet is off, we do not create alerts about drivers. Alerts about orders, plan payment and catering enquiries keep working.

A report from a driver’s phone comes here, not as an easy-to-miss status on a map pin. See duty.