> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/modules-and-features/helpdesk/cases/view-cases.md).
# View cases
You can view your support cases on the **Cases** page, including cases that are **processing**, **querying**, or **completed**.
### View your cases
To view your cases:
1. Go to **Helpdesk** > **Cases**.
2. Review the list of all cases.
The list includes key information such as the case ID, reporter, assignee, creation date, and current status.
### Open case details
There are two ways to view detailed information for a case, including messages, parameters, attachments, and more.
You can do this from the **Helpdesk** > **Cases** page, or directly from the **Chats** page.
#### From the Cases page
To open case details from the **Cases** page:
1. Go to **Helpdesk** > **Cases**.
2. (Optional) Use the 
**Filter** option to locate the desired case.
3. Select the case ID to open the case details.
#### From the Chats page
To open case details from the **Chats** page:
1. Go to **Chats**.
2. (Optional) Use the **Filter** option in the chat list to filter support cases.
3. Select a case to open the case details.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.platform.softwareone.com/modules-and-features/helpdesk/cases/view-cases.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.