How to Staff a Support Team Using Zendesk Data

Staffing decisions in support are usually based on gut feel, headcount budgets, or panic (“we’re drowning — hire someone”). None of those methods use the data you already have in Zendesk.

Your ticket data contains the signals you need to staff intelligently: volume trends, peak hour patterns, agent capacity, and the gap between inflow and outflow. This post shows how to extract those signals and use them to make staffing decisions you can defend.

Why data-driven staffing matters

Under-staffing and over-staffing both cost money. Under-staffing drives up first reply time, grows backlog, causes SLA breaches, and burns out agents. Over-staffing wastes budget and underutilizes agents, which can also demotivate the team.

The goal is not perfection — it is directional accuracy. If you can answer “How many tickets do we expect next week, and how many agents do we need to handle them within SLA?” you are already better off than most support teams.

Step 1: Understand your volume pattern

Pull ticket volume from Zendesk for the last 8–12 weeks, broken down by:

Day of week — Most support teams see predictable patterns. Monday is often the highest volume day. Weekends are typically lower (unless you serve ecommerce or global customers).
Hour of day — Use the peak hours report to identify when tickets cluster. This is critical for shift planning.
Channel — Email, chat, messaging, and phone have different handling characteristics. An agent can handle 3–5 concurrent chats but only one phone call. Volume by channel determines the staffing model, not just the headcount.

Look for patterns, not individual days. A single spike from a product outage is noise. A consistent Monday morning surge is signal.

For trend analysis, see Zendesk ticket volume report and forecast support ticket volume.

Step 2: Calculate agent capacity

Agent capacity is not “how many tickets can an agent close per day.” It is a function of several variables:

Tickets per agent per day

Start with your current data. Pull tickets per agent for the last 4–8 weeks. Use median, not average — a few outlier days will skew the mean.

A typical range for email support is 20–40 tickets per agent per day, depending on complexity. For live chat, it is usually higher per session but lower per hour because of concurrency and wait time.

Average handle time

Average handle time (AHT) is the time an agent spends actively working a ticket: reading, researching, writing a reply, updating fields. Multiply AHT by expected ticket volume to estimate total agent-hours needed.

Example: - Weekly volume: 500 tickets - Average handle time: 12 minutes per ticket - Total agent-hours needed: 500 × 12 / 60 = 100 hours - Productive hours per agent per week (accounting for meetings, breaks, admin): ~30 hours - Agents needed: 100 / 30 ≈ 3.3 → 4 agents

This is a rough calculation. Adjust for concurrency (chat agents handle multiple conversations), ticket complexity by tag, and the mix of channels.

Utilization target

Agent utilization — the proportion of time agents spend on ticket work versus total available time — should not be 100%. That leaves no buffer for volume spikes, training, or process improvement. A healthy target is 70–80% utilization. If your team is consistently above 85%, they are stretched too thin, and FRT or quality will suffer.

See Zendesk agent utilization report for how to track this.

Step 3: Map volume to shifts

Once you know volume patterns and agent capacity, map them together:

Identify your coverage window. When do you commit to responding? If your SLA says 4-hour FRT during business hours (9am–6pm), you need enough agents online during those hours.
Overlay volume on schedule. Plot hourly ticket volume on a timeline and overlay your current shift schedule. Look for gaps: hours where volume exceeds capacity and hours where agents are underutilized.
Adjust shifts to match demand. If 40% of tickets arrive between 9am and 12pm but you staff evenly throughout the day, you are under-staffed in the morning and over-staffed in the afternoon. Stagger shifts or add a morning-heavy schedule.

For teams considering extended hours, see the follow-the-sun model: distribute shifts across time zones so customers get coverage without any single team working overnight.

Step 4: Use the inflow/outflow gap

The ticket inflow vs outflow report is the clearest signal for staffing decisions:

Inflow > Outflow for multiple weeks → Backlog is growing. You either need more capacity or better efficiency.
Outflow > Inflow → Backlog is shrinking. Your team is keeping up. If utilization is low, you may be over-staffed.
Inflow ≈ Outflow but backlog is growing → Tickets are getting stuck in pending or on-hold states. The problem is process, not headcount. Check time in status to find where work stalls.

This metric is more useful than ticket volume alone because it measures whether you are keeping up, not just how busy you are.

Step 5: Plan for variance

Staffing to the average guarantees you are under-staffed half the time. Build in buffer:

Seasonal patterns — Retail teams need more agents during holiday season. B2B teams may see surges after product launches or quarterly renewals. Pull 12 months of data to identify patterns. See seasonal support planning with data.
Growth trend — If ticket volume is growing 5% per month, your staffing plan should account for where volume will be in 3–6 months, not where it is today.
Incident buffer — Product outages, security incidents, and pricing changes create volume spikes. Having one agent’s worth of buffer capacity means these spikes do not wreck your SLA.

Step 6: Justify headcount to leadership

Data-driven staffing makes headcount requests defensible. Instead of “we feel overwhelmed,” present:

Current state: “Our median FRT is 6.2 hours. SLA target is 4 hours. We breach SLA on 23% of tickets.” Include trend — is it getting worse?
Root cause: “Ticket volume is 480/week. At our current AHT and utilization, we have capacity for 420. The gap produces a growing backlog of ~60 tickets per week.”
Impact: “Backlog growth correlates with rising reopen rate (up 3 points over 8 weeks) and declining CSAT (down 4 points). Slow FRT is creating follow-up tickets that inflate volume further.”
Ask: “Adding one agent at our current AHT closes the gap and brings FRT within SLA. Cost: one headcount. Risk of not acting: continued SLA breaches and CSAT erosion.”

This is harder to say no to than “we need more people.” For more on framing, see support metrics for executive reporting and how to explain a bad support week to leadership.

The metrics that power staffing decisions

Metric	What it tells you for staffing	Where to track
Ticket volume (daily, weekly)	Demand level and trend	Volume report
Peak hours	When demand concentrates	Peak hours report
Tickets per agent	Individual capacity	Tickets per agent report
Average handle time	Work per ticket	AHT guide
Agent utilization	Capacity headroom	Utilization report
Inflow vs outflow	Are we keeping up?	Inflow vs outflow report
Backlog	Accumulated debt	Backlog dashboard
First reply time	Customer-facing impact of capacity	FRT report

Common staffing mistakes

Staffing to average volume — You will be under-staffed during every peak. Use the 75th percentile of daily volume as your capacity target, not the median.
Ignoring channel mix — A chat agent handles work differently than an email agent. Do not treat capacity as interchangeable unless agents are truly omnichannel.
Not accounting for non-ticket work — Agents attend meetings, do training, write documentation, and take breaks. Productive ticket time is typically 60–75% of scheduled time. See Zendesk solved tickets per agent hour for a realistic measure.
Reactive hiring only — By the time you feel overwhelmed, backlog and FRT have already deteriorated for weeks. Build a quarterly staffing review using the metrics above so you can spot capacity gaps before they hit customers.
Using tickets closed as the only productivity metric — Agents who close many tickets quickly may be sacrificing quality. Pair tickets per agent with reopen rate and CSAT to get the full picture.

Key takeaway

Your Zendesk data already contains the answers to your staffing questions. Pull volume trends, calculate agent capacity, map demand to shifts, and track the inflow/outflow gap. When you present staffing requests backed by data — volume, AHT, utilization, SLA impact — you turn a budget conversation into an operational one.

For the dashboards that make this analysis easy, start with the support metrics dashboard hub and the support team capacity planning guide.

See your staffing signals from Zendesk in minutes — start free