> 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/field-operations/automated-outreach/the-kinds-of-automated-outreach-job-approval-quote-invoice-visit-reminder-and-tech-en-route.md).

# The kinds of automated outreach: Job Approval, Quote, Invoice, Visit Reminder, and Tech En Route

Essential sends several kinds of automated outreach, and you can filter the Automated Outreach list by kind using the pills above the table. Job Approval reaches out to a customer ahead of upcoming recurring services so they can approve the work and confirm property access.

A single Job Approval batch can cover multiple properties, asset groups, and offices when they all use the same brand. Properties assigned to different brands are split into separate batches, even when they use the same approval contact, so the approval email and form never mix brands. Quote Outreach sends a quote you've created to the customer for that property and follows up until they respond.

Invoice Outreach sends an invoice to the customer after work is complete and follows up if it goes unpaid. Visit Reminder notifies a contact about an upcoming scheduled visit, including its date, time, and the property address; a business can set up several reminders at different times ahead of the visit, and one batch carries all of them.

Tech En Route lets a customer know a technician is on the way to their visit; it includes the technician's name and, when available, an estimated arrival time. The real technician and ETA only exist once the tech taps to head out, so a preview of this kind shows placeholder values. Quote, invoice, visit-reminder, and en-route messages use the brand and office resolved from their property (falling back to the customer's office, then the main business profile).

Quote Outreach and Tech En Route only appear if your account has those features enabled, so you may not see every pill. Each kind follows its own sequence of email and text steps, which you can review on the individual outreach's detail page.

> **Where to find it:** Automated Outreach. The row of pills above the table filters by kind: Job Approval, Quote Outreach, Invoice Outreach, Visit Reminder, and Tech En Route.

## Related guides

* [Inside an automated outreach batch: the send steps, statuses, preview, and stopping it](/field-operations/automated-outreach/inside-an-automated-outreach-batch-the-send-steps-statuses-preview-and-stopping-it.md)
* [See and browse your automated outreach (the Automated Outreach page)](/field-operations/automated-outreach/see-and-browse-your-automated-outreach-the-automated-outreach-page.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/field-operations/automated-outreach/the-kinds-of-automated-outreach-job-approval-quote-invoice-visit-reminder-and-tech-en-route.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.