> 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/the-contact-documents-tab.md).
# The Contact Documents Tab
This lesson describes the functionality of the **Contact Documents** tab under a contact.
{% stepper %}
{% step %}
## Upload a document
The **Contact Documents** tab can be used to upload and store any external documents concerning the contact. To begin uploading a document, click **Upload Document**.
{% endstep %}
{% step %}
## Select a document
The window that appears allows you to select as many files as necessary using the **Add files** button. Once you have all of your files selected, click **Start upload** to upload them to the system.
If you change your mind at any point, you can click **Cancel upload** to stop uploading the files.
{% endstep %}
{% step %}
## Access uploaded documents
Once your documents have been uploaded, they will be stored under this tab for easy access by system users.
{% 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/user-documentation/the-contact-tab/the-contact-documents-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.