> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/visitor-management/kiosk-check-in.md). # Check in at the kiosk On arrival, a visitor checks in at the onsite kiosk under the site's branding (for example **Clever Industries HQ.**), where the home screen offers **SIGN IN**, **SIGN OUT**, **1. Scan for touchless registration**, and **2. Show QR Code to sign in / out**. Several check-in paths are supported and a site can combine them; this page covers each one and the on-arrival flow. ## Choose a check-in path The path a visitor takes depends on whether they pre-registered and what the site has enabled. * **Instant QR check-in**: a pre-registered visitor scans the QR code from their access pass and is checked in within seconds. * **Facial recognition**: the kiosk camera identifies a returning or pre-identified visitor with no typing. * **Returning visitor sign-in**: a visitor whose profile was remembered taps **SIGN IN**, confirms their host and answers, and shows their QR code. * **Walk-in self-registration**: a visitor who has not been pre-registered completes the full flow on the kiosk, including profile capture, agreement signing, and OTP verification. {% hint style="info" %} **Note:** for low-security visitor types, a site can enable a streamlined light check-in where the one-time PIN (OTP) is not required. {% endhint %} ## Instant QR check-in A pre-registered visitor presents their QR code at the kiosk's **2. Show QR Code to sign in / out** camera. Kenai looks up the reference, fetches their pre-registration data, and adds them to the dashboard. The visitor sees **WELCOME, JOE**, **LET'S GET YOU ACCESS**, and their verified guest pass, then taps **COMPLETE** to finish. {% embed url="" %} Walkthrough: QR-code sign-in pulling pre-registration data through to the dashboard. {% endembed %} ## Facial recognition When a returning visitor has chosen to be remembered, the kiosk camera recognises them and shows **SIGN IN - PLEASE CONFIRM YOUR IDENTITY** with their name and photo. The visitor taps **CONFIRM**, then confirms or changes their host, reviews their check-in answers (pre-filled from their last visit), reviews and updates any assets they declared before, and completes check-in. {% embed url="" %} Walkthrough: the kiosk recognises a returning visitor, who confirms their identity, host, pre-filled answers, and declared assets. {% endembed %} ## Returning visitor sign-in A visitor who chose to be remembered on a previous visit signs themselves in from the kiosk home screen. {% stepper %} {% step %} ### Tap SIGN IN On the kiosk home screen, tap **SIGN IN**. {% endstep %} {% step %} ### Choose a host On the **HOST** screen, type at least three letters of the host's name into the **Search here…** field and pick the match. If the host isn't found, **Not on list - Please ask reception to notify your host** is offered. Tap **PROCEED**. {% endstep %} {% step %} ### Show the QR code Back at the kiosk home screen, show the visitor's QR code to the **2. Show QR Code to sign in / out** camera to complete sign-in. {% endstep %} {% endstepper %} {% embed url="" %} Walkthrough: a remembered returning visitor signs in at the kiosk and chooses a host. {% endembed %} ## Walk-in self-registration A visitor who has not been pre-registered completes the whole check-in on the kiosk. {% stepper %} {% step %} ### Verify your mobile number On the **MOBILE NUMBER** screen, enter your number to receive a one-time PIN (OTP), then tap **Send OTP**. The OTP is sent over WhatsApp; to receive it by SMS instead, use **Send OTP via SMS**. {% endstep %} {% step %} ### Enter the OTP On the **ONE TIME PIN** screen, enter the OTP sent to your mobile. If it doesn't arrive, you can **SKIP and verify next visit** or go **BACK** and try again. {% endstep %} {% step %} ### Create your profile On the **REGISTER** form, complete **FIRST NAME**, **LAST NAME**, **MOBILE NUMBER**, **EMAIL**, **COMPANY**, and **ID / PASSPORT NUMBER**, then tap **CREATE**. {% endstep %} {% step %} ### Answer the check-in questions On the **CHECK IN** screen, answer the site's questions, then tap **CHECK IN**. See the on-arrival fields below for how these behave. {% endstep %} {% endstepper %} ## On-arrival check-in fields After identity is established, the kiosk shows the **CHECK IN** questions. These fields are uniquely customised for each client site, so the exact questions vary, but they share a few behaviours: * **Prepopulated responses**: questions such as **What is the purpose of your visit today?** offer a dropdown of preset options (for example *Maintenance*, *Contractor Work*, *Training*, *Inspection*, *Other*). * **Conditional fields**: selecting a specific option can reveal another field. Choosing **Other** reveals a free-text **Please specify your reason for visiting** field; answering **Yes** to **Are you checking in for a group?** reveals a **How many people are you checking in for?** slider. * **Remembered answers**: a site can configure individual answers to be remembered or discarded. On a return visit, remembered answers are pre-filled with a reminder to confirm they are still accurate. When every question is answered, tap **CHECK IN**. The visitor reaches the **WELCOME** screen with their verified **VALUED GUEST** pass, a **Remember me to speed up my next check in** toggle, and a **COMPLETE** button. {% hint style="info" %} **Note:** leaving **Remember me to speed up my next check in** on lets the visitor skip re-verification next time. {% endhint %} ## Declare assets at check-in Where asset declaration is enabled, the kiosk shows an **ASSET DECLARATION** step during check-in. The visitor adds anything they are bringing on site, or ticks **I have no assets to declare**, then taps the declare button (for example **DECLARE 1 ASSET**). {% embed url="" %} Walkthrough: declaring an asset during kiosk check-in. {% endembed %} {% content-ref url="/pages/zWUeLY1PIhZMfV7h0Ref" %} [Declare assets (visitor)](/command-centre/visitor-management-powered-by-kenai/asset-management/declare-assets.md) {% endcontent-ref %} ## Complete the safety induction Where induction is required, the visitor completes the safety induction at the kiosk as part of arrival. The induction has its own identity confirmation, video, and questionnaire. {% content-ref url="/pages/ahCzOwh0mjA8TePsFsAW" %} [Kiosk induction](/command-centre/visitor-management-powered-by-kenai/inductions/kiosk-induction.md) {% endcontent-ref %} ## If a visitor can't use the kiosk When a kiosk path can't be used, reception can check the visitor in from the dashboard instead. {% content-ref url="/pages/lHNzJCjajrQfVGqEE3YJ" %} [Assisted check-in](/command-centre/visitor-management-powered-by-kenai/visitor-management/assisted-check-in.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/visitor-management/kiosk-check-in.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.