> 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/why-do-some-events-show-how-many-spots-are-left.md).

# Why do some Events show how many spots are left

Whether Customers see how many spots remain depends on your Club's configuration. See [Attendee List and Spots Left Configuration](/events/create-an-event/attendee-list-and-spots-left-configuration.md) for the full setup guide.

**In the App:**

* When **Show Spots Left** is enabled for an Event, the Event detail page shows how many spots remain (for example, "3 spots left").
* Event cards show a blue **ONLY X SPOTS LEFT** tag when fewer than 10 spots remain.
* Events with 10 or more spots remaining do not show the blue tag on the card, but may still show the count on the Event detail page.

**To turn off spot counts for a specific Event:** open the Event, go to **Advanced Features**, and toggle off **Show Spots Left**. This requires the area-level **Show Spots Left and Attendees List on Events** setting to be on.


---

# 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/why-do-some-events-show-how-many-spots-are-left.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.