> 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/see-and-browse-your-automated-outreach-the-automated-outreach-page.md).

# See and browse your automated outreach (the Automated Outreach page)

The Automated Outreach page lists the automated outreach your business has scheduled or sent. Each row is an outreach batch: the sequence of emails or texts that goes to a contact about upcoming work, such as a recurring service approval, a quote, an invoice, or a visit reminder.

Filter the list by status (Scheduled, In Progress, or Complete) and by the outreach type (Job Approval, Quote Outreach, Invoice Outreach, Visit Reminder, or Tech En Route). Each row shows an ID, who it's going to (Send To), the property and the asset groups it covers, and the send time (the next send for scheduled outreach, the last send for completed).

Click a row to open that specific automation, where you can see its steps and use Stop Automation to halt it. You can also ask Essential to find automations for a contact or account, or about the automation you're viewing.

> **Where to find it:** Automations, then the Automated Outreach page (route /automations/outreach)

## 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)
* [The kinds of automated outreach: Job Approval, Quote, Invoice, Visit Reminder, and Tech En Route](/field-operations/automated-outreach/the-kinds-of-automated-outreach-job-approval-quote-invoice-visit-reminder-and-tech-en-route.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/see-and-browse-your-automated-outreach-the-automated-outreach-page.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.