> 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/manage-attendees/how-does-a-customer-sign-up-for-an-event.md).

# How does a Customer sign up for an Event

* Customers can review all of the currently active Events inside of their App, under the Programs/Community tab.
* The Customer is able to filter the Events as they prefer, and can sign up for any Event if there are slots open, or sign up for the Waitlist if the Event is full.
  * Filtering Events can occur through
    * Quick Filters, which are circled in orange, or
    * Advanced Filters, which is circled in green
* This view shows a basic booking flow for a Customer seeking to find an Event, filtering for different types of Events, selecting an Event, and signing up:


---

# 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/manage-attendees/how-does-a-customer-sign-up-for-an-event.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.