> 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/administration/settings/set-the-confirmation-email-for-automated-outreach.md).

# Set the confirmation email for automated outreach

The Confirmation email section on the Automated Outreach tab of Settings -> Automations is the email a customer gets after submitting a Job Approval form. Set its **Subject** and body - both are required before you can save. **Subject when any service is denied** is optional. When set, it replaces the regular subject if the submission contains at least one denial; the same confirmation body is used. Both subjects are plain text fields: they're sent exactly as typed, so variables don't fill in there.

The body opens in **Visual**, the rendered email: click any text and type to change it. To add a variable, click in the text where it should go, then select **Insert variable** and pick one — or pick it first, then click where it should go (see [Add a variable](/administration/settings/edit-a-document-templates-design-with-edit-code.md#add-a-variable)). Variables show sample customer details, while your business's real email, website, and logo render the way a live send would. Hover a variable to see its name; Backspace or Delete removes it. Select **Edit code** in the **Visual / Edit code** switch for logic, layout, styling, or the list of services (written as a loop); switching never loses or rewrites anything.

If the body has an error, a red notice appears under it and **Save changes** stays unavailable until you fix it; a yellow notice flags a variable that doesn't exist. See [Errors and warnings](/administration/settings/edit-a-document-templates-design-with-edit-code.md#errors-and-warnings). The subjects aren't checked, since they're plain text.

The variables include the services covered by the submitted request. If the form asks for a billing destination, `{{ billing_destination }}` contains the customer's destination exactly as entered and `{{ billing_instructions }}` contains any additional billing instructions. Visual shows sample values before you save.

Both subject editors start at one line and grow automatically as text wraps or line breaks are added.

This is separate from the outreach steps above, which run before the due date; the confirmation goes out after the customer submits the form, including submissions that deny work. Use Save changes to apply it.

> **Where to find it:** Settings -> Automations -> Automated Outreach tab, the Confirmation email section

## Related guides

* [Configure the automated outreach sequence](/administration/settings/configure-the-automated-outreach-sequence.md)
* [Add or edit a pricebook item](/administration/settings/add-or-edit-a-pricebook-item.md)
* [Add the intake form to your website](/administration/settings/add-the-intake-form-to-your-website.md)
* [Automate task statuses with Task Automations](/administration/settings/automate-task-statuses-with-task-automations.md)
* [Build your intake form](/administration/settings/build-your-intake-form.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/administration/settings/set-the-confirmation-email-for-automated-outreach.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.