Self-service visitor check-in: kiosks, use-and-throw tags and a faster, safer lobby

Why are lobbies moving to self-service check-in?

In a 2025 survey of 2,000 American travellers by Talker Research for Mews, which sells hotel check-in software and kiosks, 70% said they were likely to check into a hotel with an app or a self-service kiosk instead of a front desk. That is one country, one sector and an interested sponsor, so read it only as a sign of changing habits.

Offices feel two pressures of their own. The first is cost: in JLL’s Global State of Facilities Management Report 2025 (248 organisations in more than 20 countries), 84% of real estate and facilities leaders named budget constraints and rising operating costs as a top concern, and more than half of organisations were applying technology and AI to automate workflows. The report does not study reception desks; it shows the pressure behind the change. The second is that the front desk was never the control itself. High Table, an ISO 27001 consultancy, reads Annex A 7.2 this way: “The standard is not saying that you must have a reception”, and it notes that reception can be monitored remotely instead of staffed full time.

We found no survey that counts staffed and unstaffed office receptions in India, so we state the trend as our view: self-service is the future of the lobby, as lobbies worldwide move away from staffed reception desks.

Two self-service routes: the visitor’s phone or a self-service kiosk

Route 1: the visitor’s own phone. A QR poster at the door opens check-in in the phone’s browser, with nothing to download. The visitor reads a notice in their own language, consents item by item with nothing pre-ticked, and enters their name, mobile, company, host and purpose. The host approves in one tap in WhatsApp, Microsoft Teams or Slack, and the phone becomes the pass, showing gate, floor, host and valid until. This is how every Orb site starts, with no hardware.

Route 2: the self-service kiosk by Orb. An optional add-on at reception for sites that want one. Visitors check themselves in at the kiosk, and it gives out use-and-throw visitor tags. Orb supplies, fits and runs it. Add one where the lobby needs a visible place to start, some visitors would rather not use their own phone, or you want every visitor to wear a tag. For walk-in peaks and interview drives, the phone stays the main route, because forty phones are forty check-in points.

Phone check-in, self-service kiosk or staffed desk: a comparison

How does self-service keep an unmanned reception secure?

A self-service lobby is secure when four things happen before anyone reaches the gate.

1. Identity and approval come first. The host approves the named visitor before entry. If the host does not answer, a backup is asked, then the desk. For visitor types that need it, such as contractors, ID verification runs where the building’s policy calls for it.
2. No queue at one desk. A crowd at one reception is where people get waved through. On their own phones, visitors rarely form that queue.
3. No open register. TCSA, an Indian ISO 27001 consultancy, warns against open sign-in books because guests can read other visitors’ details, and recommends per-visitor records or digital check-in instead.
4. The guard checks the pass. The guard scans it, sees photo, name, host and approval, and matches the face. The code changes every minute, so a screenshot is useless.

How this maps to ISO 27001 Annex A 7.2 (“Physical entry”). Auditors look for controlled entry points, a record of who entered, when and who approved, and visitor identification that sets visitors apart from staff and expires (TCSA, High Table). Every Orb visit records the notice, consent, approval, and entry and exit times; our ISO 27001 guide lists what auditors sample.

How this maps to PCI DSS 9.3.2 to 9.3.4. For visitors to the cardholder data environment (CDE), PCI DSS v4.0.1 requirement 9.3.2 asks that visitors are “authorized before entering”, “escorted at all times”, given “a badge or other identification that expires”, and that badges visibly distinguish visitors from personnel. Self-service does not change the escort rule: inside the CDE, someone still walks with the visitor. Requirement 9.3.3 asks that badges or identification are “surrendered or deactivated before visitors leave the facility or at the date of expiration.” Requirement 9.3.4 asks for visitor logs, for the facility and for sensitive areas, with the visitor’s name and organisation, the date and time, and who authorised access, kept for at least three months unless law restricts it (v4.0.1 changed “a visitor log” to “visitor logs”). See our PCI DSS visitor log guide.

Use-and-throw visitor tags: how single-use visitor badges work

In our experience, many Indian lobbies still hand out numbered visitor cards on lanyards. By evening some are missing, and nobody can say which number went to whom.

Orb’s use-and-throw visitor tags are single-use.

• Never reused, never passed on. A tag belongs to one visit. It cannot be handed to a colleague or kept for a later visit.
• Nothing to collect at day end. No guard chasing cards at 7 pm.
• A fresh tag for each visitor. Nobody wears a tag another visitor has worn.
• Your brand on it. Printed with the company’s branding, the tag is a small thing visitors take home and remember you by.

How the tag works with the pass. The tag never opens the gate. The guard checks the pass and the face, and the pass is valid only until the time it shows, so a tag kept from last week gets nobody in. Inside, the tag lets staff see at a glance who is a visitor, which is part of what ISO 27001 auditors and PCI DSS 9.3.2 look for; both also expect visitor identification that expires.

Whatever tag you use, decide what it shows: what staff need to recognise a visitor, and nothing that would matter if the tag were dropped in the street, such as a mobile number. High Table suggests visitor badges that clearly display an expiry date or time, which also lets staff spot a tag from another day.

The PCI DSS 9.3.3 caveat. A tag the visitor takes home is not surrendered, and a printed tag cannot be deactivated. PCI DSS states the objective of 9.3.3 as visitor identification that “cannot be reused after expiration”; whether an expiring pass plus a kept tag meets the requirement is for your QSA to judge. For rooms in a CDE, agree it with your QSA, or issue a separate badge collected at that door.

Three snapshots from a self-service lobby

These are illustrative scenes, not customers.

8:55 am, tech park lobby in Pune, 40 visitors in ten minutes. A hiring drive brings forty graduates for a 9:30 test. HR has sent invites, so the candidates skip the typing and give consent fresh at the door. They scan the posters on the lobby pillars, while two who would rather not use their phones check in at the kiosk. Pooja Nair, the HR host, approves each candidate in one tap in WhatsApp. The guard, Suresh Patil, scans passes and matches faces; nobody waits at a desk.

A visitor who keeps the tag. Sneha Kulkarni, a procurement lead from a client, checks in at the Orb kiosk in a Bengaluru office and wears the branded tag through a two-hour review, then drops it in her bag. Nothing needs collecting. A week later it reminds her of the meeting, and it cannot get her back in, because entry needs a new approval and a new pass.

A Saturday with no receptionist. At a 60-person office in Navi Mumbai, the desk is closed and one guard is on the gate. An HVAC contractor arrives with his NDA and safety induction signed before the visit. He checks in on his phone, the facilities manager approves in WhatsApp from home, and the guard scans the pass. Sites with no guard at all can, on the Growth plan, make the host’s approval the entry, with a named colleague for anything unusual.

What still needs a person in a self-service lobby?

TCSA calls receptionists “the most consequential security control in the building”. Self-service splits that job.

• The desk route. Some visitors prefer a person, have no smartphone, need help, or decline to use their own phone. The desk or guard checks them in and reads the notice aloud, and nothing from their phone is saved.
• Children. Under the DPDP Act a child is anyone under 18. From 13 May 2027, when most of the Act’s duties apply, section 9(1) requires verifiable consent of a parent or lawful guardian before a child’s personal data is processed, and Rule 10 asks you to check that the person identifying as the parent is an adult, identifiable if another law requires it. So a child does not check in alone: the parent or guardian checks in and consents for the child, and Orb lists the child by name on that adult’s visit and never asks a child for ID. When the adult is not a parent or lawful guardian, such as a teacher with a school group, record the number of children on the adult’s visit and a child’s name only with a parent’s or guardian’s consent.
• The guard. The guard matches faces, sees a quiet watchlist flag where you use one, handles the unexpected, and runs the evacuation roll call from the live register.

What Orb sets up, and what Orb manages from there

Orb starts with nothing to install: six choices (site, staff list, visitor types, notice, retention, approvals), then a poster to print. The rest is optional. With managed services by Orb, Orb sets up and runs visitor management for you and manages it from there. Orb can also build your visitor physical access, taking care of everything from architecting turnstiles and access control to designing the lobby, and works with the turnstiles, card readers and face recognition gates you have. For portfolio companies with many locations and little traffic at each, a curated Orb plan manages all the sites together. See pricing, how Orb works and security.

Where Orb fits

Orb, our visitor management system, lets a lobby run on self-service without losing the guard’s check.

Questions buyers ask