> For the complete documentation index, see [llms.txt](https://docs.eventnook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventnook.com/useful-guides-and-tools/gists/send-tailored-confirmation-emails-for-each-ticket-type.md).
# Send Tailored Confirmation Emails for Each Ticket Type
### How to Set Different Confirmation Emails for Different Ticket Types
Sending the right message to the right audience is key to creating a smooth event experience. With EventNook, you can customise confirmation emails based on ticket type—so each attendee receives relevant information, instructions, and content tailored to their role.
This is especially useful for events with multiple audience segments (e.g. **VIP**, **Media**, **Delegate**, **Virtual Attendees**), helping you:
* Deliver personalised communication
* Avoid confusion with irrelevant details
* Improve attendee experience and preparedness
***
#### Step 1: Add Custom Content
* Go to **Confirmation Email (Approved Order)**.
* Click on **Add Content**.
***
#### Step 2: Create Your Message
* Type the message you want to communicate.
* Customise the content based on the audience (e.g. VIP perks, media instructions, delegate agenda details).
***
#### Step 3: Apply to Specific Ticket Types
* Click on the **settings icon** within the content block.
* Select **Apply to selective tickets**.
* Choose the ticket type(s) (e.g. VIP, Media, Delegate).
* Click **OK** to confirm.
***
#### Step 4: Customise QR Code Visibility (Optional)
* You can also control whether a **QR Code** is included for each ticket type.
* This is useful if certain attendees do not require on-site check-in.
**Example:**
* Physical attendees → Include QR Code for check-in
* Virtual attendees → Hide QR Code
***
### Use Case Examples
#### 1. Hybrid Events (Physical + Virtual)
* **Physical Ticket Holders**
* Include QR Code
* Provide venue details and check-in instructions
* **Virtual Ticket Holders**
* Exclude QR Code
* Provide webinar links and access instructions
***
#### 2. International Events (Multi-language Emails)
* Create ticket types based on **country or language**
* Example: *English*, *Japanese*, *French*
* Customise each email in the respective language
* Apply to the corresponding ticket type
This ensures attendees receive communication in their **preferred language**.
***
#### 3. VIP vs General Admission
* **VIP**
* Exclusive access details, priority entry, special instructions
* **General Admission**
* Standard event details and check-in information
***
By using **custom content blocks** and assigning them to specific ticket types, you can create a more personalised, relevant, and professional confirmation email experience for every attendee.
---
# 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://docs.eventnook.com/useful-guides-and-tools/gists/send-tailored-confirmation-emails-for-each-ticket-type.md?ask=&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.
