Zendesk Agent Performance Dashboard
Tracking individual agent performance helps you identify training needs, balance workloads, and recognize high performers. This guide covers which metrics to include in an agent performance dashboard and how to build one for Zendesk.
Why track agent performance
Agent-level metrics let you move from team averages to individual patterns. You can spot who needs help (consistently slow first reply time), who’s overloaded (tickets per agent far above average), and who delivers quality (reopen rate near zero). Without this view, coaching is guesswork.
For the broader dashboard picture, see support metrics dashboard.
Key metrics for agent performance
| Metric | What it shows | Where to find definition |
|---|---|---|
| Tickets handled | Volume / workload | tickets per agent |
| Avg first reply time | Speed to first response | first response time |
| Avg resolution time | Time to solve | resolution time |
| Reopen rate | Quality signal | reopen rate |
| CSAT (if available) | Customer feedback | csat |
Track these in business hours so agents working different shifts are compared fairly.
How to build it in Zendesk Explore
- Create a new report — Use the Support: Tickets dataset.
- Add columns — Assignee name, ticket count, median first reply time (business hours), median resolution time (business hours).
- Filter — Solved date in the period you want (last 7 days, last 30 days).
- Sort — By ticket count or by slowest first reply time depending on your goal.
For reopen rate, you may need a second report or a calculated metric (reopened tickets / solved tickets per assignee).
Common mistakes
- Comparing calendar hours across shifts — If one agent works weekends, their calendar-hour metrics look worse. Use business hours.
- Ignoring ticket complexity — An agent handling escalations will be slower than one handling password resets. Segment by tag or ticket type.
- Using averages instead of medians — One outlier ticket skews averages. Median is more representative for performance comparison.
- No trend — A snapshot shows today; a trend shows whether an agent is improving. Compare week-over-week.
What to do with agent metrics
- Coach, don’t punish — Use metrics to start conversations, not to blame. Ask why before assuming.
- Balance workload — If one agent has 2x the tickets, routing may be broken. Fix assignment rules.
- Recognize quality — Low reopen rate + fast resolution deserves acknowledgment.
- Identify training needs — Consistently slow on a specific tag? Knowledge gap for that issue type.
For weekly review cadence, see support ops metrics and weekly support ops review.
FAQ
Should I share agent metrics with the team?
Some teams share rankings; others keep it private. Either way, be transparent about what you track and why.
What’s a good benchmark for tickets per agent?
It depends on complexity. 10-20 tickets/day is common for email support; real-time chat is different. Track your own baseline and look for outliers.
How do I account for different roles (tier 1 vs tier 2)?
Segment by group or tag. Compare tier 1 agents to tier 1, tier 2 to tier 2.