A customer sends a message on Monday morning and hears back on Wednesday. Whatever happened in between, the length of that gap is what first response time records. It starts when the message arrives, not when somebody opens it.
It is the average wait between a customer’s message and the first reply a member of your team sends to it. Replies to the same thread are not counted, and neither is anything else that happens on the thread.
What counts as a first response
One event stops the clock: a reply going out to the customer. Internal work the customer cannot see does not count.
| Action | Stops the first response clock |
|---|---|
| A reply sent to the customer | Yes |
| Assigning an owner | No |
| Changing the status | No |
| Adding an internal note | No |
| Snoozing the thread, or a rule that files and tags | No |
Help Scout states those rules for its own reports, where switching the status, assigning, tagging and adding notes do not affect response time, according to its metric definitions. The same page records the case teams argue about, where a customer writes twice before anyone answers and the wait is counted from the first message.
The clock starts when the customer writes. If you email them first and they reply, nothing has been answered yet, so the wait runs from their reply.
The average hides the one that got away
The average is the wrong shape for a wait. One thread answered in four minutes and one nobody touched for nine days average out to a number that describes neither customer.
| Reading | What it shows | What it hides |
|---|---|---|
| Mean | Roughly how the week went | One abandoned thread, and the customer in it |
| Median | The wait a typical customer had | The tail, which is the part that costs you the account |
| Longest wait, and how many are still waiting | The customer waiting right now | Nothing that matters here |
For a team of five, the third row is the one to read. The decision worth catching is the thread no one owns.
How an automated acknowledgement distorts it
A system can answer before a person does. The customer gets a receipt, a dashboard records a reply, and the clock stops with nobody having read the message. The common version is the out of office automatic reply that fires at a sender, and the same shape covers order confirmations and “we have received your request” mail.
A number that counts those replies can only go one way. It falls and the report looks calm. The distortion runs the other way too: a reply that leaves outside the tool, or from an address it does not recognise, is not always recorded, so a fast answer can be missing from the number meant to describe it.
| What happened | What gets recorded | First response time |
|---|---|---|
| An acknowledgement goes out in seconds, a person answers two days later | The acknowledgement | Seconds |
| A person answers in an hour, and the reply is logged outside the tool | Nothing | Not counted |
| A person answers two days later, and that is the first thing recorded | The reply | Two days |
Decide which of those three you are measuring. If you want the customer’s experience, measure to the first reply a person wrote.
Why it is not resolution time or handle time
| Metric | Starts | Stops | Who controls it | What it tells you |
|---|---|---|---|---|
| First response time | The customer’s message arrives | The team’s first reply goes out | Your team | How long a customer waited to be heard |
| Resolution time | The thread starts | The thread is closed | Your team, the customer and the fix | How long the whole thing took |
| Handle time | You open the thread | You press Send | The person replying | How long the writing took |
Resolution time is the honest number for the customer and the worst one to set a target on, because it includes waiting on a reply from them and waiting on the fix. Handle time is a writing measurement, and pushing it down teaches people to send shorter replies. First response time is the only one of the three the team fully controls, which is why it gets gamed.
What a small team should do with it
On a team where the person replying also fixes the bug, a fast first response buys less than it looks like. The clock that matters to the customer runs until the fix ships, and an acknowledgement does not shorten it. Treat first response time as one commitment rather than a target to beat.
- Pick one promise and keep it. “Every message gets a reply from a person within one working day” is a promise a five-person team can hold. A two-hour target is one you break on your best day.
- Read the oldest unanswered thread instead of the average. It says who is waiting right now.
- Stop the clock at the human reply. Count from the customer’s message to the first reply a person wrote, and keep acknowledgements out of it.
- Watch for the wrong win. If the response time looks good and customers still open with “any update?”, the problem was never speed. Nobody was working the fix.
Where it lives in a shared inbox
On a shared address nobody owns a reply until something shows an owner. The failure the metric is meant to catch is usually a thread four people assumed someone else had answered.
Chirp is a shared inbox for small software teams that track their work in Linear. Press i in a thread to link it
to an issue, create one, or search for the one that already exists. Snooze the thread until the issue is done, and it
comes back with a reply drafted for you that names the issue. No rule in Chirp can send mail, so there is no automatic
acknowledgement to inflate anything.
The Issues view (g i) sorts linked issues by how many customers are waiting, which is closer to the third reading
above than to an average. Response-time reports come with the ticketing model, and
shared inbox vs help desk covers which one your team needs.
FAQ
What is a good first response time? It is the one you can keep with everybody answering between other work. Decide that number for your team rather than adopting a figure from a vendor page.
Is first response time the same as resolution time? No. First response time stops at your team’s first reply. Resolution time runs until the thread is closed, so it also includes the wait on the customer and on whatever change fixes the problem.
Does an auto-reply count as a first response? In a report it often does, because the tool records a reply going out. For the customer it does not, since nobody has read the message. Exclude acknowledgements from the number you track.
What is the difference between first response time and handle time? Handle time measures one person writing one reply, from opening the thread to pressing Send. First response time measures how long the customer waited before that reply arrived.
Next step
If you are deciding where the replies should live, what a shared inbox is covers the category and the arrangements that get mistaken for it. Decide what counts as a reply before you measure it.
