> 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/force-push-an-email-to-customers-on-a-waitlist.md).

# Force Push an Email to Customers on a Waitlist

* If an Admin noticed there are Customers on a Waitlist and there are spots open on the Event, an Admin can Force Push an Email to Customers on the Waitlist.
* To do so:
  * Click into the desired Event
  * Add one extra spot to the Event
    * This will create an automated email to all Customers on the Waitlist saying the Event has a new spot open
  * Click the blue Save button at the bottom right of the side panel
  * Open the Event up again
  * Delete the one extra spot from the Event
* The Customers on the Waitlist will see this email in their inbox.


---

# 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/force-push-an-email-to-customers-on-a-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.
