> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/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/knowledge-hub/configuration-client/licensable-features/visitor-management/using-visitor-management/pre-registration-and-receptionist-functions/the-visit-screen/creating-a-visit/creating-a-visitor.md).

# Creating a visitor

Creating a visitor

#### Introduction

You will need to create a new visitor record when someone who has not visited before (not in the system) arrives at your site.

When a visitor is created personal details are recorded about the visitor. Personal details are items such as: visitor name, visitor company, contact details, notes, photograph, etc.

The visitor type determines what visitor details can be recorded for the visitor and what details are mandatory (\*must be recorded in order to save the visitor). Hence, the fields shown on the Create Visitor screen can vary depending on the visitor type.

**Note**: Your Command Centre administrator will configure what personal details can be recorded for each visitor type.

#### Procedure

Perform the following procedure to create a visitor:

1. Click the **Create** button located on the Visit screen.

   The Create Visitor window opens.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1c90720ab12a77b576bad9acbe01232cd33d31d9%2Fvm_createvisitorscreen.png?alt=media)

   **Note:** Fields marked with an asterisk (\*) are mandatory in order to save the visitor. Fields marked with two asterisks (\*\*) are mandatory before marking a visitor on-site.
2. Enter the **First Name** of the visitor into the First Name field. This field is limited to 50 characters.
3. Enter the **Last Name** of the visitor into the Last Name field. This field is limited to 50 characters.
4. Optionally, enter the visitors **Contact Details** into any Contact Details fields that appear, (e.g. Phone, Mobile, Email or Address).
5. Optionally, enter a **Note** for this visitor into the Notes field.

   This field is limited to 2500 characters.
6. Optionally, click **Capture** to capture an image to store against the visitor, (e.g. a photo of the visitor).

   See [Capturing images to store against a visitor](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/using-visitor-management/pre-registration-and-receptionist-functions/the-find-visit-screen/capturing-images-to-store-against-a-visitor.md) for a detailed procedure.

   **Note:** A capture device must be connected and configured.
7. Optionally, visitor details can be captured by scanning their business card, passport or driver's license.

   See the appropriate topic for a detailed procedure. Either:

   * [Scanning business cards for visitors](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/using-visitor-management/pre-registration-and-receptionist-functions/the-find-visit-screen/scanning-business-cards-for-visitors.md), OR
   * [Scanning passports or driver licenses for visitors](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/using-visitor-management/pre-registration-and-receptionist-functions/the-find-visit-screen/scanning-passports-or-driver-licenses-for-visitors.md)

   **Note:** The appropriate capture device for the form of ID being scanned must be connected and configured.
8. Complete any additional fields as required by the visitor type.
9. Click **OK** to save the visitor. The visitor is stored in the system and added to the current visit.

   **Note**: If configured an Escort field may be displayed. The Escort field is read-only and is updated when an escort has been assigned to the visitor.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/visitor-management/using-visitor-management/pre-registration-and-receptionist-functions/the-visit-screen/creating-a-visit/creating-a-visitor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
