How an SOS alert works
The guard presses and holds an SOS button in the app, or in some setups presses the phone's power button several times. The app sends the alert with the guard's name, employee ID, site, post, GPS coordinates and timestamp to a defined list of recipients: the site supervisor, the area manager and the agency control room. Recipients get a push notification, and usually an SMS as a fallback, with a map link to the guard's location.
Good implementations keep updating the location for a few minutes after the alert, let the guard cancel with a PIN if it was accidental, and record who acknowledged the alert and when. That acknowledgment trail is what turns a button into an accountable process.
Escalation chain and response SLA
An alert that reaches ten people and is owned by none is worse than a phone call. Define the chain: the site supervisor must acknowledge within 2 minutes; if not, the area manager is alerted; if still not, the control room calls the guard and, if unreachable, the client's site contact and the police. Write the chain into the post order so guards know what to expect after they press the button.
Set a response SLA per site and measure it: time to acknowledgment and time to a person on site. Night shifts and remote sites need a different chain from a corporate lobby at 11:00, and the client should see the SLA in the monthly report along with any alerts raised.
- Primary responder and backup for each site and shift.
- Acknowledgment time limit before auto-escalation.
- Who calls the police, fire service or ambulance, and when.
- Who informs the client, and how the incident is closed and documented.
False alarms and testing
Pocket presses and curiosity taps are common in the first weeks. Handle them with a cancel-with-PIN option, a short cool-down before the alert transmits, and a habit of calling back the guard on every alert rather than punishing false alarms so harshly that guards hesitate in a real emergency. Track the false-alarm rate per site; a high rate usually means a hardware trigger that is too sensitive, not careless guards.
Test the chain monthly with a scheduled drill: a named guard raises a test alert at a known time, and the supervisor records acknowledgment and arrival times. An SOS button that has never been tested is a promise the agency cannot keep. Every real alert should end in an incident report, which our incident report format covers.
At 01:40 a guard on the 20:00–08:00 shift at a construction site sees three people cutting the boundary fence and presses SOS. The site supervisor's phone rings with a push and SMS showing the guard's name and a map pin at the north fence; he acknowledges at 01:41 and calls the guard, who confirms the intrusion. The area manager, auto-escalated at 01:43, alerts the local police station and the client's project manager. The control room logs acknowledgment at 1 minute, police arrival at 22 minutes, and the guard files an incident report from the app at 02:30.
Attend Mitra's guard app includes an SOS alert that sends the guard's identity, site and GPS location to supervisors and admins by push notification, with SMS as a fallback where configured. Alerts appear on the supervisor dashboard, and incident reports can be filed from the same app to close the loop.