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 — 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
• The Tasks inbox: folders, status filters, and search
• What creates Deficiencies tasks
• What creates Invoices tasks
• What creates Jobs tasks (and moving them between folders)
• Organize task categories and folders