> 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/the-contact-tab.md).
# The Contact Tab
This example shows the layout of a standard contact page. The basic contact information is listed in the center of the page whilst more specialized areas are allocated their own tab on the sub-toolbar along the bottom.
This page will briefly run through the functionality of the elements on the page. To see a more in-depth guide, click the appropriate lesson on the menu above.
* The top of the page contains links to several external elements. "Enable Client Connect" will send the client an invitation to client connect, "Perform Veriphy ID Check" allows you to perform an ID check using the external Veriphy sytem, "Create Case" will create a case with the selected contact as client.
* Basic information for the contact is listed below. This consists of the contact's address and contact details as well as their position within their company and any system labels you have applied to them.
* The contact page toolbar gives you access to specific contact information through a selection of tabs. The "Cases" tab displays all of the cases for which the contact is listed as client.
* The "Related Cases" tab shows all of the cases that the contact is not the client of but is linked to through a relationship.
* The "Notes" tab displays all of the notes listed against this client.
* The "Tasks" tab allows you to add tasks related to this contact to a case.
* The "Communications" tab displays any emails sent to this contact from the system.
* The "Documents" tab displays any documents that you have created against this contact.
* The "Details" tab stores any contact custom fields types stored against this contact.
---
# 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/the-contact-tab.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.