An SLA, or service level agreement, is a promise about how quickly you’ll respond to and resolve customer requests. Even if you never put one in a contract, setting internal SLA targets is one of the highest-leverage things a small support team can do, because it turns a vague goal (“be responsive”) into a number you can manage against.
There are two targets that matter, and conflating them is the most common mistake.
First response time
First response time is how long the customer waits before a human acknowledges their request. Not a resolution, just a real reply from a real person (“Got it, looking into this now”).
This is the metric customers feel most. A fast first response sets the tone even when the fix takes a while. A good starting target for a small business is under 4 business hours; high-touch teams aim for under 1.
The word “business” is doing real work there. If you promise a 4-hour response but someone emails at 9pm Friday, measuring against the clock isn’t fair to your team or honest with the customer. Good SLA tracking counts only your operating hours.
Resolution time
Resolution time is how long from the customer’s first message until the issue is actually closed. This is lumpier: a password reset resolves in minutes, a billing dispute might take days.
Because resolution time varies so much by issue type, don’t hold every ticket to one number. A common approach is to set resolution targets by priority: urgent in hours, normal within a day or two, low whenever it’s reasonable.
Why you need both
First response time protects the experience; resolution time protects the outcome. A team can have great response times and terrible resolution times (fast “we’re on it!” followed by silence), or the reverse (everything gets fixed eventually, but customers feel ignored). Tracking both keeps either failure mode from hiding.
Setting targets you can hit
- Measure before you commit. Look at your current response and resolution times for a month. Set targets slightly tighter than your honest average, not aspirational fantasy.
- Tie targets to priority. One number for everything is either too loose for urgent issues or impossible for complex ones.
- Count business hours only, anchored to your actual schedule and time zone.
- Review breaches, don’t just count them. A breached SLA is a prompt to ask “what happened here?” not a stick to beat the team with.
Where the numbers come from
You can’t manage what you don’t measure. A help desk stamps each ticket with when it arrived, when it got its first response, and when it closed, then flags the ones at risk of breaching. That turns SLAs from a spreadsheet exercise into something you glance at daily.
teckyz tracks first-response and resolution targets per company and per department, counts only your operating hours, and flags tickets before they breach. Learn more or try it free.
For the metrics you report to leadership rather than manage day to day, see our piece on CSAT, CES, and NPS.