> 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/command-centre-site-configuration/adding-contacts-to-quot-host-quot-cardholders.md).

# Adding Contacts to "Host" Cardholders

### Introduction

A "Host" is the person responsible for visitors for the duration of their visit, and must be a non-visitor cardholder. Potentially, the "Host" can be either the "Meeting with" person or the "Escort".

Contact details for cardholders who are “Hosts” in the Visitor Management application are required so that they can be easily contacted by Reception if a visitor arrives to see them.

There are four Contact type Personal Data Fields (PDFs) that can be configured for holding cardholder contact details. Contact details for individual cardholders are then entered against these PDFs on the **Personal Data** tab of the Cardholder properties. They are then available from the **Host** screen in the Visitor Management application as "read-only", (i.e. they cannot be altered in the Visitor Management application).

<table><thead><tr><th width="216">Refer to...</th><th>for the procedure on...</th></tr></thead><tbody><tr><td><a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/personal-data-fields/creating-a-new-personal-data-field.md">Creating a new Personal Data Field</a></td><td>creating Contact type PDFs.</td></tr><tr><td><a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/editing-a-cardholders-pdf-data.md">Editing a Cardholders PDF data</a></td><td>adding contact details for individual cardholders.</td></tr></tbody></table>


---

# 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/command-centre-site-configuration/adding-contacts-to-quot-host-quot-cardholders.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.
