> 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/francais/rapports/apercu-des-performances-operationnelles/communications.md).

# Communications

#### Communications

Trafic d'e-mails entrants et sortants au sein de l'entreprise : volumes, tendances et processus à l'origine de la plus grande partie de la correspondance.

<figure><img src="https://675373381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MWYnDNwe3Cuo4zlGbs5-2056118458%2Fuploads%2Fk5SZpUGU321enjOfiBJN%2Fimage.png?alt=media&amp;token=5fd2d382-acc4-4b3b-95c6-aa7d980f6867" alt=""><figcaption><p>Onglet « Communications ».</p></figcaption></figure>

**Fiches d'indicateurs clés de performance (KPI)**

* **E-mails entrants :** e-mails reçus de la part de clients ou de tiers.
* **E-mails sortants :** e-mails envoyés.
* **E-mails de remerciement :** e-mails automatiques de clôture ou d'accusé de réception envoyés une fois l'activité résolue.
* **E-mails non traités :** e-mails reçus mais qui ne sont pas encore associés à une activité ou pour lesquels aucune action n'a été entreprise. Un nombre croissant de ces e-mails indique un retard dans la communication.

**Éléments visuels**

* **Tendance des volumes –** Entrants vs sortants – Évolution des volumes entrants et sortants au fil du temps, chaque type étant représenté sur une ligne distincte ; détail par mois → semaine → jour.
* **Par processus –** Volume d'e-mails par processus, chaque barre étant fractionnée par type d'e-mail – permet d'identifier les processus générant le plus de correspondance.


---

# 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://docs.enate.net/enate-help/francais/rapports/apercu-des-performances-operationnelles/communications.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.
