> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/how-recurring-service-automation-works-the-full-cycle/what-automated-outreach-sends-and-previewing-it.md). # What automated outreach sends, and previewing it When a recurring service is set to Automated Outreach, Essential automatically sends the customer a request, by email or text, to approve and schedule the upcoming service. You can see what's coming on the asset group's Next Automation card: it shows the automation ("Automation #A..."), whether it is In Progress or Not Started, and the next step, such as "Next send: " (or "Creates task: " when the automation is a custom task). If one automation covers several asset groups, they are grouped as a single batch and listed on the card. Use the Preview button to see the exact Outreach Content, the email subject and body or the text message, before it goes out. The customer's reply comes back to you as a Recurring Services task. > **Where to find it:** On the asset group page, the Next Automation card (the Preview button opens Outreach Content) ## Related guides * [Why isn't an asset group's automation running? (blockers)](/administration/how-recurring-service-automation-works-the-full-cycle/why-isnt-an-asset-groups-automation-running-blockers.md) * [Custom fields: your business's extra fields on records](/administration/basics/custom-fields-your-businesss-extra-fields-on-records.md) * [Custom Task automation: an internal task instead of customer outreach](/administration/how-recurring-service-automation-works-the-full-cycle/custom-task-automation-an-internal-task-instead-of-customer-outreach.md) * [How automated outreach batches are built and who they go to](/administration/how-recurring-service-automation-works-the-full-cycle/how-automated-outreach-batches-are-built-and-who-they-go-to.md) * [How recurring service automation works (the full cycle)](/administration/how-recurring-service-automation-works-the-full-cycle.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://learn.withessential.com/administration/how-recurring-service-automation-works-the-full-cycle/what-automated-outreach-sends-and-previewing-it.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.