First Response Time, Measured Properly
The metric customers feel most directly, and the one most often measured in a way that flatters the team.
Measure it honestly
First response time is the gap between the customer message arriving and a human reply going out.
An automatic acknowledgement is not a first response. Counting it is the most common way this metric gets gamed, usually accidentally, and it produces a dashboard that says twenty seconds while customers experience four hours.
Decide calendar hours or business hours and be consistent. Report the median alongside the average, because one weekend ticket ruins a mean.
The direct link to duplicate tickets
This is the connection worth internalising: your first response time sets your duplicate rate.
People contact you twice when the wait exceeds their patience. Reply within an hour and almost nobody writes again. Take six, and a meaningful share of customers will use the web form as well, then possibly chat.
So a slow first response doesn't just annoy customers, it manufactures extra tickets, which slows first response further. Teams sit in that loop for years.
Two exits: get faster, and merge the duplicates the wait already created. The second one you can do this week.
Practical ways to improve it
Frequently asked questions
Does an auto-reply count as a first response?+
No. Counting it makes your dashboard disagree with your customers, which is the worst kind of metric.
What is a good first response time?+
Under an hour is strong for business-hours support, under four hours is acceptable in most B2B contexts. What matters more is consistency: an occasional eight-hour reply damages trust more than a steady four.
Break the duplicate loop
Slow replies create duplicates, and duplicates slow replies. Merging them automatically stops the cycle from the other end.
Start free trial14-day free trial. No credit card required.