Skip to content
Camzify
Automatic Escalation

Guard notifications

A guard notification is an automatic alert sent to the security guard assigned to a specific camera when a checklist item is marked Not Compliant during a virtual patrol round. Each notification carries a predefined message explaining what was found and what action is expected.

Book a demo The alert queue
An event detail in the Camzify console showing the camera snapshot behind a failed check and the guard message sent

Named guard per camera

Every camera in the patrol sequence has an assigned guard with contact details. No ambiguity about who is responsible.

Predefined messages

Each checklist item has a pre-written escalation message. "Gate left open after delivery, close immediately."

Instant delivery

Notifications are sent the moment a failure is logged. The guard knows what happened and where before anyone else.

Why It Matters

Why guard notifications matter

A failed checklist item is only useful if it reaches someone who can act on it. Without an automatic alert, that failure sits in a report until an operator happens to review it, which might be minutes later, or might be at the end of the shift, long after the gate has been left open or the zone has stayed unattended.

Radioing around or calling the guard on duty works occasionally, but it depends on someone remembering to do it, knowing who is actually covering that camera right now, and reaching them on whatever channel they happen to have open. None of that is guaranteed, and none of it leaves a record of when the guard was told or whether they responded.

Tying the notification directly to the checklist item removes the guesswork. The moment a result is logged as Not Compliant, the system already knows which camera it came from, which guard is assigned to it, and what message to send, so the alert goes out immediately, to the right person, with no one in between.

Examples

What a notification looks like

Each message is written when the checklist item is created, so it names the problem and the expected action rather than leaving the guard to guess.

Gate left open after delivery — close immediately
Unauthorized person in loading zone — investigate now
Fire exit blocked — clear immediately
Vehicle not in designated bay — reposition
Dock door left unsecured — confirm and lock
Corridor obstruction reported — remove and log
The notifications screen listing alerts with their camera, severity and acknowledgement state
The notifications queue: every message sent, to whom, and whether it was acknowledged.
How It Flows

How notifications flow

  1. 01Patrol round reaches a camera in the sequence
  2. 02Checklist item is evaluated as Compliant or Not Compliant
  3. 03On failure, the system retrieves the guard assigned to that camera
  4. 04The predefined message for that checklist item is sent to the guard
  5. 05The notification is logged in the patrol report
Configuration

Escalation and delivery channels

Notifications aren't a single fire-and-forget message. Delivery and escalation are configured per guard, so coverage doesn't depend on one phone being switched on.

  • • Each guard can have multiple channels configured, email, SMS, WhatsApp and push, in a preferred order
  • • Acknowledgment is required within a configurable window before an alert counts as unactioned
  • • Unacknowledged alerts escalate automatically to a backup guard or site supervisor
  • • Escalation contacts are set independently of the primary guard, so backup coverage is never assumed
FAQ

Frequently asked questions

No. An automated round also raises critical notifications for safety and security risks it observes at a stop, even where no checklist item covered them; see risk detection on patrol. Those arrive on the same channels as a failed checklist item and expect the same acknowledgment.

It depends which kind of round found the problem. On an automated round it is sent automatically as the round runs, with nobody in the loop, which is the whole point of a round that happens at 3am. On a manual round the operator is already looking at the camera, so the message is offered with the specifics filled in and they choose to send it, skip it, or send it later from the same item.

If the guard doesn't acknowledge the alert within the configured window, it escalates automatically to a backup contact or site supervisor. The failure is never left waiting on a single person's availability.

Yes. A camera can carry a primary guard who receives the first notification, plus one or more escalation contacts who are only alerted if the primary doesn't acknowledge in time.

Each checklist item carries its own predefined message, written when the checklist is set up. A gate-related failure and a loitering failure can trigger entirely different wording, tailored to what the guard actually needs to do.

Email, SMS, WhatsApp, and push are all supported. Guards can have more than one channel configured, and the order they're tried in is set per guard rather than fixed for the whole site.

Yes. Every notification, with who it was sent to, when, and whether it was acknowledged, is written into that round's patrol report, so there's a record independent of the guard's own memory of the shift.

Related

Patrol Checklists Platform Notifications Guard Tour Verification

Ready to patrol your site 24/7?

Book a 15-minute demo and see a live patrol run on your own cameras.

Book a DemoCalculate Your Savings

This site is being updated

We are rebuilding pages as you read this, so an image, a link or a section may look unfinished for a while. The product itself is unaffected. If something important is broken, tell us at the contact page and we will fix it.