> 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/how-a-customer-reviews-and-signs-a-quote.md). # How a customer reviews and signs a quote When you send a quote, the customer receives a link to a public quote page. On that page they see the full quote rendered exactly as it will print, along with a prompt at the top to review and sign, or to reach out to you with questions. The page offers two buttons: Download as PDF, which lets them save a copy, and Sign. Clicking Sign opens a short agreement: the customer types their first and last name into the signature field, then clicks Agree & Submit. By entering their name they agree that they have reviewed and approved the document, and that typing their name carries the same force and effect as a handwritten signature. Once submitted, the quote becomes Signed on your side. ## Notes the customer leaves when signing The signing box also has an optional **Notes** field, for anything the customer wants to pass along with their approval — a purchase order number, a gate code, scheduling constraints, or specific instructions for the job. Notes are for you, not for the paperwork: they are never added to the quote document, so the PDF stays exactly what the customer approved. When a signed quote has notes, they appear on the quote in a **Customer notes from signing** card beside the signed document. If the note contains a PO number you will bill against, turn on **Purchase Order** capture (Settings → Quotes & Invoices → Invoicing → Custom Fields) — with it on, Essential tries to prefill the number automatically from the signing note (and other linked notes) when you create the invoice. Either way, it's editable: open the invoice's **Purchase order** dropdown to review or replace it (choose **Custom** and type it, or pick the saved purchase order) — see [Put a customer purchase order on an invoice](/revenue/invoices/put-a-customer-purchase-order-on-an-invoice.md). Only sent, unexpired quotes can be opened and signed this way. While the quote is active, the bar at the top of the page shows **Valid through** with the final day whenever one is set. The customer can review and sign for the rest of that day. Afterward, the page explains that the quote has expired and asks the customer to contact your business. The Sign button is no longer available. Reactivating the quote gives the same link a new expiration date. If a quote has been voided or is still a draft, the public page instead shows a "this quote is not available" message with your business's contact email, so customers cannot sign something you have not sent or have taken back. You can preview exactly what the customer sees at any time from an unsigned quote using the View Sent Quote button. > **Where to find it:** The customer opens the quote link they received. On your side, from an unsigned quote, click "View Sent Quote" in the top-right to see the same public page. ## Related guides * [Attach a file to a quote](/revenue/quotes/attach-a-file-to-a-quote.md) * [Send a quote to a customer](/revenue/quotes/send-a-quote-to-a-customer.md) * [Void a quote, resend it, or view what the customer sees](/revenue/quotes/void-a-quote-resend-it-or-view-what-the-customer-sees.md) * [Add a line item to a quote](/revenue/quotes/add-a-line-item-to-a-quote.md) * [Apply a discount to a quote](/revenue/quotes/apply-a-discount-to-a-quote.md) * [Set quote validity and reactivate an expired quote](/revenue/quotes/set-quote-validity-and-reactivate-an-expired-quote.md) * [Put a customer purchase order on an invoice](/revenue/invoices/put-a-customer-purchase-order-on-an-invoice.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/how-a-customer-reviews-and-signs-a-quote.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.