> 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/creating-deals.md). # Creating Deals ### New Update on Agent Deals Page We have implemented these changes on the Agents' Deals page in the latest release: * The eye option has been replaced with the "Make Visible to Office" button on top of the deals page. But the Admins can still Search the agents' deal drafts and view them. * We have changed the "Activity" button name to "Message Office" on the Listing's checklist. * In the Message office chatroom, a bell icon populates beside the agent's activities that have been done on each checklist's task. * We have also changed the "Notify Admin" to "Notify Office to Review" on the Listing checklist. * The tasks' status badges on the Listing checklist have been changed: "Notified" to "Office Notified," "Approved" to "Office Approved," and "Declined" to "Office Declined." * When the agents upload a file, DocuSign, or split the PDF, they will see a new onscreen confirmation box to submit for Review or not submit. * In the fact sheet column, a new bell icon (next to the Timeline) has been added instead of the Setting button." {% embed url="" %} --- # 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/creating-deals.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.