IoT Alarms & Escalation Chains That Reach People | Kilo

Alarms & Escalation

IoT alarms with escalation chains that reach someone

When a cold-storage sensor breaches at 3 AM, the right person needs to know — immediately, reliably, through the right channel. Kilo's alarm management system turns sensor events into structured operational alerts: five severity tiers, multi-step escalation, email, SMS, and push, and a mobile app whose Critical alerts wake a silenced phone.

Included in every plan · Free for 5 devices

app.kiloiot.io · Alarms

Real product
Click to enlarge
Alarm definitions and the live inbox

Nobody left unnotified

Escalation chains: unacknowledged alerts climb the ladder

Every alarm definition carries an ordered escalation chain. The first step fires immediately when the alarm triggers; if it stays unresolved after a configurable delay, the next tier fires — new recipients, new channels — and so on until someone resolves it or the chain is exhausted. Resolution at any point halts all remaining steps.

A 3 AM cold-storage breach: the on-call technician gets email and push immediately. Unresolved after the delay? The shift supervisor gets SMS and email. Still unresolved? The site manager gets SMS — a potential compliance event now has management awareness, automatically.

Five severity tiers

Severity policies that match operational priority

Five levels — Critical, High, Medium, Low, Info — classify every alarm, and each level carries its own repeat policy: a recurring reminder interval in hours or days while the event stays active, or a one-time notification. Individual alarm definitions can override the global policy when one alarm needs its own cadence.

Critical

Production-stopping conditions — keep repeating until someone responds.

High

Urgent deviations like cold-chain drift or pressure anomalies.

Medium

Operationally significant — capacity thresholds, maintenance triggers.

Low & Info

Awareness and background reporting — ideal for one-time delivery.

Email · SMS · Push

IoT alerts by email, SMS, and push — Critical alerts wake the phone

Every escalation step picks its own recipients and channels for its IoT notifications. Email contacts are verified before they receive anything; SMS runs on a flexible credit add-on — buy bundles when you need them, credits stay valid for a full year; and push reaches responders through the IoT Alerts mobile app for iPhone and Android.

The app holds Apple's Critical Alerts approval: a Critical alarm opens a full-screen alert with a looping tone that breaks through silent mode and Do Not Disturb — with the responder's permission — while lower severities arrive as ordinary notifications. From the full-screen alarm, "Dismiss & Acknowledge" resolves the event for everyone and halts escalation.

Signal, not noise

Suppression windows, schedules, and quiet hours

Alert fatigue kills response times, so every alarm definition carries its own noise controls.

Suppression windows

Suppress duplicate firings for 1–60 minutes when a sensor reports frequently.

Per-alarm schedules

Day-of-week toggles and a From/To time range — 24/7 by default, business hours or night shift when you need it.

One-time or repeating

Per severity or per alarm: a single notification, or a repeat interval until resolved.

Enable / disable per definition

Switch an alarm off without deleting it — it simply stops firing until you switch it back.

One triage queue

The alarm inbox that closes the loop

Every fired alarm lands in the Inbox: filter by severity and status, search by title, and mark events resolved — which immediately cancels any remaining escalation steps. Each event links straight to the originating rule in the rules engine, so investigating "why did this fire?" is one click, and fixing a noisy threshold is the click after.

For system integrators

An alarm management system for the whole response chain

Your client's escalation policy — who is notified, in what order, through which channel, on which shift — stops being a paragraph in a handover document and becomes configuration: severity tiers, timed escalation steps, schedules, and suppression, all visible and auditable in one place.

Book a call

FAQ

Alarms FAQ

Can an alert really break through a silenced phone?

Yes — for Critical severity. The IoT Alerts app (iPhone and Android) holds Apple's Critical Alerts approval, so a Critical alarm opens a full-screen alert with a looping tone through silent mode and Do Not Disturb, provided the responder grants the permission. Lower severities respect the phone's normal notification settings.

What happens if the first responder doesn't react?

The escalation chain continues: after each configurable delay, the next step notifies additional recipients through additional channels — supervisor, then site manager, for example. The moment anyone resolves the event in the Inbox, all remaining steps are cancelled.

How do I stop a chatty sensor from spamming everyone?

Three tools: a suppression window (1–60 minutes) that swallows duplicate firings, per-severity or per-alarm repeat policies (including one-time delivery), and a per-alarm schedule so an alarm only fires during the hours it matters.

How does SMS pricing work?

SMS is a flexible add-on: buy credit bundles when you need them from the subscription page — your balance and per-message cost are shown there — and credits remain valid for a full year.

Never miss a 3 AM breach again

Start free with 5 devices, define your first alarm, and put the escalation chain to the test — no payment details required.