← All help

Alerts & notifications

Who gets told, and in what order

Store contacts and members whose territory covers the store, filtered by the level each has asked for — then the escalation chain if nobody responds.

When a unit crosses a threshold, the recipients are worked out from the store it's assigned to — which is why an unassigned unit alerts nobody.

  1. Contacts attached to that store who have asked for this level.
  2. Members whose territory covers the store — directly, by region, by market, or through active temporary coverage — filtered by their role's policy and their own preferences.
  3. Anyone the same person would appear as twice is contacted once. A store contact who is also a member doesn't get two texts.
  4. If nobody acknowledges within the first escalation step's delay, the chain begins.

Where escalation chains conflict, the most specific wins: rules on the unit itself, then an override on the store, then the organization's default chain.

"Why didn't I get an alert?" has four common answers, in rough order of likelihood: the unit isn't assigned to a store; your territory doesn't cover that store; your level threshold is above the level that fired; or your contact details are missing or bouncing. Readiness finds all four.

In the dashboard: Readiness Answers one question for your whole fleet: if a store hit Danger right now, would a human find out?

Related

HeatAlert monitors workplace heat and tells someone before it becomes an incident. See plans or talk to us.