> 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/how-automated-outreach-batches-are-built-and-who-they-go-to.md). # How automated outreach batches are built and who they go to Automated Outreach goes out in batches. When recurring services come due and their automation is set to Automated Outreach, Essential builds the outreach per contact: it gathers that contact's due recurring services and combines the ones whose due dates fall close together (within the business's outreach batch window) into a single batch, so the customer gets one message covering several due services instead of a separate message for each. A batch ties one contact to the recurring service schedule(s) it covers, and it runs as those services come due. Who a batch goes to is decided by contact role: Essential uses the property's approvals contact first, and if there isn't one it falls back in order to the scheduling, then onsite, then billing contact. Within a role it prefers a property-level contact over a customer-level (account-wide) one, and a primary contact over a secondary one. If no contact holds any of these roles for the property, the automation can't send - that's the "Add a contact role to this property to enable outreach" blocker. > **Where to find it:** Built automatically from due recurring services; the recipient and timing show on the asset group's Next Automation card and on the Automated Outreach page ## Related guides * [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 recurring service automation works (the full cycle)](/administration/how-recurring-service-automation-works-the-full-cycle.md) * [What "Awaiting Service Completion" means and how it clears](/administration/how-recurring-service-automation-works-the-full-cycle/what-awaiting-service-completion-means-and-how-it-clears.md) * [What happens after automated outreach: the customer's response](/administration/how-recurring-service-automation-works-the-full-cycle/what-happens-after-automated-outreach-the-customers-response.md) * [Visit types: which services an inspection report can complete and reset](/administration/how-recurring-service-automation-works-the-full-cycle/visit-types-which-services-an-inspection-report-can-complete-and-reset.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://learn.withessential.com/administration/how-recurring-service-automation-works-the-full-cycle/how-automated-outreach-batches-are-built-and-who-they-go-to.md?ask=&goal= ``` `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.