Nobody sits down and decides "we will run our security operations through WhatsApp." It happens by default — someone creates a group during setup, it works well enough for a while, and by the time anyone notices its limits, it's the only system anyone knows.
It isn't that WhatsApp is a bad app. It's that incident management asks it to do things it was never built to do.
There's no structure, so there's no consistency
A chat message can be anything: "guy by the gate acting weird," a voice note, a photo with no caption. Two guards describing the same kind of incident will describe it completely differently, which means nobody downstream — not the estate manager, not an insurer, not a court — can treat those messages as comparable records of what actually happens on the property.
Nothing is addressed to anyone specifically
A message in a 40-person group is, functionally, a message to no one. It depends entirely on someone happening to read it, understand its urgency, and act — and there's no way to know whether that happened until you ask.
There is no record that survives
Chat history gets deleted, phones get changed, people leave the group. Even when the history survives, scrolling back through hundreds of unrelated messages to reconstruct what happened during an incident three weeks ago is not something anyone does reliably, which means in practice the record doesn't exist.
There's no way to verify anything happened
A guard can text "all clear on patrol" without having walked the route. Nothing about the message format stops this, and nothing about it proves the opposite either. This is the direct cause of the "ghost guarding" problem estate managers already know about but rarely have a clean way to catch.
It has no concept of severity
A message about a blocked drain and a message about an intruder look identical in a chat thread — same font, same bubble, same notification. The group has no way to make the second one impossible to miss.
What this actually costs
None of this means the guards or the management are doing a bad job. It means the tool they're using has no opinion about any of the things that actually matter in an incident: who saw it, when, what they did, and whether it's resolved. A system built for casual conversation will always behave like one, no matter how seriously the people using it take their work.
The fix isn't "stop using chat to communicate" — it's recognizing that incident management and casual messaging are different jobs, and giving the first one a tool that was actually built for it.
Lemtik replaces the WhatsApp group with structured incident reporting, verified patrol check-ins, and a record that survives past the next phone upgrade. See how it works.
Subscribe for Updates
Get notified when we publish new articles, product updates, and announcements.