> For the complete documentation index, see [llms.txt](https://help.paintscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.paintscout.com/support/estimating/sending-and-acceptance.md). # Sending & Acceptance Send estimates to customers, understand how they view and accept proposals, and collect signatures. Once your estimate is ready, send it with the right delivery and acceptance flow. This section covers email and text delivery, customer preview and acceptance, onsite signatures, and sharing estimates or work orders with your team. ## In This Section * [Sending Estimates](/support/estimating/sending-and-acceptance/sending-estimates.md) — Send estimates by email or text, customize the message, and control follow-up settings * [How Customers View & Accept](/support/estimating/sending-and-acceptance/how-customers-view-accept-estimates.md) — See how customers open the estimate, review terms, download it, and accept online * [Accepting On Site](/support/estimating/sending-and-acceptance/accepting-estimates-on-site.md) — Present the estimate in person with preview mode and capture a signature on the spot * [How Signatures Work](/support/estimating/sending-and-acceptance/how-signatures-work.md) — Understand estimator and customer signatures, where they come from, and how they appear on accepted estimates * [Share With Your Team](/support/estimating/sending-and-acceptance/how-to-share-estimates-and-work-orders-with-your-team.md) — Share estimates and work orders by email, live link, PDF, or staff sharing permissions --- # 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://help.paintscout.com/support/estimating/sending-and-acceptance.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.