> For the complete documentation index, see [llms.txt](https://docs.hashsphere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashsphere.com/support/managing-support-tickets.md).
# Managing Support Tickets
To view support tickets, select **Requests** from the user menu in the support portal:
Or select 'My requests' from the landing page:
This will take you to a list of support requests that you’re associated with, including tickets you raised and tickets you were CC’d on:
Requests can be searched and sorted by creation date and last activity.
You can filter by **My requests** vs **Requests I'm CC'd on**. You can also filter by status:
* Open
* Awaiting your reply
* Solved
You can also select 'Organization requests' to see requests raised by other members of your organization.
### Updating a ticket
When a ticket is selected, you can see the details of the ticket and a chat window for communication with the support team:
---
# 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.hashsphere.com/support/managing-support-tickets.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.
