For the complete documentation index, see llms.txt. This page is also available as Markdown.

Agent Performance

The Agent Performance page shows individual and team performance: how much work each person gets through, how their logged time is spent, and how much of that time is productive. The KPI cards give team-level figures, the leader board compares agents side by side, and the charts show how hours are allocated and how many people are active. Everything is limited to the viewer's own team, so a team leader and an operations director see different numbers. It helps managers see who is delivering, understand why utilization or productivity moved, and spot time-recording problems.

Below is a full breakdown of the default graphs and data displays:

Work Items Resolved Per User

Work items resolved by team members, divided by team size. It adjusts throughput for team size so a large team isn't automatically judged more productive. It is currently limited to work that was Closed and Met, so it will read lower than the name suggests.

AHT in Hrs

The average hands-on time the team spends per work item, on completed work. It shows team-level effort per item.

% Utilization

Working time minus downtime and breaks, divided by working time. It answers "how much usable capacity did we have?"

% Productivity

Time logged against work plus time recorded outside Enate, divided by working time. It answers "how much of that capacity was actually used?" It can exceed 100%, which points to a time-recording problem rather than exceptional performance.

Active Users

Distinct people in the team with at least one logged activity. It gives context for the per-person figures and shows how much of the team was working.

Agent Leaderboard - Throughput

One row per agent showing work items resolved, utilization %, productivity % and SLA %. It puts volume, time usage and quality side by side. The table deliberately doesn't combine these into a single score, because high throughput at poor SLA is a very different situation from steadier throughput delivered on time.

Time Allocation (in Hrs) Breakdown

Stacks the team's logged hours by activity type (working, meetings, training, breaks, downtime, ad-hoc tasks, feedback and time outside Enate), viewable by month, week or day. It explains why utilization or productivity moved. A dip from a training week is a planned investment, whereas the same dip from downtime is a problem, and the headline percentages can't tell those apart.

Responsible Agents

Work items started in the period, split by status, for the viewer's direct and indirect reports. It gives a manager a "my team only" view of workload by status rather than every agent in the system.

Active Users

The number of people on the viewer's team who logged any activity, day by day. It tracks team engagement over time for the manager's own reporting line.

Last updated

Was this helpful?