Agent Onboarding: Metrics to Track Progress
New support agents don’t perform at full speed on day one. Onboarding is a ramp. Tracking the right metrics helps you know when someone is ready—and where they need more support.
Why track onboarding metrics
- Identify struggles early — Catch training gaps before they become problems.
- Set realistic expectations — New agents shouldn’t be compared to veterans on day one.
- Improve onboarding — If everyone struggles with the same thing, fix the training.
- Protect customers — Ensure quality before full workload.
Key metrics for onboarding
1. Tickets handled (volume ramp)
Track tickets per day or week. New agents start slow and ramp up.
| Week | Tickets/day (typical ramp) |
|---|---|
| 1 | 2–5 |
| 2 | 5–10 |
| 4 | 10–15 |
| 8 | Team average |
If someone isn’t ramping, investigate: training gap? Confidence issue? Workflow confusion?
2. Handle time
Handle time is typically longer for new agents—they’re learning.
Track median handle time and compare to team average. New agents might be 2x slower initially; that’s normal.
3. First reply time (agent-attributed)
First reply time shows how fast the agent responds once assigned.
Slow FRT early is expected. If it’s still slow after 4 weeks, investigate workflow or confidence.
4. Reopen rate
Reopen rate is a quality signal. New agents may have higher reopens if they’re closing tickets prematurely or giving wrong answers.
Target: New agent reopen rate should approach team average by week 6–8.
5. CSAT
CSAT is the ultimate quality metric. New agents may have lower CSAT initially.
Watch for:
- CSAT improving over time (good)
- CSAT flat or declining (needs intervention)
6. Escalation rate
How often does the new agent escalate to seniors? High escalation early is expected; it should decline over time.
If escalation stays high after 4–6 weeks, they may need more training on those topics.
Setting onboarding benchmarks
Create a ramp chart for your team:
| Week | Tickets/day | Handle time | Reopen rate | Escalation |
|---|---|---|---|---|
| 1–2 | 5 | 2x team avg | < 10% | High |
| 3–4 | 10 | 1.5x | < 8% | Medium |
| 5–8 | 15 | 1.2x | < 6% | Low |
| 8+ | Team avg | Team avg | Team avg | Team avg |
Adjust based on your team’s data.
How to use onboarding metrics
1. Weekly check-ins
Review metrics in 1:1s. Don’t punish; diagnose.
“I see your reopen rate is 12%—let’s look at a few tickets and see what’s happening.”
2. Identify training gaps
If multiple new hires struggle with the same tag or issue type, the training is missing something.
3. Know when to graduate
Define “full ramp” based on metrics:
- Handling team average tickets/day
- Handle time within 20% of team
- Reopen rate and CSAT at team level
Until then, keep lighter workload and more oversight.
4. Celebrate progress
Onboarding is hard. Acknowledge when someone crosses a milestone.
Common mistakes
| Mistake | Fix |
|---|---|
| Comparing new agents to veterans | Use ramp benchmarks, not team average |
| Not tracking at all | You can’t improve what you don’t measure |
| Punishing slow ramp | Diagnose and support instead |
| Extending onboarding indefinitely | Set clear milestones and timelines |
FAQ
How long should onboarding take?
Typically 4–8 weeks to reach team average, depending on product complexity. Some roles take 12 weeks.
Should new agents handle all ticket types?
No. Start with easier issues; add complexity over time. This builds confidence and reduces risk.
What if someone isn’t ramping?
First, diagnose: training gap? Wrong hire? Personal issues? Intervene early; don’t wait months.