> 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/custom-task-automation-an-internal-task-instead-of-customer-outreach.md). # Custom Task automation: an internal task instead of customer outreach An asset group's automation can be set to Custom Task instead of Automated Outreach. With Custom Task nothing is sent to the customer: each cycle, when the service comes due, Essential automatically creates an internal task for your team carrying the notes you set up, and that task lands in the Custom group under Recurring Services on the Tasks page. Use it for recurring work that doesn't need the customer's approval - an internal inspection, a routine check - where you just want a reminder to do the work. It contrasts with Automated Outreach, which messages the customer for approval, and with None, which fires no automation at all (you schedule the work yourself). Like outreach, creating the custom task moves the recurring service to Awaiting Service Completion until the work is recorded. > **Where to find it:** Chosen as the Type on the asset group's Automation Setup card; the task it creates lands in the Custom group under Recurring Services on the Tasks page ## 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) * [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) * [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) * [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 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/custom-task-automation-an-internal-task-instead-of-customer-outreach.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.