Visitor App is the gate guard's tool — the third piece of the community deployment trio. Visitor walks up. Guard scans the QR from the resident's pre-approval, or runs face-scan, or types the passcode, or registers a walk-in. Resident gets a push. Gate opens. Eight seconds, every time. Behind every check-in: a structured event in the audit log — name, unit, time-stamp, gate, guard on duty. The paper register that lost half the entries by the end of the month is retired. Pairs with Community App at the resident's phone and Community Management at the back office, with the upcoming CAFM App giving technicians their own gate-pass workflow.
Visitor App on its own gives a gate kiosk that scans QRs but has nothing to scan against — no resident pre-approvals, no auto-push to the right unit, no integration to the maintenance ledger. Community App on its own gives residents a payment portal but the visitor pre-approval doesn't sync anywhere — guards still call upstairs. Community vertical on its own gives the manager a billing engine but no real-time gate visibility — the daily visitor count comes from a paper count by the head guard. Deployed as a trio, the three pieces close the loop. And when the manager dispatches a service ticket, the upcoming CAFM App takes over — the technician's interface for actually repairing the asset, with a gate-pass auto-generated through Visitor App so the technician doesn't wait at the boom barrier.
Gate guard's interface · 7 features · QR scan, face scan, walk-in registration, residents directory, multi-gate switching.
Resident's interface · 22 features · visitor pre-approval, family register, bills, service requests, facility booking.
▸ See Community AppManager's web platform · billing engine, complaint workflow, AGM minutes, vendor contracts, audit-grade ledgers.
▸ See verticalTechnician's interface · receives dispatched tickets, auto-generates gate pass through Visitor App, closes work order.
▸ See CAFM AppThe visitor approaches the gate. The guard taps Check In on the app. Camera comes up. The visitor holds up their pre-approval QR (received on their WhatsApp from the resident through Community App). Scan. Detected: visitor name, expected window, resident unit, pre-approval status — all flash up in green. The guard taps Confirm. The resident gets a push notification: Your visitor Suresh has arrived at Gate 02. Eight seconds. If the visitor doesn't have a QR, alternate methods are one tap away — Face Scan (matches against pre-approval photo), Passcode (4-digit pre-shared code), or Manual (guard registers a walk-in, calls the resident through the app). Same flow regardless of method. Same audit-grade log behind every entry.
The guard's reference layer. The Visitor List has four tabs — Check In (currently on premises), Check Out (left already), Late (entered but past expected window), Denied (resident said no, logged for security). Search by visitor name or resident unit pulls instant results. The Residents directory lets the guard verify "I'm here to see Mrs Sharma in B-708" by searching the unit register — every resident's name, photo, contact, family members, registered pets, registered vehicles. Service staff list shows everyone with standing approval — daily help, drivers, milkmen — pre-cleared so they walk through with one tap. Vendor list covers the recurring ones — Voltas service, Amazon delivery, Big Basket. Three reference lists, one search bar.
The supervision layer. The head guard pulls Daily Visitor count for the morning round-up. The community manager pulls Pending Check Out — visitors who entered but haven't logged exit, possibly forgotten by the guard, possibly a security flag. Late Arrivals report shows pre-approved visitors who came after their window. Entry Denied logs every refused entry with the resident's reason — useful when the resident later asks "why didn't you let my cousin in?". Service Staff and Waiting Visitor reports complete the picture. Multi-BU and Multi-Gate switching in the hamburger menu lets the same app run across an estate's gates — the head guard rotates the device or signs in at a different post, picks the gate from the dropdown, and the app context switches instantly.
The paper register exists because someone, decades ago, decided a gate needs a record. The form factor never updated. The Visitor App preserves the intent — every entry recorded, every exit logged — but updates the form factor for 2026: instant scan instead of handwritten name, push to resident instead of intercom call upstairs, structured event in a database instead of a smudged signature. The result: the security audit becomes a query, not a forensic project. The police inquiry becomes a 30-second filter, not a notebook hunt.
I've been head of security at this 600-flat society for eleven years. The first nine years it was a paper register at every gate — three notebooks every month, lost in the cupboard, illegible by week three. Then we deployed the trio. The first month was the loudest silence I've ever heard. No more arguments at the gate, no more calls upstairs, no more "where is my plumber sir." The visitor scans, the resident gets a push, the gate opens. Eight seconds. The boom barrier hasn't backed up at 8 AM in two years.— Head of Security · 600-flat society · Mumbai · 11 years on site
30 minutes for the walkthrough. Three months for a structured pilot at one of your societies. Deploy Visitor App on a tablet at the main gate, Community App for 50-100 resident families, Community Management at the manager's desk. We'll set up multi-gate switching for the second gate when ready, train the head guard on the reports screen, and walk through the audit-export flow. The metrics that improve in week one: gate dwell time, intercom call volume, paper register pages filled.