> 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.md).

# Transactions

Whether you are working with a buyer, representing a seller, or supporting transactions across a brokerage, Rechat helps everyone work from the same connected Deal.

<figure><img src="/files/VmratFvjswJHriYcgcGE" alt=""><figcaption></figcaption></figure>

### What can you do in Transactions?

Depending on your role, permissions, and brokerage configuration, you can use Transactions to:

* Create and manage listing and buyer Deals.
* Keep important property and transaction information organized.
* Add clients, agents, title representatives, and other transaction contacts.
* Track important dates and deadlines.
* Follow a brokerage-provided transaction checklist.
* Prepare forms and send documents for electronic signature.
* Upload, email, organize, and split transaction documents.
* Submit documents to your office for review.
* Add an offer to an existing listing Deal.
* Manage a transaction through closing.
* Create marketing using information and photos from a Deal.

### How a transaction moves through Rechat

A typical transaction follows this path:

1. Create a Deal.
2. Add the property, side represented, clients, and other known details.
3. Review the Deal workspace and brokerage-provided checklist.
4. Prepare or upload the required documents.
5. Send documents for signatures when needed.
6. Submit completed documents to the office for review.
7. Add an accepted offer to a listing Deal or manage the buyer contract.
8. Track dates, tasks, documents, and feedback through closing.
9. Complete the transaction and retain its record in Rechat.

### Your experience may vary

Your brokerage determines many parts of its transaction process, including:

* Questions asked during Deal creation
* Property and transaction types
* Available forms
* Checklist items
* Required and optional documents
* Contact roles
* Deal statuses
* Office-review requirements

The examples in this Help Center demonstrate common Rechat workflows. Your screens and requirements may look different.

### Deals for agents and administrators

Agents use **My deals** to create, find, and manage the Deals in which they are involved.

Admins use **Transactions Admin** to locate Deals across the brokerage, monitor operational inboxes, review submitted documents, and identify transactions that require attention.

### Get started

* [Create a Deal](/guides/deals/create-a-deal.md)
* [Navigate and Manage Your Deals](/guides/deals/navigate-and-manage-your-deals.md)
* [Understand Your Deal Workspace](/guides/deals/understand-your-deal-workspace.md)
* [Understand Your Transaction Checklist](/guides/deals/understand-your-transaction-checklist.md)


---

# 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.md?ask=<question>&goal=<endgoal>
```

`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.
