> For the complete documentation index, see [llms.txt](https://support.holidayhero.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.holidayhero.com/the-basics/calendar-events.md).

# Calendar Events

#### What are calendar events? <a href="#what-are-calendar-events" id="what-are-calendar-events"></a>

**Calendar Events** let you tell your guests about things that are happening — a local festival, a weekly market, a guided tour, a seasonal opening, or a one-off activity. Each event has a title, a date and time, a description, photos and contact details, and is shown to guests in the calendar of the guest app.

An event can stand on its own, or it can be connected to an [experience](file:///the-basics/experiences.md) or a supplier. You decide which listings see the event — all of them, or a hand-picked selection.

#### Creating a calendar event <a href="#creating-a-calendar-event" id="creating-a-calendar-event"></a>

1. Go to **Calendar Events**
2. Click **Create**
3. Fill in the essentials:
   * **Title** — the name guests see in the calendar
   * **Nickname** — an internal name only visible in the admin, handy when you have many similar events
   * **Category** — pick the category that best describes the event
   * **Starts At** / **Ends At** — when the event begins and ends
4. Save

Once created you land on the event's detail page, where you can add everything else — a description, photos, contact details, an action button, and a connection to an experience or supplier.

{% hint style="info" %}
If you leave **Ends At** blank, the midnight of the start date is used
{% endhint %}

#### Timing and recurring events <a href="#timing-and-recurring-events" id="timing-and-recurring-events"></a>

Set when the event happens under the **Timing** section.

For something that happens more than once, turn on **Recurring event?** and choose the pattern:

1. **Every** — repeat every X **day(s)**, **week(s)**, **month(s)** or **year(s)**
2. **Days** — for weekly events, tick the days of the week it runs on (e.g. Monday and Wednesday)
3. **On** — for monthly events, repeat on the same day of the month (**Start Day**) or on a relative day such as "the 2nd Tuesday of the month"
4. **Ends** — the recurrence runs **Never** (forever) or **On** a specific end date

{% hint style="info" %}
Times are always shown in the event's local timezone. We work this out from the event's address first, then from the connected experience's address, and otherwise fall back to your workspace timezone. This means an event in another country shows the correct local time, no matter where you are.&#x20;
{% endhint %}

#### Description, photos and contact details <a href="#description-photos-and-contact-details" id="description-photos-and-contact-details"></a>

* **Summary** — a short summary shown to guests. This is generated by AI and can be edited.
* **Content** — the full description, written in the rich text editor.
* **Contact Details** — a **Website**, **Email**, **Phone** number and **Address** for the event. The address is also used to work out the event's timezone and to power directions and taxi ordering in the guest app.
* **Photos** — upload up to 100 photos. Drag to reorder them; the first photo is used as the thumbnail.

#### Connecting an experience or supplier <a href="#connecting-an-experience-or-supplier" id="connecting-an-experience-or-supplier"></a>

Under **Experience / Supplier** you can tie the event to something already in your account:

* Connect an **Experience** when the event is run as part of one of your experiences.
* Connect a **Supplier** when an external partner organises it.

{% hint style="info" %}
An event can be connected to **either** an experience **or** a supplier — not both at the same time.&#x20;
{% endhint %}

When an event is connected to an experience, guests will see the event wherever that experience is available — even if you haven't added the event to those listings directly.

#### The guest action button <a href="#the-guest-action-button" id="the-guest-action-button"></a>

The **Action** section controls the button guests see on the event:

* **None** — no button.
* **Form** — guests open a form. Set the **Button Text**.
* **Routing** — guests are sent to a web address. Set the **URL** and the **Button Text**.
* **Experiences** — guests are pointed towards your experiences.

#### Choosing which listings see the event <a href="#choosing-which-listings-see-the-event" id="choosing-which-listings-see-the-event"></a>

Open the **Listings** tab on an event to decide where it shows up:

* **All listings** — the event is shown at every listing.
* **Selected listings** — turn off "All listings" and tick the specific listings that should display it.

{% hint style="info" %}
&#x20;If the event is connected to an experience, any listing where that experience is added will always show the event through the experience — regardless of the listings you pick here.&#x20;
{% endhint %}

#### Documents <a href="#documents" id="documents"></a>

The **Documents** tab lets you attach files to the event — for example a programme, a map, or terms and conditions. Upload, reorder and remove documents here; guests can download them from the event in the app.

#### Managing events from an experience or supplier <a href="#managing-events-from-an-experience-or-supplier" id="managing-events-from-an-experience-or-supplier"></a>

You can also reach an experience's or supplier's events from their own pages:

* On an **experience**, the **Calendar Events** tab lists the connected events, and you can detach an event from there. See [Experience Calendar Events](file:///the-basics/experiences/calendar-events.md).
* On a **supplier**, the **Calendar Events** tab does the same for supplier-organised events.

***

#### Frequently Asked Questions <a href="#frequently-asked-questions" id="frequently-asked-questions"></a>

<details>

<summary>What's the difference between the Title and the Nickname?</summary>

The **Title** is what guests see in the calendar. The **Nickname** is an internal name only visible in the admin — useful for telling apart events that share a similar public title.

</details>

<details>

<summary>Why does my event show a different time than I entered?</summary>

Event times are shown in the event's local timezone, which we derive from the event's address (or the connected experience's address). If you haven't set an address yet, we fall back to your workspace timezone. Add or correct the address to make sure the time is shown correctly.

</details>

<details>

<summary>Can one event appear at more than one listing?</summary>

Yes. Use the **Listings** tab to display the event at **all** listings or at a **selected** set. If the event is connected to an experience, it also appears automatically at every listing that offers that experience.

</details>

<details>

<summary>Can I connect an event to both an experience and a supplier?</summary>

No — an event can be connected to either an experience or a supplier, but not both at once. They can be connected to an supplier, through the experience

</details>

***

## Agent Instructions: Querying This Documentation <a href="#agent-instructions-querying-this-documentation" id="agent-instructions-querying-this-documentation"></a>

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/calendar-events.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.


---

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

```
GET https://support.holidayhero.com/the-basics/calendar-events.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.