> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/making-deals-visible-to-admins.md).

# Making Deals Visible to Admins

### Deals Visible to Admins

Rechat Admins now have access to Deals created by Agents; this allows them to efficiently examine all details before each transaction.

{% embed url="<https://rechatq.wistia.com/medias/8i44i20v6k>" %}

### Notify Admin of Deal Updates

In addition, Agents can now notify Admins of any deal updates. After providing the required data requested by the Admin office, the update submission will be immediately visible to the Admin.

This facilitates structured communication between Agents and the Admin's back office, enabling them to review updates through a streamlined process.

{% embed url="<https://rechatq.wistia.com/medias/u6xpojmbv1>" %}


---

# 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://help.rechat.com/whats-new/making-deals-visible-to-admins.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.