India has over 100,000 gated residential communities, and managing one is harder than it looks from the outside. Visitor logs, maintenance dues, staff attendance, amenity bookings — the paperwork never ends. Dozens of software platforms have tried to fix this. Most of them work reasonably well. And yet, walk into any society using one of them and you will hear the same complaint: only half the residents actually use it.
That number — 40 to 60 percent adoption — is not a fluke. It is a structural ceiling, and it is baked into the model.
The install problem
Every app-based platform asks residents to do the same sequence of things: find the app in the store, install it, create an account, verify a phone number, connect to their society, and then remember to open it when something happens at the gate. For a 35-year-old with a smartphone habit, this is unremarkable. For an elderly resident, a tenant who has been there three months, or a domestic worker managing a flat while the owner is abroad, each of those steps is a reason to drop out.
The society manager cannot mandate the app. The resident who does not install it still needs to be told when a visitor is waiting at the gate. So the guard picks up the phone and calls. The manual process persists alongside the digital one, which means the society is running two systems at the cost of one.
WhatsApp is already installed
Over 500 million people in India use WhatsApp. In most residential societies, the penetration is close to 100% — including the elderly residents, the tenants, and the family members who would never think to install a dedicated app. The society already has a WhatsApp group. Residents already know how to tap a button in a chat.
When we designed UnitSync, we started from a simple question: what if the resident never had to leave WhatsApp?
The answer turned out to be cleaner than we expected. When a visitor arrives at the gate, the guard logs them on the Guard PWA — a browser-based interface that runs on any Android handset, no install required. The resident gets a message in their existing WhatsApp from UnitSync. They tap Approve or Deny. The gate opens. That is the entire interaction from the resident's side.
No app. No account. No password. No store.
What this changes
The practical effect is that adoption stops being a product problem and becomes a communications problem. Society managers do not need to run onboarding campaigns or chase residents to install something. They announce that UnitSync is live, and the next time a visitor comes, residents discover the experience themselves — inside an app they already use every day.
In pilot societies, we are targeting 85% or more of residents actively receiving and responding to visitor requests within the first week. That is not because UnitSync is better-designed than the alternatives. It is because the alternatives asked people to change their behaviour, and UnitSync did not.
The tradeoffs
Being WhatsApp-native is not free of constraints. We work within what WhatsApp's Cloud API allows — structured Flows and interactive buttons, not arbitrary interfaces. We cannot build the same depth of UI that a native app offers. There are things we will not be able to do over WhatsApp that a dedicated app could handle more elegantly.
We made that tradeoff deliberately. A 90% adoption rate with a simpler feature set is more useful to a society than a 50% adoption rate with a richer one. The residents who are not on the platform are precisely the ones who matter most for visitor management and emergency alerts — the people who live there but do not carry a smartphone habit into every interaction with their home.
What comes next
UnitSync is live for visitor management today. Maintenance payments, community notices, and complaint ticketing are next. All of it will go through WhatsApp, because that is where the residents are.
If you manage a residential society and want to see what this looks like in practice, get in touch.