From the console to email, SMS and your other systems, and on to sirens, door strikes and talkdown, Visylix makes sure the right person knows, and the site responds, in seconds. Critical alerts that go unanswered escalate on their own.
Design Your Alert FlowChoose the channels that fit your operators, your building systems and your security tools.
Alerts land on the alert rail and in the alarm console the instant they fire, with a snapshot and a one-click jump to the recorded second.
Critical alerts reach on-call responders by text message, even when they are away from a screen.
Alert emails with the camera, event and time, plus a daily security digest written by Radha on your own servers.
Do more than notify. Rules speak through camera speakers and switch siren and door-strike relays the moment something happens.
Send any event to any system with a signed webhook. Set the address, headers and message for each rule, with automatic retries and a dry run.
Feed security events into your SIEM and forward incidents to your PSIM, so Visylix fits the control room you already run.
A built-in MQTT broker connects sensors and building systems. Publish detections to your topics and bring sensor readings into the video timeline.
Routing, schedules and escalation keep channels calm while making sure critical alerts are never missed.
Silence routine alerts outside working hours on each person's own schedule. Critical alerts always get through.
Each operator sets a severity limit for their channels, and each rule chooses which channels it uses. Below the limit, alerts stay in the console.
Critical alarms that are not acknowledged in time escalate automatically, with a timestamped note and a fresh notification. The audit trail shows who acknowledged what, and when.
Each operator picks the alert types, channels and severities they care about, and only sees the cameras they are allowed to. The right alerts reach the right people.
Personal preferences, quiet hours and severity routing keep the noise down. Escalation makes sure nothing critical slips through.
Alerts appear instantly on the alert rail and in the alarm console in the browser. They can also go by email and SMS, as a daily security digest by email, and to other systems through HMAC-signed webhooks, MQTT, SIEM and PSIM. Each person chooses the channels and severities they want, and each automation rule can choose which channels it uses.
Yes. Sudarshan rules can speak a talkdown warning through the camera speaker and switch siren and door-strike relays wired to your cameras. Physical actions run once an administrator has armed the rule.
It escalates. The alarm console raises unacknowledged alarms by priority, adds a timestamped note and sends a fresh notification, and every acknowledgement is recorded in the audit trail.
Each operator subscribes only to the alert types, cameras and severities they care about. Quiet hours silence routine alerts outside working hours, while critical alerts always get through. Rules can snooze, cap firings per hour and pause during maintenance windows, and every alert carries a dispatch score so the most urgent come first.
Yes. Every outgoing webhook carries an HMAC signature, so the receiving system can confirm the event is genuine and unaltered. Each rule can have its own secret, and failed deliveries retry automatically.
Yes. MQTT is a lightweight messaging standard used by sensors and building systems. Visylix has a built-in MQTT broker: alerts and detections publish to topics you choose, and sensors such as temperature, smoke and motion can send events back to Visylix to appear alongside the video.