> 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/email-and-communication/email-settings/automatic-thank-you-emails.md).

# Automatic Thank You Emails

Configure automatic thank you emails to be sent when customers accept or decline estimates, with customizable subject lines and body content.

Automatic Thank You Emails in PaintScout send a customizable email to customers when they accept or decline an estimate, without any manual action required.

➡️ **Skip to the 1:56 timestamp in the video below.**

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

1\. Click the person icon in the top right of your page and go to your **Account Settings** > **Communications** > **Email Templates** > **Emails Sent Automatically** section.

2\. Click on the **Thank you - Accepted** or **Thank you - Declined** estimate templates. These will get automatically sent when estimates have been accepted or declined.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-62257c5ed57044ab30d5ee33f723b2c2e8c276c4%2Fd075421172f4247d0f20f4a2_PaintScout_Settings_2024-01-22_at_3.50.18_PM.jpg?alt=media" alt="Screenshot showing the Thank You - Accepted and Thank You - Declined email templates in the automatic emails section"><figcaption></figcaption></figure>

3\. Fill in your subject line and body of the email. Make sure to have the **'Enabled'** checkbox on.

<figure><img src="https://231248629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPyUbJF1GXLjxdJqm89IQ%2Fuploads%2Fgit-blob-4b4526e1ffcd165d03acf2538a026e7f83246157%2Fcf53339752e0529683ef557a_PaintScout_Settings_2024-01-22_at_3.51.19_PM.jpg?alt=media" alt="Screenshot showing the email template editor with subject line, body content, and Enabled checkbox"><figcaption></figcaption></figure>

&#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>Payment Emails</strong></td><td>Customize automatic emails for received, processing, failed, and refunded payments.</td><td><a href="/support/email-and-communication/email-settings/payment-received-emails.md">Payment Emails</a></td></tr><tr><td><strong>Automatic Emails</strong></td><td>Customize automatic email templates that send when estimates are accepted, declined, payments received, or events are booked or cancelled.</td><td><a href="/support/email-and-communication/email-settings/automatic-emails.md">Automatic Emails</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/email-and-communication/email-settings/automatic-thank-you-emails.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.
