> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/help-desk/settings/custom-ticket-builder/types-of-questions-labels.md).
# Types of Questions/Labels
We try to accommodate all our customers needs in our Custom Ticket Builder. Here is a list of all the types of questions and Labels and what they do/ look like to the end user.
## 1. Text
* Use this when you need a single line answer to a question/label.
\*
```
```
* Here is what it will look like to the end user.
\*
```
```
## 2. Number
* Use this when you need a numerical answer to a question/label and you do **not** want any text in the answer.
\*
```
```
* Here is what your end user will see.
\*
```
```
## 3. Multiline Text
* Use this when you need your user to give more detail then a single text line allows.
\*
```
```
* Here is what the end user will see.
\*
```
```
## 4. Checkbox
* Use this when you want a user to check if a question applies to them.
*
* Here is the end user's view.
*
## 5. Date
* Use this to add a date/ pop up calendar for the user.
\*
```
```
* Here is what the end user will see.
\*
```
```
## 6. Conditional
* Use this if you have a yes/no condition. I've also added a condition to this question as well.
\*
```
```
* Here is what the end user will see.
*
## 7. Selection
* Use this when you need a drop down menu and multiple selections. Enter your selections under "Options".
\*
```
```
* Here is what the end user sees.
\*
```
```
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.adminremix.com/help-desk/settings/custom-ticket-builder/types-of-questions-labels.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
## 5. Date
* Use this to add a date/ pop up calendar for the user.
\*
```
## 7. Selection
* Use this when you need a drop down menu and multiple selections. Enter your selections under "Options".
\*
```