How to Build a Support Team Scorecard
A support team scorecard consolidates your most important KPIs into a single view. Instead of jumping between reports, you see volume, speed, quality, and efficiency at a glance. This guide shows you how to build one.
What goes on a support scorecard
A good scorecard has 5–8 metrics organized by category. More than that and it becomes noise. Less, and you miss something important.
| Category | Metrics | Glossary |
|---|---|---|
| Volume | New tickets, ticket inflow, backlog | ticket volume |
| Speed | First reply time, resolution time | |
| Quality | Reopen rate, CSAT | |
| Efficiency | Tickets per agent, touches per ticket |
Start with these. Add or remove based on what your team can actually influence.
Step 1: Pick your metrics
List what you care about. For most teams:
- Volume: How much work is coming in? Trend up or down?
- Speed: Are we responding and resolving fast enough?
- Quality: Are customers satisfied? Are tickets reopening?
- Efficiency: Are we doing more with the same team?
Don’t add a metric unless you’ll act on it. If CSAT isn’t actionable (low response rate, unclear feedback), leave it off until you fix the survey process.
Step 2: Define targets
Each metric needs a target or baseline. Targets can be:
- Internal baseline — Your own average over the last 90 days.
- SLA — Contractual or published response times.
- Industry benchmark — Use cautiously; your context is different.
Example: Median first reply time target = 4 business hours. Reopen rate target = < 5%.
Step 3: Choose the time frame
Weekly is ideal for ops cadence. Monthly for executive reporting. Daily is too noisy for most teams.
For weekly reviews, see weekly support ops review.
Step 4: Build the view
Options:
- Zendesk Explore dashboard — Native, but limited customization. Good for basics.
- Spreadsheet — Export data weekly; manual but flexible.
- Third-party tool — Auto-updated, drill-down, no exports.
For a template, see support dashboard template.
Step 5: Review and iterate
Review the scorecard weekly. Ask:
- What changed vs last week?
- Why did it change?
- What will we do about it?
If a metric never changes or never triggers action, remove it.
Common mistakes
- Too many metrics — 15 metrics means no one reads it. Focus.
- No targets — Numbers without context don’t help. “Is 6 hours good?” depends on your target.
- No trends — A single snapshot misses direction. Show week-over-week or month-over-month.
- No ownership — Who reviews this scorecard? When? Make it part of a meeting.
Example scorecard layout
| Metric | This week | Last week | Target | Status |
|---|---|---|---|---|
| New tickets | 312 | 298 | — | ↑ |
| Open backlog | 45 | 52 | < 50 | ✓ |
| Median FRT (biz hrs) | 3.2h | 4.1h | < 4h | ✓ |
| Median resolution (biz hrs) | 18h | 22h | < 24h | ✓ |
| Reopen rate | 6% | 5% | < 5% | ✗ |
| CSAT | 87% | 88% | > 85% | ✓ |
Simple. Scannable. Actionable.
FAQ
How often should I update the scorecard?
Weekly for ops; monthly for leadership. Automate if possible.
What if we don’t have CSAT data?
Use reopen rate and touches per ticket as quality proxies until you set up CSAT.
Should agents see the scorecard?
Yes. Transparency builds ownership. Share it in your weekly standup or team channel.