> 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/agent-performance.md).

# Agent Performance

#### Agent Performance

Throughput, handling time, utilisation and how each agent spends their day. As noted under *Row-Level Security*, this tab is scoped to the logged-in manager's reporting line (i.e. you see your own team, not the wider operation).

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

&#x20;                                                            *Agent Performance tab.*

**KPI cards**

* **Work Items Resolved Per User -** average items resolved per agent across the team - a throughput-per-head measure.
* **AHT in Hrs -** average handling time per item for the team.
* **% Utilisation -** share of tracked working hours that was productive (not break or downtime).
* **% Productivity -** share of the working day spent on actual work, including time logged in Enate and related work done outside the system.

**Visuals**

* **Agent Leaderboard -** per-agent table of items resolved, utilisation %, productivity %, SLA % and AHT.
* **Time Allocation Breakdown -** stacked columns showing how time splits across Working, Ad Hoc, Break, Downtime, Outside Enate, Feedback, Meeting and Training. Drills month → week → day.
* **Responsible Agents -** agents ranked by how many work items they picked up.
* **Active Users Trend -** daily active agents over time; dips can indicate leave, absence or access issues.


---

# 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/agent-performance.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.
