> 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/field-operations/tasks/what-creates-recurring-services-tasks.md). # What creates Recurring Services tasks Recurring Services tasks come from how a customer responded to a recurring service request you sent them, with one manual exception. The folders are Approved (the customer approved the service), Declined (they declined), Ask Someone Else (they asked you to contact a different person), Email Bounced (the request could not be delivered), and Unanswered (they never responded by the due date). The Custom folder is the exception: those tasks come from the custom task settings on an asset group's recurring service schedule (RSS), not from a customer response. You work each task by moving it through its statuses. A Recurring Services task can also move into a custom folder your business has added, and back to its original folder, using **Move to Folder** in Quick Actions — see [Organize task categories and folders](/administration/settings/organize-task-categories-and-folders.md) — but Move to Folder cannot switch it directly to a different built-in Recurring Services folder, such as from Approved to Declined. Typical next steps are: schedule a job or visit for Approved tasks, mark the customer or property inactive for Declined tasks when the site is no longer operating, restart outreach or manually contact a new person for Ask Someone Else, update the email address and restart outreach for Email Bounced, and follow up manually for Unanswered or Custom tasks. A text message that fails while the email was delivered does not create an Email Bounced task; the outreach keeps going and the failed text shows on the outreach's schedule. If a customer answers an outreach after it already filed an Email Bounced or Unanswered task, that task moves on according to your task automations. > **Where to find it:** Tasks page, the Recurring Services group in the left sidebar ## Related guides * [How tasks are created and organized](/field-operations/tasks/how-tasks-are-created-and-organized.md) * [The Tasks inbox: folders, status filters, and search](/field-operations/tasks/the-tasks-inbox-folders-status-filters-and-search.md) * [What creates Deficiencies tasks](/field-operations/tasks/what-creates-deficiencies-tasks.md) * [What creates Invoices tasks](/field-operations/tasks/what-creates-invoices-tasks.md) * [What creates Jobs tasks (and moving them between folders)](/field-operations/tasks/what-creates-jobs-tasks-and-moving-them-between-folders.md) * [Organize task categories and folders](/administration/settings/organize-task-categories-and-folders.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/field-operations/tasks/what-creates-recurring-services-tasks.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.