> 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/receptionist-functions/performing-visitor-actions/sending-invitations.md).

# Sending Invitations

### Introduction

Sending an invitation is an action that a Host would perform during the creation of a new Visit, or selecting an existing visit.

### Prerequisites

Sending invitations to visitors requires the following:

* the Visitor to be the correct Visitor Type and have a configured Email Personal Data Field with a valid Email in it. If not, an email will still be created but the **To** field will be blank.
* the Email Personal Data Field has the **Default Notification** checkbox ticked (on the **Type** tab).
* a card type has been created with barcodes.

### Procedure

1. Select the visitor record on either the Find Visit, Visit or Home screens.
2. Click the **Invite** action button.

   **Note:** The reception configuration determines if the Invite action is displayed, or not.

   The Visitor receives the email with an attached **.png** file containing the QR Code barcode, and the Host is cc'd on the email if email is configured.

   When the visitor arrives for their visit:

   1. They scan the Barcode directly from their cell phone or printed on a piece of paper.

      This either marks them as ‘signed In’ or ‘on site’, depending on configuration.
   2. A Badge is printed that contains the Barcode (this is a manual action).
   3. When they leave, they swipe the Barcode on their Badge and they are marked ‘off site’.


---

# 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/receptionist-functions/performing-visitor-actions/sending-invitations.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.
