> For the complete documentation index, see [llms.txt](https://docs.cooltix.com/cooltix-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cooltix.com/cooltix-support/organizers/order-settings/order-form.md).

# Order form

### Buyer questions

Collect additional information from your buyer. Customer name, customer email address, and invoicing details are asked by default, you don't have to manually add these questions.

Additional buyer questions will be asked once per order.

You can decide which questions are mandatory to answer, and you can even hide questions temporarily.

If you want to ask for information per ticket, and not just once per order, you can add such questions in the Attendee questions section.

### Attendee questions

Collect additional information from your attendees. These questions will be asked about each attendee, in other words per every ticket put in the basket. This is where you can decide if the name of the attendees should appear on the ticket or not.

You can decide which questions are mandatory to answer, and you can even hide questions temporarily.

If you want to ask for information per order, and per every purchased ticket, you can add such questions in the Buyer questions section.

{% hint style="info" %}
All details given by the customers upon signing up or making a purchase will be put at the organizers' disposal without exception, in accordance with the general terms and conditions accepted upon signing up or making a purchase. Organizers may use this data in accordance with their own terms and conditions. Terms and conditions must be in compliance with GDPR standards.
{% endhint %}

&#x20;


---

# 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.cooltix.com/cooltix-support/organizers/order-settings/order-form.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.
