Every Visitor Expected.
Every Entry Accounted For.
Book a visitor appointment and the host knows before anyone arrives. Check them in with a photo and an ID, hand them a pass, and the register answers the only question that matters in an emergency: who is on this site right now. Couriers, material and staff stepping out are on the same digital register.
Companies already running their gates on VizPass
Same gate. Two very different mornings.
The way it runs today
- ×A paper book at the gate — names nobody can read, and no photo against any of them
- ×The guard phones around to find the host while the visitor waits in reception
- ×Half the entries have no exit, so the count on the page is wrong by lunchtime
- ×Couriers pile up on the reception desk until somebody recognises a name
- ×Material leaves on a signature in a diary, and the challan is found later or never
- ×Nobody can answer “who is inside right now?” — which is the one question a drill asks
The way it runs on VizPass
- ✓The visit is booked before arrival; the host knows who is coming and when
- ✓Check-in captures the ID and the face, and issues a numbered pass in seconds
- ✓“On site now” is derived from check-ins and check-outs — never typed, never stale
- ✓Couriers are logged to a named recipient, with proof of handover
- ✓Nothing leaves the gate without an approval, and returnable material is chased
- ✓Any day, any register, exported to CSV in one click — it is your data
What people come to VizPass to fix
All use casesFrom the gate to the register, in three moves
Expect them
Book the visit, or send an invite link and let the visitor fill in their own details before they travel.
Check them in
Capture the ID and a photo at the gate, issue a numbered pass, and the host is told the moment it happens.
Check them out
The pass closes when they leave. Until it does they are counted as present — which is what makes the register worth trusting.
What actually happens in your first afternoon
No consultant, no implementation fee, no six-week project plan. This is the whole thing, in order.
Create the company
Name, timezone and your working week. Then add your sites and their gates — a site with two entrances wants two gates, because a visit is recorded against the gate it happened at.
Fill in the gate lists
Why people visit, what ID you accept, the badge numbers you hand out. These are the columns your register is read by later, so they are worth ten minutes now.
Bring your hosts in
Import the staff list or add them by hand. A host needs a name, an email and a phone — that is how they are told somebody has arrived for them.
Put somebody on the gate
Give the guard the Security Guard role and the front desk Receptionist. A guard gets the gate and nothing else — no staff records, no settings.
Run one visit end to end
Book a real visit, open the invite yourself, check them in at the gate and check them out again. That is the system live.
Switch on the rest as you need it
Couriers, material in and out, exit passes and attendance are each a switch. Start with the front desk and add the others once the gate is running.
Stuck at any step? A human replies — but the point is that you should not need one.
Everything That Crosses Your Gate, On One Register
Who is on site, right now
Derived from check-ins and check-outs, never typed and never stale. It is the list somebody reads out during an evacuation — so a visitor still inside on an expired pass is flagged in red, not buried.
How it works →A pass with a photo and an ID
Capture the face and the document at check-in, issue a numbered pass, and keep both against the visit. A returning visitor is recognised, not retyped.
See the register →Couriers that reach their owner
Every parcel logged in and out, with proof of handover.
Material in and out
Items, vehicle and challan on the way in; an approval before anything leaves.
Staff stepping out
An out gate pass with a reason, an approval and a recorded return.
Attendance, if you want it
Punches, shifts and overtime for the people behind the gate.
WhatsApp-native. 10 languages.
The host hears about their visitor where they already look; every screen reads in the language your team picks.
A register you can defend to anyone
Because every entry and exit is captured as it happens — not reconstructed afterwards from a book — the count is defensible: who is inside, who let them in, what they brought, and when they left.
- A live on-site count, derived from the register rather than typed
- Every pass carries the photo and the ID that was checked
- Material and couriers on the same register as the people
- An immutable audit trail behind every approval
Sound familiar?
The register is a paper book
Names nobody can read, No photo, No ID, and no way to answer "who is inside?" without turning pages at the Gate.
The host finds out on arrival
The Guard rings a desk phone, Somebody walks down, and the Visitor waits in Reception while it gets sorted.
Nobody checks anyone out
Half the book is check-ins with no matching exit, so the site count is wrong by the afternoon and useless in a drill.
If two of the three sound familiar, the trial will pay for itself in the first week. Free 7-day trial →
"A visitor book tells you who came. It cannot tell you who is still inside. That gap is the whole reason this product exists."
One price a month, by what you switch on.
No implementation fee. No setup charge. Cancel whenever you like and take your data with you.
The questions owners actually ask
What happens if somebody forgets to check a visitor out?
They stay counted as present, and once their pass expires they show as overstaying — so the count corrects itself and the host is chased, instead of the register quietly lying.
Do I need someone technical to set this up?
No. There is no server to install and no configuration project. If you can fill a form you can add your gates, invite your hosts and check the first visitor in the same afternoon.
Does it work on more than one gate, or more than one site?
Yes. Every visit is recorded against the gate it happened at, sites keep their own gates and passes, and company-wide rules — visitor types, approvals, the watchlist — apply everywhere at once.
Will it work for the guard on the gate?
It runs in the browser on a basic Android, and installs to the home screen like an app in two taps. Big buttons, one flow, and the guard's language.
What happens to my data if I leave?
You export every record to CSV whenever you want, including after you cancel, during the wind-down window. No lock-in and no exit fee.
Do we have to take the whole thing?
No. Start with the visitor register alone; material, exit passes and attendance are modules you switch on when you want them — and stop paying for when you do not.
From the gate, in writing
How gates actually run — registers, contractors, evacuations and the paperwork in between.
Contractor Liability at the Gate: Who Carries the Risk?
The assumption is that the contracting firm carries the risk. Indian law is less generous than that, and the gate is whe...
Read
Visitor Management System Requirements: A Template
Most evaluations go wrong before the first demo, because nobody wrote down what the system has to do. Here is a requirem...
Read
What is a visitor management system? A complete guide
What a visitor management system does at each stage, what the better ones add, why Indian businesses are adopting them n...
ReadBuilt to be trusted
Tenant isolation
Your data is scoped to your company at the database layer, verified by automated tests on every release.
Immutable audit trail
Who Approved what, and when. A register entry is reversed with a reason, never edited or deleted, so the history stays honest.
Your data, always yours
One click downloads every record as CSVs — visitors, passes, couriers, material and the audit trail. No lock-in, ever.