Overview 01 How it works 02 Escalation 03 Platforms 04 Channels 05 Security 06 ← Back to xplug.in Request a pilot
xplug.in /SmartNotifier /Channels
— Delivery channels

The channel your responders already have open

Channels are a delivery detail, not the product — but the detail matters, because the wrong one means an alert nobody sees. Here is exactly what arrives, how it is acknowledged, and what you have to supply.

WhatsApp

Responder seesA template message with the snapshot as the media header: camera, zone, severity and local time in the body.
AcknowledgeReply ACK or DISMISS. The reply is matched to the sender's number, so the acknowledgement carries a named identity rather than an anonymous button press.
You supplyA WhatsApp Business Platform account — Meta Cloud API or Twilio — with its phone number ID and access token.
SetupRecipients opt in once. Alerts go out as approved utility templates, so they arrive at any hour rather than only inside a 24-hour customer-service window. Inbound replies reach the backend through a webhook you point at your own server.

Telegram

Responder seesA photo message with the snapshot and the alarm detail in the caption.
AcknowledgeInline Acknowledge and Dismiss buttons carrying the alarm reference.
You supplyA bot token from BotFather, and the chat ID of each recipient or group.
SetupEach recipient starts a chat with the bot once so it is allowed to message them. Nothing else.

Microsoft Teams

Responder seesAn Adaptive Card, colour-coded by severity, with the snapshot and the alarm fields laid out as facts.
AcknowledgeAction buttons on the card.
You supplyAn incoming webhook URL for the channel that should receive the alarms.
SetupCreated from the Teams channel itself in a minute or two. One webhook per channel, so different zones can post to different channels.

Slack

Responder seesA Block Kit message with the snapshot and the alarm fields.
AcknowledgeAction buttons on the message.
You supplyAn incoming webhook URL, or a bot token if you want acknowledgement buttons to resolve to a Slack identity.
SetupStandard Slack app install into your workspace.

PagerDuty

Responder seesAn incident in your existing PagerDuty service, opened through the Events API v2 with the alarm as the payload.
AcknowledgeAcknowledging in PagerDuty resolves the incident and stops SmartNotifier's ladder; acknowledging in SmartNotifier resolves the PagerDuty incident.
You supplyA routing key for the service the alarms should open incidents against.
SetupNone beyond creating the service. Severity maps onto PagerDuty's own levels.

Email

Responder seesAn HTML message with the snapshot attached, as a fallback channel or a primary one.
AcknowledgeA link back to the acknowledgement endpoint.
You supplySMTP host, port, credentials and a from-address.
SetupNone. This is the channel that works when a site's policy rules out everything else.
WhatsApp delivery uses the official WhatsApp Business Platform — Meta Cloud API or Twilio. Alerts are sent as approved message templates, so they arrive reliably at any hour. Recipients opt in once; there is nothing to install.
You are not choosing one channel. A single alarm can go to several at once, and escalation levels can use different channels entirely — WhatsApp at level 0, Teams and email at level 1.
— 30-day pilot

Run it on your own system
for 30 days.

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.

Request a pilot Back to the overview