# Invites

***

### What are invites?

Invites are links and codes that can be shared to invite guests to access their reservation. A invite generates a unique code that can be used to access the reservation and can be shared among other guests. 

A invite can have personal data such as: `firstName` `lastName` `email` or `phone`. However, they are not tight to a certain person. It will be used to keep track of conversion and who has been invited and who hasn't. 

### How are Invites distributed?

Invites are distributed automatically depending on the [Touchpoint](/getting-started/glossary.md#touchpoints) settings or by guests themselves.

* **Touchpoints -** A special `invitation` touchpoint is always available within your workspace. Check the settings of your touchpoints [here](https://admin.holidayhero.com/touchpoints).
* **Guests-** An existing guest has the opportunity to create an invite for another guest. From within the `My Party` section of the App, any guest can create an invite for other guests. If the browser supports a native share function, we will use and trigger that. 

**My Party - section**

<figure><img src="/files/LlyfyQ0PdVXnQJlL69QQ" alt=""><figcaption><p>An example my party section. Colors may differ based on your branding settings. The MyParty section is disabled in the Public Views. </p></figcaption></figure>

**Share display options can be:**&#x20;

<details>

<summary>Native Share</summary>

This is available on the majority of the platforms. Full browser compatiablity can be found here. (<https://developer.mozilla.org/en-US/docs/Web/API/Navigator/share#browser_compatibility>).&#x20;

**Example on Safari - Dekstop**

![](/files/kUsIXrRvUeHEmEIN9azm)

</details>

<details>

<summary>Browser Share</summary>

If the browser doesn't allow a native share functionality. We will throw the fallback modal from which the user can share the invite automatically.&#x20;

Example.&#x20;

![](/files/CnOP7lvAigDWpC2sNNin)

</details>

### Invite Statusses

Invites can have various statusses. See a list of statusses and their descriptions below:&#x20;

| Status                                                             | Description                                |
| ------------------------------------------------------------------ | ------------------------------------------ |
| <mark style="color:yellow;background-color:yellow;">Pending</mark> | The invite hasn't been used yet.           |
| <mark style="color:green;background-color:green;">Accepted</mark>  | The invite has been used at least one time |
| <mark style="color:red;background-color:red;">Cancelled</mark>     | The invite has been cancelled or removed   |

It can occur that a reservation has only pending invites and users. This happens, when the user has manually searched for their reservation based on a confirmation code, stay date or last name.&#x20;

***

### Frequently Asked Questions:

<details>

<summary>Are invites automatically generated by the integrations? </summary>

Yes, if the guest details are known, the invites are automatically generated by most of the integrations. One major exception is the [iCal](/integrations/pms-platforms/ical.md) integration. This integration, just creates the reservation and sends you an email to remind you to copy over the guest details.&#x20;

</details>

<details>

<summary>Are invites automatically removed? </summary>

No, at the moment we keep all the invites. You have the option to manually remove an invite.&#x20;

</details>

<details>

<summary>Can invites be localized? </summary>

Yes, within the translations section of the Admin, you can add translations for your invitation touchpoint.&#x20;

</details>


---

# Agent Instructions: 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:

```
GET https://support.holidayhero.com/the-basics/reservations/invites.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.