> 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/guides/deals/2.-deals-profile-view.md).
# Deal Profile View
1. Inside of your deal you will find all of the key information about your listing and the required documents.
2. On top, you’ll find the property address and some key actions for your deal.
3. Once the listing is in the MLS, you can enter the MLS number right under the deal address, which would then connect your deal to its respective MLS listing and have its information auto-populated from the MLS.
4. On the left side of the page, you will find all of your deal’s key facts such as the critical dates, key listing information, and contract information. This information will then be used to auto-populate the required forms in that deal.
5. The documents are listed in the order in which you would most likely need to complete them, and some are marked as **Required** by your office which means they are mandatory for that particular deal.
6. If you need a form that does not appear on the list, you can scroll to the bottom and choose **Upload** in **Unorganized Files**. Or you can email files to the **Unique Deals Email.**
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.rechat.com/guides/deals/2.-deals-profile-view.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.