> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/case-type-settings/changing-mandatory-fields-in-the-contact-form.md).
# Changing Mandatory Fields in the Contact Form
This lesson will show you how to choose which fields are mandatory in the "Add Contact" form.
{% stepper %}
{% step %}
### Access "Create Contact Form"
When adding a contact to AgileCase, there will be certain fields that you want filled in as part of the minimum criteria to create a contact.
First, access the contact form page by clicking "Create Contact Form" under "Case Type Settings".
{% endstep %}
{% step %}
### Check the boxes to toggle mandatory status
On the contact form page, click the checkbox for the fields you want to make mandatory. Once this has been done, click "Save Changes" to finish.
{% endstep %}
{% step %}
### The selected fields will now be mandatory
When you next go to create a contact, the fields you marked as mandatory will have to be filled in to proceed.
{% endstep %}
{% endstepper %}
---
# 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.agilecase.com/administrator-documentation/case-type-settings/changing-mandatory-fields-in-the-contact-form.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.