> 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/what-are-the-different-ways-a-customer-can-be-adde.md).

# What are the different ways a Customer can be adde

* When to add a customer to an Event, there are three options the Admin can choose from.
  * Regular - the customer is charged the set amount (based upon Member vs. Non-member pricing) for the Event, and the customer is counted toward the total number of participants
  * Free - the customer is not charged anything for joining the Event, whether they are a Member or a Non-member, and the customer is counted toward the total number of participants
  * Guest - the customer is not charged anything for joining the Event, whether they are a Member or Non-member, and the customer is NOT counted toward the total number of participants


---

# 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/what-are-the-different-ways-a-customer-can-be-adde.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.