Security guarding carries real, ordinary risk โ a confrontation at a gate, a medical emergency on a night shift, a break-in in progress. When something goes wrong, the guard on the ground needs a way to raise an alarm that reaches the right people in seconds, not a phone call that might not connect or a WhatsApp message someone checks an hour later. That's what Raksha Kavach's emergency system is built for.
The guard's SOS button
Every guard has an SOS button in their mobile app, confirmed with a quick tap to prevent accidental triggers. Pressing it immediately alerts the company's admins, HR, and โ critically โ the supervisor responsible for that specific site, along with the guard's live GPS location at the moment the alert was raised. The people closest to the situation, not just head office, are in the loop from the first second.
HQ can raise the alarm too
Emergencies don't only originate with a guard. HQ can broadcast an alarm outward โ to guards and supervisors at a site or across the company โ for situations like a nearby law-and-order incident, a weather warning, or an evacuation notice. It runs through the same alert pipeline as an SOS, just reversed in direction.
Every alert becomes a real incident ticket
An alert isn't just a push notification that disappears once read. Each one becomes a tracked incident with its own number, a severity level (from routine up to critical), and a clear status lifecycle โ Active, then Acknowledged once someone responds, then Resolved once it's actually handled, with optional resolution notes recorded at that final step. Photos, video or audio can be attached to an alert as evidence.
Response and resolution timers
Raksha Kavach automatically measures how long it took from an alert being raised to being acknowledged, and separately from acknowledgment to resolution. Over time, that data tells an agency owner something a gut feeling can't: whether their emergency response is actually fast, or whether a particular site or shift consistently sees slow acknowledgment.
Auto-escalation when nobody responds
An alert that sits unacknowledged is the worst-case failure of any emergency system โ everyone assumed someone else saw it. Raksha Kavach checks for exactly this: an alert still unacknowledged after 5 minutes automatically re-notifies the relevant managers, so a gap in attention doesn't turn into a gap in response.
Severity level decides who gets pulled in and how loudly โ critical alerts are designed to reach the right people through more than one channel, not just an app notification someone might miss.
SMS, WhatsApp and voice calls โ ready, pending your own account
Beyond in-app and push notifications, Raksha Kavach's architecture already supports sending SMS, WhatsApp messages, and even an automated voice call for the most severe alerts, via Twilio. This is fully built and wired โ it activates the moment an agency connects its own Twilio account, at which point high-severity alerts start reaching managers on channels that don't depend on someone having the app open.
Conclusion
An emergency system is only as good as what happens in the seconds after someone presses the button. By turning every SOS or alarm into a tracked incident โ with the right people notified immediately, timers measuring response speed, and automatic escalation if nobody answers โ Raksha Kavach is built around the assumption that in a real emergency, nothing should be left to hope someone noticed.