QR and OTP Check-In: The Entrance Is Not a Usability Lab

The design is sound: a visitor scans a code at the entrance, checks in from their own phone, verifies a one-time code, and the host is notified. No shared kiosk, no queue at a tablet, no logbook on display, and the visitor's device does the work. The objections below are the ones that decide whether it survives contact with a real doorway — and each has an answer that is a design decision rather than a hope.

The objections, and the design answers

"Our lobby has no signal"

Common in basements, back entrances and thick-walled buildings, and fatal if unaddressed: a check-in flow that needs the visitor's mobile data does not work where there is none, and an OTP by SMS does not arrive. Guest Wi-Fi with a captive portal that permits the check-in domain before login is the usual answer, and it has to be tested at the actual door rather than assumed from a coverage map. Ask any vendor what their flow does with no connectivity at all — if the answer is that it cannot proceed, you need a fallback that a receptionist can run.

"A bus of forty people just arrived"

Individual self-service is the wrong shape for a group. Forty people each scanning, typing and waiting for a code is slower than a clipboard, and everyone can see that it is. Group check-in has to exist as a distinct path: one organiser registers the party in advance, the individuals are pre-loaded, and arrival is a confirmation rather than forty registrations. If a system has no group concept, its throughput claim only describes visitors arriving one at a time.

"The delivery driver will not do this"

Nor should they. A courier at a loading bay for ninety seconds is not a visitor in the sense the system means, and forcing them through an identity flow produces either an abandoned check-in or a fake one. The honest design decision is to classify entrants and route them differently — deliveries logged by the person receiving them, contractors through a heavier flow with permits and induction, guests through self-service. A single path for everyone is the design error, not the driver's reluctance.

"Some visitors cannot use a smartphone"

Some visitors will have a flat battery, an old handset, a work phone that blocks unknown domains, or no comfort with the interaction. Any system whose only path is self-service excludes them, and reception will invent a workaround — usually a notebook, which reintroduces everything digitising was meant to remove. An assisted path where a receptionist completes the same record on the visitor's behalf keeps the data in one place, which is the entire point.

Bilingual means before the first tap, not inside a menu

A visitor in Oman may read Arabic, English, or neither comfortably. The language choice has to be the first thing offered and it has to be obvious — a flag or a word, immediately, not a setting three screens in after the form has already been presented in the wrong language.

Getting this right is more than translating labels. Arabic requires the layout to mirror properly, not merely the text to change: field order, progress indicators, back buttons and the numeric keypad for the OTP all have a direction. And names are where sloppy implementations show themselves — a visitor whose name is written in Arabic script needs a field that accepts it and a badge that prints it, not a form that silently strips it to question marks. A system that treats Arabic as a translation layer over an English product announces itself within two screens.

What the OTP is actually for

It is worth being precise, because this is frequently oversold. A one-time code to a phone does not verify identity. It verifies that the person at the door controls that phone number. Anyone can type a false name and receive a real code on their own handset.

That is still worth having, and for a clear reason: it converts an unverifiable claim into a reachable contact. A visitor record with a confirmed number can be used to send a check-out prompt, to reach someone during an incident, or to establish contact history afterwards — none of which a handwritten name achieves. Where genuine identity assurance is required, that is a document check at a manned desk, and it belongs to the contractor flow rather than the guest one. Claiming the OTP does more than it does is how a security posture ends up resting on a misunderstanding.