Gated communities and apartment societies
Every entry has a name.
Every name has a time.
A paper register at the gate is either incomplete or illegible, usually both. Vistr gives the guard a screen with four buttons and the resident a notification they can actually answer.
Built for the gate, not for the annual general meeting.
- Guard-first interface, not resident-first
- Delivery entries handled separately
- Approval or rejection in one tap
- Exportable visitor history
What the gate records
-
Visitor passes
A resident issues a pass for a guest with a validity window. The guard checks the code, logs entry, and the pass expires on its own — no phone call to the eleventh floor.
-
Deliveries, done separately
Twenty delivery riders a day do not need the same flow as a guest. A fast delivery entry records the company, the flat and the time, and lets the resident choose at the gate or at their door.
-
Domestic staff and repeat visitors
A daily help, a driver, a tutor. A standing entry with a photo and a fixed time window removes the same handwritten name from the register every morning.
-
A record that exports
When something goes missing or a committee asks a question, the answer is a filtered list by date, flat or visitor, not a search through a wet notebook.
Four taps at the gate
-
Guard opens the entry screen
Large targets, no login prompt per visitor, no scrolling through a resident directory to find a flat.
-
Choose visitor, delivery or staff
Three paths, because they are three different questions. A delivery does not need the same fields as a relative staying for a week.
-
The resident approves
A notification with the visitor's name and photo. One tap to allow, one to decline. A non-response after a set time is not consent.
-
Exit is logged too
An entry without an exit is not a record, it is a rumour. Exits close the visit and make the daily report mean something.
The register problem is not compliance, it is legibility
Most societies have a register because a rule requires one. It is filled in at rush hour by a guard holding a pen and a parcel, so half the entries are unreadable, the exit column is empty, and nobody knows who was in the building at eight last Tuesday. A digital log is only better if it is faster than the pen. That is the design constraint, and most visitor apps fail it because they were built for the resident's phone rather than for the guard's hand.
- The guard's screen is the product. The resident's app is the convenience.
- Fewer mandatory fields at the gate, more detail added later.
- Works on a low-cost tablet mounted at the gate, not only on a phone.
- Offline-tolerant: an entry recorded without signal syncs when it returns.
For committees and guards
Does every visitor need the app?
No. Residents approve visits; visitors do not install anything. A guest can be given a pass code or simply be logged by the guard with the resident's approval.
What happens if the internet is down?
The gate keeps a local log and syncs when the connection returns. A visitor system that stops working during a power or network outage is worse than paper, so this is a core requirement rather than a premium feature.
Who can see the visitor data?
The committee and the guard on duty, for the purpose of running the gate. Residents see their own visitors. Data is not sold, and the retention period is set by the society rather than by us.
Is this a CCTV replacement?
No. A camera records an image; a visitor log records who was expected and whether the resident let them in. They answer different questions and a serious gate has both.
A register that survives an audit.
Every visitor, delivery and domestic worker, with a time in, a time out and a resident who approved it.