Relayion
← Use cases
Internal · Ops

Staff alerts & approvals

Ops teams need people to respond to incidents quickly. The most reliable channel is the one that requires nothing on the recipient's end. No app, no login, no notification permission. That's SMS.

SMS · OUTBOUND
[OPS] Site EAST-3 offline. Reply ACK to acknowledge.
↩ "ACK"

When a monitoring system detects an incident, it needs to reach the on-call engineer. That engineer may not have the company app installed on their personal phone. They definitely have SMS. Relayion lets your alerting system send over a real SIM with no carrier contract, no shared number pool, just a device that holds a persistent connection to the API.

The alert goes out through Relayion's API. The engineer replies with ACK, DONE, or a status message. The reply arrives at your webhook. Your system updates the incident record, silences the alert, or triggers the next step in the runbook.

This pattern works for more than incidents. Purchase order approvals, leave request confirmations, and shift change acknowledgements all follow the same logic. Any workflow where a human reply triggers the next step can be handled over SMS without requiring any setup on the recipient's end.

Because the number is consistent, engineers learn to recognise it. Over time, an alert from that number carries its own signal before the message is even read.

Send an incident alert
POST /api/v1/outbound HTTP/1.1
Authorization: Bearer rlyn_bfb4d3c9…
{
"recipientNumber": "+61 4 5555 0199",
"body": "[OPS] Site EAST-3 offline for 4 min.
Reply ACK to acknowledge."
}
// Engineer replies, arrives at your webhook
{ "event": "inbound.received", "data": { "body": "ACK" } }
More use cases

Ready to connect your first device?

Free plan. One device, 500 messages per month. No credit card required.

Get started free →Read the docs