> 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/transaction-management-deals/deal-automations.md).

# Deal Automations

Deal Automations connect your brokerage’s transaction workflows with Rechat’s CRM and marketing tools.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2F1hyot2Sl2SU52zznJWOG%2F2026-09-22_14-22-52.png?alt=media&amp;token=ced4fe08-c5d9-49fd-aea7-8d612b433441" alt=""><figcaption></figcaption></figure>

Admins can define when something should happen, what Rechat should do, and which deals should qualify—all without requiring agents to repeat the same work manually.

Use Deal Automations to create consistent processes across your organization, reduce missed follow-up, and keep client and deal information up to date throughout the transaction.

{% hint style="info" %}
**Deal Automations is currently in beta.** Available options and behavior may continue to evolve as Rechat introduces new automation capabilities.
{% endhint %}

### What can Deal Automations do?

Deal Automations can respond to deal events, context changes, and important dates.

Depending on the automation, Rechat can:

* Send an email from the agent.
* Update a buyer’s address using the property information from the deal.
* Send a testimonial request.
* Copy or calculate deal dates.
* Add tags to contacts associated with the deal.
* Subscribe selected deal participants to a monthly market report.
* Add a task, form, application, or SkySlope Form to the deal checklist.

For example, your brokerage could create automations that:

* Send a testimonial request on the Closing Date.
* Subscribe a buyer to a market report after closing.
* Update a buyer’s contact record with their new address.
* Add a required disclosure to the checklist when a property meets certain criteria.
* Set the Listing Expiration to one year after the Listing Start Date.
* Send an email to the agent when an offer is received.
* Tag buyers and sellers as past clients when the deal closes.

### How an automation works

Each automation is built as a sentence:

> When **something happens**, **do this**, for **these deals**.

The three parts determine:

<table><thead><tr><th width="252.4296875">Part</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>When something happens</strong></td><td>The event, context change, or date that starts the automation</td></tr><tr><td><strong>Do this</strong></td><td>The action Rechat performs</td></tr><tr><td><strong>For these deals</strong></td><td>The deal side, property types, and statuses that qualify</td></tr></tbody></table>

An automation will only run when its trigger occurs and the deal satisfies the conditions selected by the admin.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2FKAh0yPpldcwQXhZdyRsG%2F2026-09-22_14-19-28.png?alt=media&amp;token=7e33db4c-82d7-4049-9cf3-49dee45eef2c" alt=""><figcaption></figcaption></figure>

### Admin and agent experiences

#### Admins

Admins create and manage Deal Automations under the selected team or office’s **Deal Settings**.

Admins determine:

* What starts the automation.
* When a date-based automation runs.
* What Rechat does.
* Who receives an email, tag, testimonial request, or market report.
* Which deal sides and property types qualify.
* Which deal statuses qualify when the action runs.

Admins can also edit or delete the automations created at their organizational level.

#### Agents

Agents do not create or change the brokerage’s Deal Automations. When an automation applies to one of their deals, it appears beneath the applicable date or context in the deal’s **Timeline**.

Agents can see what Rechat is scheduled to do and can turn off an upcoming automation for their individual deal. Turning off an automation on one deal does not change the original admin automation or affect other deals.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2Fro6H4HiyltNgGEfixahd%2F2026-09-22_14-22-52.png?alt=media&amp;token=cc67cfd4-eaf3-4fba-a3ca-f702e1922a16" alt=""><figcaption></figcaption></figure>

### When automations are added to deals

Automations created for a team or office are applied to qualifying new deals.

Each deal retains the automation it received when the deal began. If an admin later edits or deletes the original automation, existing deals are not retroactively rewritten.

* Editing an automation changes what is applied to new deals going forward.
* Deleting an automation removes it from new deals.
* Existing deals retain their previously scheduled automation.
* An agent turning off an automation affects only that individual deal.

{% hint style="info" %}
Deleting an automation does not remove it from deals that have already received it. The delete confirmation specifically states that the automation will be removed from all **new deals**.
{% endhint %}

### Automation inheritance

When an automation is created at a parent brand or organizational level, it applies to the teams and offices beneath it.

Inherited automations:

* Appear in the child team’s Automation list.
* Are identified as being added by an admin.
* Cannot be edited, disabled, or deleted by the child team.
* Can only be changed at the organizational level where they were created.

A child team can still create additional automations for its own deals.

### Before you create an automation

Review the entire workflow the automation will support, including:

* The trigger that should start it.
* Whether the action should happen immediately or relative to a date.
* The people who should receive or be affected by the action.
* The deal sides and property types that qualify.
* The deal status that should be required when the action runs.
* The information Rechat needs to complete the action successfully.

{% hint style="info" icon="head-side-brain" %}
**Best practice:** Start with a narrowly defined automation and confirm that it behaves as intended before expanding it to additional property types, sides, statuses, or recipients.
{% endhint %}

### Related guides

[**Create and Manage Deal Automations**](/appendix/brokerage-set-up/transaction-management-deals/deal-automations/create-and-manage-deal-automations.md)

[**View Deal Automations on an Individual Deal**](/appendix/brokerage-set-up/transaction-management-deals/deal-automations/view-deal-automations-on-an-individual-deal.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 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/transaction-management-deals/deal-automations.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.