> 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/appendix/brokerage-set-up.md).

# Brokerage Set Up

From branding to MLS integrations, discover how a seamless setup empowers your team to work smarter and achieve more.

Getting Rechat set up properly is essential to unlocking the full potential for your agents and administrators. A seamless setup ensures that your team can hit the ground running, with all the tools they need configured and ready to go. From personalized branding to integrating MLS data, Rechat makes this process effortless, allowing you to focus on driving success.

Rechat simplifies brokerage setup with intuitive tools and expert guidance. Our platform helps you customize everything from your marketing templates to brokerage-wide settings. With our MLS integrations, your data is always accurate and up-to-date, making it easier than ever to manage listings, transactions, and compliance.

You’re not just launching a system—you’re empowering your team with a streamlined, efficient platform designed to grow your business and maximize productivity from day one.


---

# 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/appendix/brokerage-set-up.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.