Skip to main content
LLMs.md

Reaction defaults

Reaction defaults answer the question: "What should happen when something goes wrong?" — once, centrally, instead of on every single shift. You define one default rule per event type for the whole tenant, and add exceptions only where a property needs to react differently.

Reaction defaults (notifications)

:::warning Why this matters Checks like the minimum duration or the check-in window only detect violations — nothing is reported unless a reaction rule is linked. With a reaction default, every shift is covered automatically, including newly created ones. :::

The two event types (slots)​

SlotCovers
Attendance violationMissed or late check-in/check-out (check-in/check-out windows), violated minimum duration
Check-aliveMissing check-alive signal during a running shift

The linked rule determines the reaction: create an incident, notify responsible staff, run an escalation chain, send an SMS alert — anything an automation rule can do.

Setting the default​

  1. Open the Automation tile (in the Tools group at the bottom of the sidebar) — you land on Notifications.
  2. In the Reaction defaults section, pick the slot, e.g. Attendance violation.
  3. Choose the rule that will act as the default for all properties.

From now on the rule fires for every shift of the tenant whose check trips — with no per-shift configuration required.

Exception for a property​

Some properties need a different reaction — say, a stricter escalation for a critical building:

  1. Open Tools → Automation → Notifications and choose "Add property exception" on the slot.
  2. Pick the property and the deviating rule.

The exception applies to this property only; all others keep following the tenant default.

How it looks in the shift dialog​

In "Create new shift" (and when editing), the reaction section shows the inherited default as a hint, e.g.:

Default: rule "Escalate to site manager" — from tenant

or "— from property" if a property exception applies. A shift-level rule is still possible — it is the last stage of the chain and beats both property and tenant:

Shift rule → property exception → tenant default

How this differs from shift defaults​

  • Shift defaults on the property define the target values (how long is the check-in window, which minimum duration applies).
  • Reaction defaults define what happens on a violation.

Since the value side now has a tenant level as well — the shift defaults in the main settings — both systems are built symmetrically: values and reactions each follow the chain shift → property → tenant. The value chain determines what is checked; the reaction chain what happens on a violation. Together they yield shifts that usually need no individual configuration at all.