Anyone can push an event to Teams. This is the part that takes the other eleven months: deciding who hears about an alarm, proving that they saw it, and doing something about it when they didn't.
A rule matches on any combination of these dimensions. An unset condition means match-all.
Perimeter* catches every perimeter alarm without listing them.Critical, High, Medium, Low — normalised from the VMS priority before the event leaves the plugin.No app, no login, no account to create.
ACK or DISMISS. The reply is matched to the sender's number, so the acknowledgement carries an identity.When an alarm is ingested, an escalation check is scheduled for the acknowledgement timeout. When it runs, one of three things happens.
An illustration of one alarm's record, with a 60-second acknowledgement timeout and two escalation levels.
When it fired, which rules matched, every message sent and to whom, whether each delivery succeeded, who acknowledged and at what time, and every escalation step along the way. Searchable, exportable, and retained for as long as you configure.
For a monitoring operation, that record is the evidence of an SLA being met. For everyone else, it's the answer to "what happened last Tuesday night?"
We install it, configure your rules with you, and you see exactly what your team sees. No cost during the pilot. If it isn't useful, we uninstall it cleanly.