> 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/deal-automations.md). # Deal Automations Deal Automations allow Rechat to complete scheduled follow-up and transaction activities without requiring you to recreate the workflow manually.
### Where automations appear Open the deal and review the **Timeline** on the left side of the deal. Upcoming automations appear beneath the date or context that controls when they will run. A lightning-bolt icon identifies an automated action. For example, beneath the Closing Date, you may see: * Ask For Testimonials * Subscribe to Market Report ### What agents can control Agents can see the automations scheduled for their deals and turn off an upcoming automation when it is not appropriate for that specific transaction. Agents cannot: * Change the brokerage’s original automation. * Change the automation for other deals. * Access the admin Automation builder. * Change the action, timing, recipients, or deal conditions established by the admin. Turning off an automation affects only the individual deal. ### Why an automation may not run An automation may be unable to run if: * Its required date has not been entered. * The deal does not have the required status when the action is scheduled to run. * A selected recipient or deal role is missing. * Required contact information is unavailable. * Required property information is incomplete. * The automation was turned off for the individual deal. Keep the deal’s dates, statuses, contacts, roles, and property information current so Rechat can complete scheduled actions accurately. {% hint style="info" %} Changing a deal date may also change when its related automations are scheduled to run. {% endhint %} ### Completed automations After an automation runs, the Timeline provides a record of the completed activity beneath the relevant deal context. Completed automations cannot be changed because they represent actions Rechat has already performed. --- # 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/guides/deals/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.