> 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-happens-after-automated-outreach-the-customers-response.md). # What happens after automated outreach: the customer's response Automated Outreach sends the customer a short series of messages (reminders) asking them to approve and schedule the upcoming recurring service. What happens next depends on their reply, and every outcome comes back to you as a Recurring Services task on the Tasks page - Essential does NOT schedule the visit for you. Approved or Declined: the answer is recorded as a task, and for an approved service you schedule the visit yourself from that task. Ask Someone Else: the customer points you to a different contact, whose details are saved on the task for you to follow up - but Essential does NOT automatically send a new outreach to them. Unanswered: if no one responds within a few days, the outreach stops on its own and files an Unanswered task. Email Bounced (or a failed text): delivery failed, so a Bounced task is created for you to fix the contact's email or number and try again. In every case the recurring service moves to Awaiting Service Completion until the work is recorded, so the automation won't keep re-sending. > **Where to find it:** The reply comes back as a Recurring Services task on the Tasks page; the asset group's Next Automation card shows the in-progress outreach ## Related guides * [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) * [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) * [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) * [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) --- # 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/what-happens-after-automated-outreach-the-customers-response.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.