> 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/pre-registration.md).

# The visitor pre-registration flow

A visitor pre-registers by opening the link in their invitation email and working through a browser-based flow: they accept the visitor agreement, verify their mobile with a one-time PIN, confirm or create their profile, complete any required steps, and receive an access pass with a QR code for fast check-in at the kiosk.

Pre-registration runs in a customer-branded portal. The steps a visitor sees depend on how the site is configured, so not every visitor sees every step below.

## Pre-register for a visit

{% stepper %}
{% step %}

### Open the invitation link

The visitor receives a branded email with an embedded pre-registration link. Opening it takes them into the browser-based flow for the site.
{% endstep %}

{% step %}

### Accept the agreement or NDA

The visitor reads and accepts the site's visitor agreement or NDA to continue. They tick **I have read, understood and accepted the agreement**, then **Continue**.
{% endstep %}

{% step %}

### Verify a mobile number

The visitor confirms their mobile number and verifies it with a one-time PIN (OTP) sent to that number by **SMS**, with **WhatsApp** as a fallback if the SMS doesn't arrive. A verified mobile is required to continue.
{% endstep %}

{% step %}

### Confirm or create a profile

If a profile already exists, the visitor confirms it is them. Otherwise they register a new profile: first name and last name, and (where the site captures them) a photo, company, and ID number.
{% endstep %}

{% step %}

### Book parking

Where booking is enabled, the visitor enters vehicle and parking details. Visitor booking in this flow is limited to parking. See [Book a resource](/command-centre/visitor-management-powered-by-kenai/resource-booking/book-a-resource.md).
{% endstep %}

{% step %}

### Complete the safety induction

Where induction is enabled, the visitor watches the induction video and answers the questionnaire. They can skip it and complete it on site instead. See [Kiosk induction](/command-centre/visitor-management-powered-by-kenai/inductions/kiosk-induction.md).
{% endstep %}

{% step %}

### Declare assets

Where asset declaration is enabled, the visitor pre-captures the assets they are bringing. See [Declare assets](/command-centre/visitor-management-powered-by-kenai/asset-management/declare-assets.md).
{% endstep %}

{% step %}

### Complete the check-in form

The visitor answers the site's check-in questions. Fields can be single-select, multi-select, text, or a range, and follow-up questions can be conditional on an earlier answer.
{% endstep %}

{% step %}

### Submit and receive the access pass

The visitor reviews the summary and submits. On completion they receive an access pass email containing a QR code for fast check-in at the kiosk.
{% endstep %}
{% endstepper %}

Pre-registration ends with the access pass. What happens when the visitor arrives, including returning-visitor and facial-recognition sign-in, is covered separately:

{% content-ref url="/pages/0Aq74SeJuZLdkygLYC7U" %}
[Check in at the kiosk](/command-centre/visitor-management-powered-by-kenai/visitor-management/kiosk-check-in.md)
{% endcontent-ref %}

## Update your check-in details before arrival

A visitor can change their details after pre-registering but before they arrive. The access-pass email carries an **Update your check-in** button. Pressing it opens a shortened version of pre-registration: accept the agreement, pass the identity check with a one-time PIN, then revisit the parking, induction, asset, and check-in steps. On submit, the visitor receives a fresh access pass and updated booking details by email.

{% embed url="<https://app.arcade.software/share/aT6NUXLQ7cI0eJs55O9l?embed=true>" %}
Walkthrough: updating check-in details from the access-pass email through the shortened pre-registration flow.
{% endembed %}

{% hint style="warning" %}
**Warning:** a pre-registration link is tied to one visitor. If a link is shared and someone else registers on it, the last person to register takes over the profile.
{% endhint %}


---

# 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/pre-registration.md?ask=<question>&goal=<endgoal>
```

`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.