> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/work-manager/work-manager-2021.1/reports/operations-performance-overview/communications.md).

# Communications

#### Communications

Email traffic in and out of the operation - volumes, trends and which processes drive the most correspondence.

<figure><img src="/files/FhkGaF9VWeNNaZm5njXO" alt=""><figcaption></figcaption></figure>

&#x20;                                                            *Communications tab.*

**KPI cards**

* **Incoming Emails -** emails received from customers or external parties.
* **Outgoing Emails -** emails sent out.
* **Thank You Emails -** automated closure/acknowledgement emails sent when work is resolved.
* **Unhandled Emails -** emails received but not yet linked to a work item or actioned. A growing number signals a communication backlog.

**Visuals**

* **Volume Trend - Incoming vs Outgoing -** incoming vs outgoing volumes over time, each type on its own line; drills month → week → day.
* **By Process -** email volume per process, each bar split by email type - shows which processes generate the most correspondence.

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enate.net/enate-help/work-manager/work-manager-2021.1/reports/operations-performance-overview/communications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.