> 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-quotes-tasks.md). # What creates Quotes tasks Quotes tasks track what is happening with quotes you have sent. Signed means the customer signed the quote, so you can turn it into scheduled work. Email Bounced means the quote could not be delivered to the customer. Unanswered means the customer has not responded by the due date. New signatures collected in person also create Signed tasks with the quote attached; the quote does not need to have been emailed first. Their **Create Job / Visit** action carries the same quote context and planned items into the job. You work each task by moving it through its statuses. A Quotes task can also move into a custom folder your business has added, and back to its original Quotes folder, using **Move to Folder** in Quick Actions — see [Organize task categories and folders](/administration/settings/organize-task-categories-and-folders.md). The Quotes group appears if you have permission to view quotes. Open a Quotes task to see the quote number, current quote status, total price, and a preview of its description. Select **Preview quote** to open the quote document over the task without losing your place. The quote number links to the full quote when you need its controls, timeline, or complete editing view. On a Signed task, **Create Job / Visit** carries the quote into the job: Technician Instructions are drafted from the quote (its description, line items, and the customer's signing note, with pricing left out) in the style of the instructions your office has saved before, the quote's line items become the visit's **Parts, Labor & Items**, and the quote is linked to the job so it shows on the job's Quotes tab. Technicians see the instructions and the line items on the visit in the mobile app. See [Quick Actions on a task](/field-operations/tasks/quick-actions-on-a-task-create-a-visit-invoice-or-quote-without-leaving-the-task.md). > **Where to find it:** Tasks page, the Quotes 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-quotes-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.