> For the complete documentation index, see [llms.txt](https://docs.indinite.co.uk/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.indinite.co.uk/manual-attendee-add.md).
# β Manual Attendee Add
### π Why Youβll Love It
* βοΈ **Quick & Easy** β Add attendee details right from your dashboard.
* ποΈ **No Ticket? No Problem** β Perfect for walk-ins, offline sales, or complimentary passes.
* π οΈ **Full Control** β Assign them to any ticket type (regular or pass).
* π **All Synced Up** β Added attendees show up in your attendee list, reports, and check-in logs.
### πΉοΈ How It Works
1. Head to the **Attendees** section in your event dashboard.
2. Click **Add Attendee**.
3. Fill in their details (name, email, ticket type, etc.).
4. Done β β theyβre now part of your event just like any online buyer.
### π― Best Use Cases
* Walk-in guests at the gate πͺ
* Bulk offline sales π«
* Complimentary/VIP passes π
* Last-minute entries π
---
# 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.indinite.co.uk/manual-attendee-add.md?ask=&goal=
```
`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.