> 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/deal-automations.md).
# Deal Automations
Rechat’s new Deal Automations help brokerages create more consistent transaction workflows by automatically taking action when key deal events occur.
Admins can build automations using a simple structure:
**When something happens, do this, for these deals.**
Automations can be triggered when a listing is added, an offer is received, a transaction date changes, or a scheduled milestone arrives. Actions can include:
* Sending an email or testimonial request
* Adding a task or tags
* Updating an address or Context
* Calculating one transaction date from another
* Subscribing selected contacts to a Market Report
Each automation can be limited by transaction side, property type, and status. For date-based automations, admins can choose whether the action runs when the date is entered, on the date itself, or a set number of days or weeks before or after it.
Agents can see upcoming automated actions directly in the transaction **Timeline**, making it easier to understand what is scheduled for each deal and manage queued actions when necessary.
Deal Automations are configured from **Accounts → Deal Settings → Automation**.
Ready to get started? Visit our Guides for complete instructions on creating, managing, and reviewing Deal Automations:
[**Explore the Deal Automations Guides →**](/appendix/brokerage-set-up/transaction-management-deals/deal-automations.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/whats-new/deal-automations.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.
