> 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/user-documentation/dashboard/creating-a-contact-person.md).
# Creating a Contact (Person)
This lesson will show you how to add a person as a contact in AgileCase.
### Enter Contact Details
Once you have chosen to add a contact, you will be given the opportunity to fill out the contact details. First of all, enter basic information including their name, date of birth, and address details.
### Enter Further Information
You can also add contact details in the form of an email address and phone number, as well as passport, driving license, and social security numbers.
After this, you can add the contact's company details, selecting their company, position, and client status. You can also apply system labels at this stage. At the bottom of the contact screen, there is the option to fill in any contact custom fields that you have created, in this case "Primary Contact".
Once you have finished entering your contact details, click "Save Contact" to create the new contact.
### View Contact
Once the contact has been created, you can view them under the "Contacts" tab on the toolbar.
---
# 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/user-documentation/dashboard/creating-a-contact-person.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.