It does not replace the panel's communicator
Our alarm signals are supplementary fault signals. They do not replace the alarm panel’s own communicator.
Alerts go where your people already look
The portal, email, Slack, Microsoft Teams, webhooks, and an alarm signal into your own monitoring software over SIA DC-09.
What it does
One confirmed fault, told once, everywhere you chose
When a device stops answering or reports a fault, we raise one alert. It is shown in the portal and sent by email, to Slack and Microsoft Teams channels, and to webhooks.
Each message names the device as the portal names it, with its address and its site. Every alert email carries an Acknowledge link, and every Slack and Teams message an Acknowledge button.
For a control room, the same fault goes into your own monitoring software as an alarm signal over SIA DC-09. It is sent in SIA or Contact ID format, with the reason in the alarm text. A device offline is "supervision lost" on that device's zone; a fault is a trouble code; a site network down is its own code. A restore signal follows.
Supplementary signalling
Our alarm signals are supplementary fault signals. They tell your control room that a device has stopped answering, has a fault, or that a site’s network is down. They do not replace the alarm panel’s own communicator.
How you use it
Add a channel, choose what each device sends, acknowledge where you read it
-
Add the channels
In the portal, add the email addresses, Slack and Microsoft Teams channels and webhooks that should hear. Each channel chooses which severities it receives.
-
Choose what each device sends
For every monitored device, choose whether its faults go to email, to your monitoring software as an alarm signal, or both. Change it per device or in bulk.
-
Acknowledge in one click
Press Acknowledge in the email or the message. It opens a page that asks you to confirm, so a preview fetched by a mail or chat service acknowledges nothing.
The details
What happens between the fault and the person
- Severities and reminders
- Alerts are critical, warning or info, and each channel chooses which it receives. Today a critical alert repeats hourly three times, then daily, until it is acknowledged.
- Held while it would only add noise
- Alerts for a device are held while its box is offline, while its site's network is down, and while it is muted for planned work.
- The acknowledgement is recorded
- Who acknowledged an alert, or which channel, and when, is kept with the alert. Every alert, the message it sent, and when, stays with the site.
- Alarm signals, by zone
- Each monitored device has its own zone in your monitoring software. A device offline is "supervision lost" on that zone and a fault is a trouble code; a site network down is its own code. When forwarding starts or stops for a device, that is signalled too.
- Encrypted, with a backup receiver
- DC-09 signalling supports AES encryption, a backup receiver and link supervision. The check message is every minute, every 90 seconds, every 5 minutes or every hour, chosen in the portal.
- Your response target
- Set your control room's own response target. The monthly report measures acknowledgements against it, and shows how quickly your control room was alerted after each fault was confirmed.
- Which plan includes it
- Alerts, alarm signals, webhooks, acknowledge links and monthly reports are in the Relay + Alerts plan. On the Relay plan, alerts still appear in the portal but nothing is sent. See Pricing.
What it does not do
Three limits, said plainly
It sends nothing on the Relay plan
On the Relay plan, alerts are raised and listed in the portal, but no email, message, webhook or alarm signal is sent. Your settings are kept.
It cannot alert for devices at a site that cannot reach Relayant
Our service raises alerts and alarm signals. While a site cannot reach Relayant, its box is reported offline and nothing else is raised for its devices. Your local relays' camera connections keep working.
Send each fault to the right person
Tell us what monitoring software your control room runs and where your team reads its messages. We reply by email.