How to Set Realistic SLA Targets
SLA targets define what you promise customers—and what your team commits to delivering. Set them wrong, and you’re either overpromising (leading to burnout and breaches) or underpromising (leaving room for competitors).
What an SLA target covers
Common support SLA metrics:
| Metric | What it measures |
|---|---|
| First response time | Time to first reply |
| Resolution time | Time to solve |
| SLA compliance | % of tickets meeting target |
Most SLAs are tiered by priority:
| Priority | FRT target | Resolution target |
|---|---|---|
| Urgent | 1 hour | 4 hours |
| High | 4 hours | 24 hours |
| Normal | 8 hours | 48 hours |
| Low | 24 hours | 72 hours |
Step 1: Baseline your current performance
Before setting targets, know where you are:
- What’s your current median FRT and resolution time?
- What’s your p90 (90th percentile)?
- How does it vary by priority?
If your current median FRT is 6 hours, promising 1 hour is unrealistic without major changes.
Step 2: Understand customer expectations
SLAs should reflect what customers expect—not just what you can do:
- Survey customers or review feedback for expectations
- Check competitor SLAs if public
- Consider channel: chat expects minutes; email expects hours
A target that exceeds customer expectations is wasted effort. A target that misses them loses customers.
Step 3: Factor in capacity
Can you consistently hit the target with current staff?
Use capacity planning to estimate:
- Required agents to hit target
- Coverage hours needed
- Buffer for peaks
If hitting a 2-hour FRT requires 24/7 staffing you can’t afford, the target is unrealistic.
Step 4: Start conservative, then tighten
It’s better to overdeliver than to breach:
- Set initial targets at your current p75 (better than 75% of tickets today)
- Improve processes and efficiency
- Tighten targets as you improve
Example: Start with FRT < 6 hours, improve to < 4 hours, then < 2 hours over quarters.
Step 5: Define compliance threshold
100% compliance is usually impossible. Define acceptable compliance:
- Common: 90% or 95% of tickets meet target
- Aggressive: 98%+
- Realistic: Match your current state and improve
“95% of Normal priority tickets will receive a first response within 8 business hours” is clearer than “FRT < 8 hours.”
Step 6: Use business hours
Business hours reflect when your team actually works. A ticket created at 5 PM on Friday shouldn’t breach Monday morning.
Align SLA hours with support coverage. If you only work 9–5, don’t promise 24/7 response times.
Common mistakes
| Mistake | Why it’s a problem |
|---|---|
| Copying competitors | Their context is different |
| Promising what you can’t deliver | Leads to breaches and frustration |
| One SLA for all channels | Chat and email have different expectations |
| Not revisiting targets | What was right a year ago may not be now |
Example: Setting FRT target
Current state:
- Median FRT: 5 hours
- p90 FRT: 12 hours
- Compliance at 8-hour target: 75%
Analysis:
- 8 hours is too aggressive (25% breach)
- Median is 5 hours, so 6 hours is achievable
New target:
- FRT < 6 business hours, 90% compliance
- Review in 3 months; tighten if consistently exceeding
FAQ
Should I publish SLAs externally?
Only if you can consistently hit them. Internal targets can be aspirational; external promises must be reliable.
How often should I review SLAs?
Quarterly. Adjust based on performance, customer feedback, and business changes.
What if we keep breaching?
Either the target is wrong or capacity is insufficient. Diagnose before committing to the same target again.