> For the complete documentation index, see [llms.txt](https://docs.allocations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allocations.com/why-allocations/deal-support.md).

# Deal Support

The Support tab holds every support conversation about a deal. Use it to raise or follow up a request with the Allocations team.

![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/q4Vsa4WczNBPhDR4HCUZ/Unknown%20image)

1. **Conversations** Lists the support threads for this deal, with Refresh and New at the top.
2. **Search conversations** Finds a support thread by typing a keyword.
3. **Status filters** Filter threads to All, Open, Pending, or Closed, each with its own count.
4. **Conversation** Shows one support thread with who raised it, its subject, and the date.
5. **Tags** Show the channel the thread arrived on and its current status.
6. **Reading pane** Shows the selected conversation in full, with every reply in order.

### Statuses

Each conversation has a status, and the filters above the list count the threads in each one.

* **Open:** The thread is active and awaiting a reply from support.
* **Pending:** The thread is waiting on information or an action.
* **Closed:** The thread has been resolved and is kept on the deal's record.

### Starting a conversation

Select New to start a conversation.


---

# 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.allocations.com/why-allocations/deal-support.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.