> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/adding-questions-and-content/question-reference/yes-no.md).
# Yes/No
A yes or no question.
Yes/no questions are a quick way to add a binary question type to your form. The value types of these questions are stored as the boolean `true` or `false` data type.
```
{
"Am I a yes/no question?": true
}
```
### Customizing the question
A boolean question may use any of the [styles of the select question](/adding-questions-and-content/question-reference/select.md#styling-choices), but defaults to displaying as buttons.
Yes/no questions only have two choices, but the "yes" and "no" labels of the choices can be changed in the choices tab.
The boolean true/false values of the choices cannot be changed.
{% hint style="info" %}
If you'd like to have more than two choices mapped to true or false, use a [select](/adding-questions-and-content/question-reference/select.md) question and change *Choice value type* to boolean.
Similarly, use a select question if you need an alternative value type to Boolean returned altogether.
{% endhint %}
---
# 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.formsort.com/adding-questions-and-content/question-reference/yes-no.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.
