CHANNELS
Six built in
Slack, Teams, email, SMS, webhook, Pagerduty. Add more with a JSON config - every alert has a stable schema you can match on.
01 · Platform · Alerts
Be the first to know - before the complaints come in.
Set a threshold. Pick a channel. Get told when the room is too full, the queue is too long, or the CO₂ is climbing. Sub-second latency. No false-positive avalanche, because each alert is gated by a calm-period you control.
02 · Threshold setup
Drag the threshold. Watch the room cross it.
A tiny version of the live floorplan, with a configurable threshold. When occupancy crosses, the corresponding alert preview flashes. This is exactly what your operations team would see.
Threshold preview
Anonymous dots cross zone capacity. The alert side fires.
Alert channels
Slack
Teams
Email
SMS
Webhook
Pagerduty
Sample alert
▲ DENSITY · Library A · Floor 4
Occupancy crossed 90% (28/30). Calm-period was 5 min.
19:42:08 AEDT · acknowledged by j.harper@university.example
03 · Operational signal-to-noise
Alerts that actually mean something.
Sample week · Campus-wide
Calm-periods, escalation policies and acknowledgements baked in.
Alerts this week
14
Down · −22% vs 7-day avg
Median time to ack.
0 min
Target 5 min · OK
False positives
0%
Calm-period gating · perfect
04 · Routing
Where the alert goes is up to you.
ROUTING
By zone, time, role
After-hours alerts go to the duty manager. Working-hours alerts go to the team channel. Critical alerts always copy ops leadership. All scriptable.
ACKING
Closing the loop
Every alert has an ack URL. Click in Slack, on your phone, in email. Acknowledgements are logged, audit-ready, and visible to the next person on shift.
05 · Quiet alerts. Loud signals.