Tickets per Agent

Tickets per Agent measures the number of support tickets each agent handles over a given time period. It’s a fundamental metric for understanding workload distribution and individual productivity.

Why Tickets per Agent Matters

Tracking this metric helps you:

• Balance workloads — Ensure fair distribution across team members
• Identify capacity issues — Spot overloaded or underutilized agents
• Measure productivity — Track output (with quality considerations)
• Plan staffing — Understand how many tickets your team can handle

How to Calculate Tickets per Agent

Tickets per Agent = Total Tickets Handled / Number of Agents

For individual agents:

Individual Tickets = Count of tickets assigned to that agent in the period

Consider tracking:

• Solved tickets — Fully resolved by the agent
• Touched tickets — Any tickets the agent worked on
• Assigned tickets — Currently in the agent’s queue

Interpreting the Metric

High tickets per agent might indicate:

• High productivity (positive)
• Rushed work affecting quality (negative)
• Simple ticket types (context-dependent)

Low tickets per agent might indicate:

• Complex issues requiring more time (acceptable)
• Underutilization (needs investigation)
• Training or onboarding period (expected)

Balancing Quantity and Quality

Never optimize for tickets per agent alone. Always pair with:

• Quality metrics — CSAT, reopen rate, FCR
• Complexity factors — Ticket difficulty varies
• Time metrics — Resolution time, handle time

Improving Workload Distribution

• Smart routing — Distribute tickets based on capacity and skills
• Real-time monitoring — Track queue sizes across agents
• Capacity planning — Match staffing to volume patterns
• Specialization — Route complex tickets to experts

Agent Workload in TicketBoard

TicketBoard provides clear visibility into agent workload:

• Assignee volume charts showing tickets per agent
• Comparison across team members
• Trend analysis over time