> 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/revenue/quotes/quote-outreach-task-folders-and-follow-up.md). # Quote outreach task folders and follow-up When a quote is sent, Essential can enroll the contact in quote outreach and create follow-up work based on what happens next. Automatic quote reminders stop for good once the quote expires — the saved sequence is closed, not paused. After reactivating the quote, use **Resend** to send it to the customer again; that starts a fresh follow-up sequence from the beginning. ## Quote task folders * **Signed:** The quote was signed. Use **Create Job / Visit** on the task to schedule the approved work; Technician Instructions are drafted from the quote with pricing left out, the quote's line items become the visit's Parts, Labor & Items, and the quote is linked to the job so technicians see what was approved on the visit in the mobile app. * **Email Bounced:** Use the task action to send the quote to another contact or edit the contact and resend. * **Unanswered:** Follow up manually or try another contact. ## If the contact replies directly If the contact emails or calls with feedback instead of using the quote flow, revert the quote to Draft so you can make content changes and resend when ready. An Unsigned (including expired) quote reverts to Draft directly; only a Signed quote needs to be voided first. > **Where to find it:** Tasks and the open quote ## Related guides * [Send a quote to a customer](/revenue/quotes/send-a-quote-to-a-customer.md) * [Quote statuses and lifecycle](/revenue/quotes/quote-statuses-and-lifecycle.md) * [What creates Quotes tasks](/field-operations/tasks/what-creates-quotes-tasks.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/revenue/quotes/quote-outreach-task-folders-and-follow-up.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.