> For the complete documentation index, see [llms.txt](https://docs.podplay.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podplay.app/events/create-an-event/waitlists-and-customer-messaging/what-is-the-process-for-notifying-customers-on-the-waitlist.md).

# What is the process for notifying Customers on the Waitlist?

* When an Event has filled up, Customers who are still interested in the Event can sign up for the Waitlist. When a customer who already signed up for the Event decides to cancel, everyone on the Waitlist for that Event will be notified by email that there is an open slot for the Event.
* Everyone on the Waitlist is notified at the same time so that there is no preferential treatment.
* Here is an example of what the customer will see when a spot opens up in the Event, and what the Admin will see on the All Areas Overview if a Customer has signed up for an Event Waitlist.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.podplay.app/events/create-an-event/waitlists-and-customer-messaging/what-is-the-process-for-notifying-customers-on-the-waitlist.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.