> 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/confirmation.md).
# Confirmation
An acknowledgement checkbox.
This question type is commonly used for documenting that the responder has read the terms and conditions or is acknowledging the information presented in the page.
The answer to a confirm question is stored as a [boolean](/response-data-collection-and-management/variable-schema.md#variable-data-types).
## **Changing the confirmation text**
You can personalize the text that shows up next to the checkbox by editing the **Confirmation text** field in the setting menu that appears when the question is selected.
## **Setting the default behavior**
If you enable the **Default to be checked** option in the setting menu, the confirmation box will appear in its checked state when the content is first loaded.
{% hint style="info" %}
In order to style the confirmation box (changing the padding between the text and the box or the color), you can style **Multiple Choice (and not the radio buttons)** boxes [checkmarks](/styling/customizing-appearance/checkmarks.md) menu.
{% 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/confirmation.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.
