> 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/online-registration-send/send-email-blast.md).

# Send Email Blast

## Sending Email Blasts To Your Registered Attendees

EventNook offers two options for sending **Email Blasts.**

Here’s how the two options work:

### Email To Orders vs Attendees

1. **Email to Orders -** [Email To Orders](/online-registration-send/send-email-blast/email-to-orders.md)
   * This option sends the email to the main registrant or buyer only. When your event allows Group Registration in a single order, this option lets you send emails to the primary contact (main registrant).
   * Useful for contacting the **primary contact** for the order (e.g., the person who purchased multiple tickets in a group registration).
   * Only the key contact will receive the email.
2. **Email to Attendees -** [Email To Attendees](/online-registration-send/send-email-blast/email-to-attendees.md)
   * Sends emails to **each ticket holder** listed under the registration.
   * Allows you to send targeted emails based on ticket types. For example, if you want to email only specific attendees, such as VIP ticket holders, this option makes it possible.
   * Great for personalizing communication to all attendees, even in group orders.

#### When to Use Each Option:

* **Email to Orders**: Ideal for general updates that only need to reach the primary buyer.
* **Email to Attendees**: Best when you want to reach every attendee directly or send specific information to different ticket categories.

These flexible options make it easy to manage communication effectively, whether you're targeting the buyer or individual attendees.


---

# 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/online-registration-send/send-email-blast.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.