> 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/create-case.md).

# Create case

You can create a support case from any of the following locations:

* Select the help icon <i class="fa-circle-question">:circle-question:</i> in the header, then choose **Need help**.&#x20;
* Go to **Helpdesk** > **Cases**, then select **Add**.
* Go to **Chats**, then select **+ Support case**.

Regardless of where you start, the same **Add case** wizard opens.

### Create a case

To create a case:

1. Open the **Add case** flow from one of the available entry points.
2. In the guided **Add case** flow, complete the following steps:
   1. Select the area you need help with, then select **Next**.&#x20;
   2. Review the available self-help resources. If you still need assistance, select **Next** to continue.
   3. Provide details about your request or issue.
   4. Select **Add** to submit the case.

After you submit the case, it is routed to the appropriate team based on the information you provide. You can view your submitted case on the **Cases** page. For more details, see [View cases](/modules-and-features/helpdesk/cases/view-cases.md).


---

# 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/create-case.md?ask=<question>&goal=<user_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.