> For the complete documentation index, see [llms.txt](https://docs.mluvii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mluvii.com/en/for-administrators/company-management/operator-metrics.md).

# Operator metrics

If you have permission to view operator metrics, you may have noticed that a new **Operator Metrics** section has appeared at the top of the main dashboard.

The operator metrics are intended to track the statistics and performance of individual operators. For example, **you can track in detail the evolution of sessions and operator states over time, session length or ACW length.**

{% hint style="warning" %}
*The section displays data not older than 3 months only.*
{% endhint %}

{% hint style="info" %}
*The metrics are available to any user who has been granted the **"View Operator Metrics"** permission.*
{% endhint %}

{% hint style="info" %}
*If your operators are calling clients (outgoing calls), you can find the BCW (Before Call Work) status in the metrics. The status starts when you click the "Call" button and ends when the call starts dialing.*
{% endhint %}


---

# 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.mluvii.com/en/for-administrators/company-management/operator-metrics.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.