Designing alerts that people do not mute

Every security system that can send alerts can send too many. Anyone who has run a control room or carried the on-call phone knows the pattern. A system goes live, notifications pour in, most of them turn out to be nothing, and within weeks the channel is muted or an email rule files everything in a folder nobody opens. The system keeps detecting and nobody is listening.

Alarm fatigue is a design problem, and the design choices that prevent it are well understood. An alert keeps its audience when it is rare, relevant to the person receiving it, quick to verify and clear about what to do next.

Start from the response

Write the response before you write the rule. For each alert, name who receives it, what they are expected to do and how quickly. If nobody can name the action, the event belongs in a daily report, where it can be read at a desk in the morning.

Make each rule specific

“Motion on camera 7” fires all day. A useful rule describes one situation that matters, and four settings do most of the work.

• Zone: draw the area that matters, such as the stock room door or the fence line, and leave the public sidewalk out of it.
• Schedule: after-hours presence applies when the site is closed. The same person at noon is a customer.
• Subject: alert on people or vehicles. Detection that recognizes what moved ignores cats, headlights and branches.
• Duration: loitering means staying. Set a threshold that fits the place, short at a cash office door and longer beside a bus stop.

Send it to the person who can act

Route by responsibility. A night-time intrusion goes to the guard or keyholder. A fall goes to the nurses’ station or the shift supervisor. A crowd building at an entrance goes to the duty manager. Camera tampering and offline cameras go to IT or the installer, who can fix them, and stay out of the security channel.

Match the channel to the urgency. WhatsApp and Telegram suit events that need a response in minutes. Email suits events that can wait for working hours. A webhook passes events into systems the organization already runs, such as a ticket queue or a monitoring platform. When an alert goes to a group, name one owner per shift, because five recipients will each assume one of the other four has it.

Let the clip do the verification

A text alert that reads “Intrusion, zone 3” gives the recipient a job: open the app, find the camera, rewind and work out what happened. An alert with the clip attached is verified from the lock screen in seconds.

If the event is real, the recipient acts at once: makes the call, triggers the siren through a relay, or follows the person from camera to camera until someone arrives. If it is harmless, they dismiss it and note the reason, which becomes input for tuning the rule.

Review and prune

Once a month, list each rule with the number of alerts it sent and the number that led to action. A rule that is mostly dismissed needs a tighter zone, a longer threshold or a different recipient. A rule that never fires needs a walk test to prove it still works.

Retire rules that fail the review. A site with six rules that are always answered is better protected than a site with sixty that are ignored. Maiyn Respond delivers each alert with its clip by WhatsApp, Telegram, email or webhook.