> 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/customization/templates-and-presets/estimate-disclaimers.md).

# Estimate Disclaimers

Customize acceptance and decline disclaimers that appear below the signature box when customers respond to estimates.

Estimate Disclaimers in PaintScout are customizable messages that appear below the signature box when customers accept or decline an estimate.

➡️ **Skip to the 5:41 timestamp in the video below.**

{% embed url="<https://www.youtube.com/watch?v=Sc-iM49Nu4Y>" %}

## What are Acceptance Disclaimers?

PaintScout requires an electronic signature from your customer upon acceptance. The acceptance disclaimer is the message displayed below the signature box when customers accept estimates or additional work.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-b52f451d271eddde87e56df154cb05a50359dcb4%2F65bada1d1d9f10d1d461c9a2_Screenshot_2023-08-20_at_2.05.37_PM.png?alt=media" alt="Screenshot showing the acceptance disclaimer settings displayed below the electronic signature box"><figcaption></figcaption></figure>

***

## How do I let customers decline estimates?

Toggle on the **Declined** option to give customers a decline button on the estimate. You can add a custom disclaimer message, similar to the acceptance disclaimer.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-18ab36554cb02dfdf4baf27098a862d59dd3a20d%2Fde0fae17e2a4c9a63764947f_Screenshot_2023-08-20_at_2.05.53_PM.png?alt=media" alt="Screenshot showing the decline disclaimer toggle and message field for customer estimate declines"><figcaption></figcaption></figure>

Customers can also provide a reason for their decline after clicking the "decline" button on the estimate.

&#x20;&#x20;

## Related articles

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Updating Estimate Terms</strong></td><td>Add, edit, and manage contract terms in your account settings, plus learn how to change or update terms on individual estimates before they are accepted.</td><td><a href="/support/customization/presentations-and-terms/updating-estimate-terms.md">Updating Estimate Terms</a></td></tr><tr><td><strong>Setting Default Terms</strong></td><td>Set default contract terms for each estimate type so the correct terms are automatically applied every time you create a new estimate.</td><td><a href="/support/customization/presentations-and-terms/setting-default-terms.md">Setting Default Terms</a></td></tr></tbody></table>


---

# 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/customization/templates-and-presets/estimate-disclaimers.md?ask=<question>&goal=<user_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.
