> 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-case-tab.md).
# The Case Tab
This is what a case screen looks like in AgileCase. Case information is displayed in the box at the top of the page whilst the different areas of the case are allocated their own tabs below.
The elements of the case page are as follows:
* **Details** lists any custom fields assigned to the case type.
* **Client** displays information concerning the client of the case.
* **Bills** contains the billing information for the case.
* **Contacts** contains the details of any contacts listed against the case.
* **Tasks** displays any tasks saved in the case and allows you to manage them.
* **Calendar** contains all of the calendars available in the case and allows you to manage them and view upcoming events.
* **Docs& Comms** contains all of the documents listed against the case and allows you to create them using templates.
* **Time** allows you to make time entries against the case for the purposes of fees and reporting.
* **Expenses** allows you to make expense entries against a case.
* **Audit** provides you with a history of actions made by users in the case.
* **Contact Details** displays any contact custom fields relevant to the case.
---
# 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-case-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.