A panic button in the pocket
of every guard and every client
One tap in the app and the whole response fires: an audible alarm and on-screen alert in your dispatch center, an immediate notification to the guards nearby, and a top-priority case nobody can dismiss until it has been acknowledged, dispatched and closed. The same protocol protects your officers and your clients.
Real product screenshots
The problem with emergencies that have no protocol
The guard is on their own
In a robbery or a medical emergency, dialing a phone takes minutes nobody has. With no panic channel, the officer is betting that someone picks up.
The alert drowns in the noise
One more message in a group chat is not an emergency protocol. With no forced escalation, the calls that matter get read too late.
Nobody documents the response
Who received the alert, when help was dispatched, when it was resolved — with no record, you cannot prove your response time to a client.
What happens when someone hits SOS
Alarm in dispatch
Your dispatch center gets an audible alarm and an on-screen alert with the identity, the post and the GPS location of whoever asked for help.
The team on site finds out
Guards assigned to that site get an immediate push notification to respond or secure the perimeter.
A top-priority case opens
A maximum-priority case is created that demands acknowledgment, dispatch and resolution — the alarm persists until somebody answers.
Everything is documented
Acknowledgment, dispatch and closing times are all recorded: your real response time, provable to the client.
A response, not a hope
- Guard SOS and client SOS run the same complete protocol
- Persistent alarm in dispatch until a human acknowledges it
- GPS location and post context attached to every alert
- Simultaneous notification to the guards on that site
- Case states (acknowledge, dispatch, resolve) with measurable times
- Emergency history by site and client, ready for audits
Frequently asked questions
Is the panic button only for guards? +
No. Your clients get SOS in their own Mi Seguridad app: activating it fires the same complete protocol — alarm in your dispatch center, alert to the guards on that site, and a priority case with follow-up.
What stops an alert from going unanswered? +
The alarm in dispatch is persistent and the case stays at maximum priority until an operator acknowledges it. It is not a message that can be scrolled past: it is a queue with mandatory states.
Does the alert include the guard's location? +
Yes: identity, assigned post and the device's GPS position at the moment of activation, so you dispatch help without guessing.
Does this replace calling 911? +
No — it complements it. CGuardPro coordinates your own operational response; 911 and law enforcement remain the right call for the event itself. The difference is that your dispatch center knows within seconds and acts in the meantime.
Can I measure my dispatch center's response time? +
Yes. Every case records activation, acknowledgment, dispatch and resolution times — real metrics for your service reports.
Trigger a live SOS in the demo
We fire a test panic and you watch the alarm hit dispatch, the alert reach the team and the priority case open — the whole protocol, in seconds.