Headquarters
7150 Columbia Gateway Drive, Suite L, Columbia, MD 21046
New York Location
112 West 34th Street, 18th Floor, Room 18025, New York, NY 10001
Proud Member
Touchless visitor check-in in an office building covers several different workflows, from advance registration and QR credentials to mobile badges and host-assisted arrival. A useful way to judge them is whether the workflow removes a step from the arrival or only removes a touch. A credential issued before the visit can cut repeat data entry at the kiosk. A screen a visitor waves at instead of tapping is the same arrival with a different gesture. This is a way to decide which options earn their place in a particular building, including what happens when someone arrives without a registration or a working phone.
The term covers several different things, so a building needs to define the workflow before judging the result.
In a current office lobby it usually means some combination of these:
Those sit at very different levels of commitment and have very different consequences. Treating them as one purchase can hide the dependencies of each workflow. Confirm the capabilities and integrations included in the proposed deployment. What a visitor management system does in an office building covers how these pieces fit the wider system, and the Navigo visitor management solution page sets out what the platform itself supports.
This is the test, and it sorts the list quickly.
Workflow | What it actually does | Verdict |
|---|---|---|
Pre-registration with a QR code | Puts the visitor in the system before arrival, cutting repeat data entry | Moves work earlier |
Pre-screening sent ahead on a schedule | Moves the NDA or disclosure to a desk the day before | Moves work earlier |
QR credential at a turnstile | Replaces a printed credential where readers and access-control integration support it | May remove a step, depending on the existing workflow |
Digital badge on a phone | Changes what the visitor carries, not what they do | Removes a touch |
Wave or gesture interface at the kiosk | Same stop, same identification, same wait, different gesture | Removes a touch |
Video greeting and direct connection to the host | Replaces the receptionist in a lobby that has none | Depends on reliable remote assistance |
Face recognition | Offered for faster processing, raises biometric obligations | Legal question before operational |
Pre-registration is the clearest case of moving work earlier. The visitor is in the system before they arrive, which can cut repeat data entry and some of the desk work where the host, the visitor and the building's workflow are all set up for it. An identity check, a host approval, a safety acknowledgement or a queue can still stand between arrival and access. Pre-screening sent as a token link on a schedule does the same thing to the paperwork: the NDA or the disclosure is signed at a desk the day before rather than by someone standing in a lobby with a bag in one hand. A QR code can replace a printed credential and carry a visitor through a turnstile where compatible readers, access-control integration and an authorized visitor workflow are in place. Some buildings still require a badge, a security check or host approval on top of it.
A touchless interface on its own does not. If a visitor still has to stop, identify themselves and wait for approval, the arrival has the same number of steps it had before. That is not an argument against it, and in a shared lobby there are good reasons to reduce contact with a surface hundreds of people touch. It is an argument against expecting it to speed anything up.
Worth being precise about the middle category, because it is where most of the value sits and where most of the overclaiming happens. Pre-registration and pre-screening rarely delete work outright. They move it to a calmer moment, which is a real gain and a different one from elimination. A QR credential is the case that genuinely can collapse two steps into one, but only against the right starting point: if it replaces a printed badge the visitor still has to collect and present, it has changed the medium rather than the number of steps.
Three questions sort any touchless feature before it goes on a quote:
The ones that pull work backward in time, to before the visitor arrives, are the ones that change how the lobby feels at 8:45 on a Monday.
A workflow that depends on somebody completing an advance task needs a usable path for the day that task is missed.
Pre-registration is the clearest case. It works beautifully when the host remembers to register the guest, and when they forget, the visitor needs an unregistered arrival path. That is a workflow dependency to plan for. That is why a system that supports both registered and non-registered visitor sign-in matters more than it sounds: the unregistered path needs to work for guests who arrive without advance registration.
The same logic applies to a QR code the visitor cannot find in their email, and to a screening link sent to an address somebody no longer checks. These can be workflow dependencies, and the useful question before buying is what happens on the day the dependency is not met.
We did not identify a reliable, office-specific comparison of which touchless features tenants kept and which they dropped in the sources reviewed, and ITS has not published adoption figures. What a building can do is look at its own numbers: the share of arrivals that were pre-registered last month tells you whether the habit took, and is a useful starting point. Pair it with arrival time, completion rates and unanswered host requests to see whether the workflow is helping.
The arrival has to work without a person behind the desk, which raises the value of anything handled in advance. It does not make touchless the only option: an unstaffed reception can also run a conventional touchscreen or an assisted remote flow, and a kiosk that scans an ID or takes typed credentials still involves physical interaction.
In an unstaffed lobby, Navigo documents an arrival that can run end to end: a video greeting as someone walks up, a searchable tenant directory, a DirectDial™ audio or video connection so the visitor speaks to the person they came to see, self check-in by scanning an ID or entering credentials, and an automated door unlock once the tenant approves them. Which of those are present in a given building depends on the hardware, the integrations, permissions and how it is configured, so treat the sequence as what the product supports rather than what every installation ships with. The approval is still a human decision. It is made by the tenant upstairs rather than a receptionist downstairs.
This is where advance work and a reliable remote-assistance path can matter most. If the tenant does not answer, the visitor is standing in a lobby with nobody to ask. Worth confirming before go-live: what the system does when an approval request goes unanswered, and who it escalates to.
Both, depending on which parts a building picks, and this is the question most touchless marketing skips.
The gains are real. Navigo offers a language translation toggle supporting more than 90 languages, which, where a building enables it, serves visitors a printed sign never did, although translation availability is not the same thing as meeting an accessibility standard. A phone-based flow can let someone use their own device, with their own text size and their own screen reader, rather than a fixed kiosk at a fixed height, which helps some visitors and does not by itself make the arrival accessible.
The losses are real too. A QR-only arrival assumes a compatible device, a credential the visitor actually received and can locate, a screen readable enough to scan from, and enough battery to show it. A code can be saved or screenshotted, so a live data connection is not always the obstacle; access to the credential usually is. A visitor without those is excluded by design unless an alternative path exists. And the kiosk itself still has to meet the physical requirements that apply to anything mounted in a lobby: reach range, operable parts and protrusion, which ADA and Section 508 considerations for self-service displays covers in more detail.
Face recognition deserves its own note here. It is offered for faster visitor processing, and it can raise biometric privacy and consent requirements that photo capture alone does not, depending on the jurisdiction and on what is collected and how it is processed. What a visitor badge system prints, stores and deletes covers those obligations in detail. That is a decision for the building's counsel before it is a decision for the lobby.
A short version a property manager can act on.
Keep pre-registration and pre-screening, because they move work to before the arrival. Keep the QR credential where the readers and the access-control integration support it, because it can collapse two steps into one. Keep an unstaffed-lobby arrangement where remote assistance, approvals and an escalation path reliably cover the hours without reception.
Be honest about the rest. A touchless gesture on an otherwise unchanged check-in is a contact reduction, not a speed improvement, and should be justified on those terms. Face recognition needs a legal answer before an operational one. And any feature that depends on a host remembering something needs a working path for the day they do not.
The six moments a property manager owns places arrival in the longer sequence it belongs to.
Tell us whether your lobby is staffed all day, whether there is a barrier between the lobby and the elevators, and roughly what share of your visitors are expected in advance. That last number decides more than any feature list. What comes out of that conversation is concrete: which arrival steps are doing no work, what your access-control platform has to support before a credential can carry anyone through a turnstile, and what the building does on the morning a visitor turns up with no registration and a dead phone.
It covers arrivals handled without shared-surface contact, usually some mix of pre-registration with an emailed QR code, pre-screening completed before arrival, a digital badge on a phone, a video connection to the host, and in some buildings face recognition. The mix depends on the hardware, integrations and workflow configured for the building.
It can where it removes a step. Pre-registration and pre-screening move work before the visitor reaches the building, though an identity check, host approval or queue may still remain. A touchless gesture on an otherwise unchanged check-in reduces contact with a surface without reducing the number of steps, which is a reasonable goal stated accurately.
Yes. Navigo documents a video greeting on approach, a searchable tenant directory, a DirectDial audio or video connection to the host, self check-in by ID scan, and an automated door unlock once the tenant approves, subject to hardware, integrations and configuration. An ID-scanning kiosk still involves physical interaction. Confirm what happens when an approval goes unanswered.
No. It assumes a compatible device, a credential the visitor received and can locate, a readable screen and enough battery. A code can be saved offline, so the connection is not usually the barrier; getting and reading the credential is. Keep an alternative path, and the kiosk still has to meet reach range, operable parts and protrusion requirements.
It can. Several states regulate biometric identifiers specifically, and data derived from face geometry is treated differently from a stored photograph under those laws. Whether a deployment is covered depends on the jurisdiction and on what is collected and how, so get an answer from counsel before enabling it, not after.
Toll-Free
Phone
© Copyright 2025 ITS, Inc. All rights reserved.
Stay in touch with the latest news and updates from ITS, Inc.
7150 Columbia Gateway Drive, Suite L
Columbia, MD 21046
112 West 34th Street, 18th Floor, Room 18025
New York, NY 10001