Five delivery channels, per-user preferences, quiet hours, severity routing, and acknowledgment tracking. Visylix notifications are built to prevent alert fatigue while ensuring nothing critical slips through.
Design Your Alert FlowFrom push notifications to MQTT, choose the channels that fit your operator workflow, IoT stack, and downstream integrations.
Planned for the iOS and Android apps, which are on the roadmap and not available today: push with rich payload (event thumbnail, camera name, zone, tap-through to live video).
SMS for critical alerts delivered to operator phones, so an on-call responder is reached even when they are away from a screen.
Email notification with the event details (camera, event type, and time) sent to each operator who has email delivery enabled.
Outbound webhooks with HMAC-SHA256 signatures. Custom endpoints, retries with exponential backoff, and secret rotation without downtime.
Native MQTT broker for IoT sensor fusion. Publish detections to configurable topics and subscribe to sensors for correlated video-and-sensor timelines.
Routing, scheduling, and acknowledgment controls keep operator channels clean while guaranteeing critical alerts never get missed.
Silence non-critical alerts outside working hours. Per-user schedule with timezone awareness. Critical alerts always break through.
Critical → SMS + oncall push. High → email + dashboard. Medium → digest. Low → dashboard only. Fully configurable per tenant.
Alerts require operator ack within SLA window. Auto-escalate unacknowledged critical alerts up the chain. Full audit trail of who ack'd what and when.
Each operator opts in only to alert types, cameras, zones, and severities they care about. No global spam, just the right alerts to the right people.
Per-user preferences, user-selectable quiet hours, and severity routing keep noise down. Acknowledgment tracking keeps critical alerts from slipping through.
Four channels available today: SMS via Twilio (Scale and Enterprise tiers), email with inline event thumbnails, HMAC-signed webhooks for custom endpoints, and MQTT for IoT/SCADA integration. Mobile push would arrive with the iOS and Android apps. Each channel is independently subscribable per user.
Per-user subscription preferences let each operator opt in only to the alert types, cameras, and severities they care about. Quiet-hours scheduling silences non-critical alerts outside working hours. Severity routing delivers critical alerts to oncall rotation while routine events only appear in the dashboard. Acknowledgment tracking prevents duplicate escalation.
Yes. Every outbound webhook carries an HMAC-SHA256 signature header computed over the payload with a shared secret. Webhook receivers verify the signature to ensure the event is authentic and un-tampered. Signature rotation is supported without downtime.
Yes. Alerts carry a severity (critical, high, medium, low) derived from AI confidence, zone configuration, and event type. Routing rules deliver critical alerts to SMS and oncall push, high to email and dashboard, medium to dashboard and email digest, low to dashboard only.
Yes. Visylix ships with a native MQTT broker for IoT sensor fusion (temperature, smoke, motion, ACS, SCADA). Alerts and detections publish to configurable topics, and external sensors can publish events to Visylix for correlated video-and-sensor timelines.