Average Tickets per Hour Calculator

The Average Tickets per Hour Calculator calculates average tickets processed per hour using total tickets and elapsed working time.

Average Tickets per Hour Calculator Explained

The calculator measures throughput, not speed for one ticket. It divides the number of tickets resolved by the hours worked. You can use team hours for a team rate, or agent hours for a per-agent rate. This metric helps you judge capacity, load balance, and hiring needs.

Behind the scenes, the method assumes stable working conditions during the period measured. If ticket arrivals and handling are random and independent, counts often follow a Poisson distribution. That assumption lets you add simple confidence bands around the estimated rate.

Use this number to benchmark days or teams with similar work. Compare like with like: the same ticket types, similar tools, and the same service policies. The calculator highlights the result, but your interpretation should include context and any known constraints.

Equations Used by the Average Tickets per Hour Calculator

The calculator converts ticket counts and time into a normalized hourly rate. It supports team totals, per-agent rates, and interval-weighted averages. When data volume is large, it can also estimate variability under common assumptions.

• Basic hourly rate: r = total tickets / total hours. Example: 120 tickets over 10 hours gives r = 12 tickets per hour.
• Per-agent rate: r_agent = total tickets / (number of agents × hours per agent).
• Weighted rate across intervals: r = sum(tickets_i) / sum(hours_i). This handles unequal time blocks safely.
• Active-time rate: r_active = total tickets / active hours, where active hours exclude breaks and outages.
• Approximate 95% confidence interval (Poisson): for N tickets in time T hours, rate = N/T, margin ≈ 1.96 × sqrt(N)/T.

These equations are simple but powerful. Use active time when you want a productivity view. Use total time when you want a capacity view. If the workload is highly variable, the Poisson interval suggests expected fluctuation around the observed rate.

How the Average Tickets per Hour Method Works

The method is straightforward: count resolved tickets and normalize by hours worked. It compresses varying shifts, breaks, and team sizes into a comparable rate. This makes it easy to see trends and test whether a change improved throughput.

• Track tickets resolved within a clear time window, such as one shift or one week.
• Measure total working hours in that window, including the number of agents involved.
• Divide tickets by hours to get the hourly rate.
• Repeat over several windows to create a baseline and spot trends.
• Check assumptions: similar ticket mix, stable tools, and consistent staffing patterns.

When ticket volume is random and independent over short intervals, counts often show a Poisson-like spread. That distribution implies the standard deviation is roughly the square root of the count. While not perfect, it is helpful for quick planning and risk bounds.

What You Need to Use the Average Tickets per Hour Calculator

Gather a few pieces of data before you start. You can calculate using either team totals or per-agent inputs. Decide whether breaks and system downtime should be excluded or included based on your goal.

• Total tickets resolved in the period.
• Total hours worked in the period, or start and end times.
• Number of agents who worked on those tickets (for per-agent rates).
• Breaks or idle time to exclude for an active-time rate (optional).
• Time window definition, such as shift, day, or week.
• Any exclusions, for example, escalations or automated resolutions.

Typical ranges vary widely by industry. If you enter zero hours, the rate is undefined. If tickets are zero, the rate is zero. Very small samples can produce unstable rates and wide intervals. Consider aggregating across several days to reduce noise.

How to Use the Average Tickets per Hour Calculator (Steps)

Here’s a concise overview before we dive into the key points:

1. Select the time window you want to analyze, such as a single shift.
2. Count how many tickets were resolved during that window.
3. Total the hours worked for all agents during the same window.
4. Decide whether to exclude breaks to compute active-time hours.
5. Enter tickets, hours, and agent count into the Calculator.
6. Review the hourly rate and, if shown, the confidence interval.

These points provide quick orientation—use them alongside the full explanations in this page.

Example Scenarios

An IT service desk has 5 agents working an 8-hour shift. They resolve 320 tickets. Team hours equal 5 × 8 = 40 hours. Team rate per hour is 320 ÷ 8 = 40 tickets per hour. Per-agent rate is 320 ÷ 40 = 8 tickets per agent per hour. Assuming a Poisson distribution with N = 320 and T = 8 hours, the 95% margin is 1.96 × sqrt(320)/8 ≈ 1.39, so the team rate is about 40 ± 1.39. What this means: The desk can expect roughly 38.6 to 41.4 tickets per hour in similar conditions.

A retail support team measures a busy 3-hour window and resolves 90 tickets with 3 agents. Total agent hours are 3 × 3 = 9. Per-agent rate is 90 ÷ 9 = 10 per agent per hour. If they run another 5-hour window with 110 tickets and 2 agents, agent hours are 10, so per-agent rate is 11. A weighted rate across the two windows is (90 + 110) ÷ (3 + 5) hours of window time for team rate, or use agent hours for a per-agent comparison: (90 + 110) ÷ (9 + 10) = 10.53 per agent per hour. What this means: Performance improved slightly in the second window after normalizing for hours and staffing.

Limits of the Average Tickets per Hour Approach

This metric simplifies complex work into one number. That clarity is useful, but it hides variation, queue length, and ticket complexity. Interpret the result with your context and known constraints.

• Non-stationary demand can bias rates; peaks and lulls get averaged away.
• Ticket mix matters; easy and hard tickets inflate or deflate rates.
• Batch closures or automation spikes can distort a single window.
• Very small samples create large uncertainty in the estimate.
• Backlog health, wait times, and quality are not reflected in the rate.

Use this method alongside other indicators. Combine it with first-contact resolution, backlog age, and customer satisfaction to get a balanced view. Check assumptions regularly and update your baseline when processes change.

Units & Conversions

Tickets per hour is the standard unit, but your data might be in minutes, shifts, or days. Convert consistently before comparing teams. Clear units prevent errors when you roll up results across multiple schedules.

Read the table left to right. Identify your source unit, apply the conversion, and check that all compared teams use the same hour definition, including whether breaks are included.

Common Issues & Fixes

Several pitfalls can skew the rate. These problems are common when combining data from multiple teams or tools. Use the following quick checks before trusting the result.

• Zero or near-zero hours: verify window boundaries and time zone settings.
• Double counting: ensure tickets are only counted at final resolution.
• Mixed ticket types: filter to a comparable category or compute separate rates.
• Partial shifts: include only hours when agents were on duty for those tickets.
• Automation impact: tag and separate auto-closed tickets when relevant.

Fix inputs first, then compute the rate. If variability is high, increase the sample size or group by similar hours, such as only weekdays or only peak hours. Compare the result with your historical baseline to sanity-check the outcome.

FAQ about Average Tickets per Hour Calculator

Should I measure tickets created or tickets resolved?

Measure tickets resolved when you want throughput and productivity. Measure tickets created when you want demand. Use both to see whether capacity matches demand over time.

How much data do I need for a stable rate?

A full week of typical operations is a good start. When counts are low, the rate will swing. Aggregating across several weeks gives a steadier baseline.

Do I include tickets that were escalated or reopened?

Define clear rules before counting. Many teams exclude escalations and count the final resolver only. Reopened tickets can be counted once at their final closure.

How do I compare teams of different sizes?

Use per-agent rates by dividing total tickets by agent-hours. This normalizes team size and shift length, making the comparison fair.

Key Terms in Average Tickets per Hour

Average tickets per hour

The normalized count of tickets resolved per hour over a defined window. It summarizes throughput for a team or an individual.

Throughput

The volume of work completed per unit time. In support operations, it often equals tickets resolved per hour.

Arrival rate

The number of new tickets created per unit time. It helps estimate demand and compare it with throughput.

Service rate

The rate at which agents complete tickets. It depends on staffing, tools, process, and the mix of ticket complexity.

Occupancy

The fraction of time agents spend on active work. Higher occupancy can raise throughput but may increase wait times or burnout.

Weighted average

An average that accounts for different interval lengths by summing totals and dividing by total time. It avoids bias from unequal windows.

Poisson distribution

A probability distribution for counts of random events in a fixed interval. It often models ticket counts and supports simple uncertainty estimates.

Confidence interval

A range that likely contains the true rate, given assumptions. Wider intervals indicate more uncertainty in the estimate.

References

Here’s a concise overview before we dive into the key points:

• Poisson distribution overview
• Little’s Law and its implications for throughput
• Zendesk: Essential support metrics and how to use them
• Atlassian: Service desk metrics to track
• Queueing Theory Basics: Arrivals, service, and utilization
• Freshdesk: Ticketing system metrics and best practices

These points provide quick orientation—use them alongside the full explanations in this page.