First response time (FRT) is the average time between when a customer contacts your team and when a human agent sends the first reply. You calculate it as total time to first response divided by the number of tickets, measured in business hours and excluding automated acknowledgments. A good FRT depends on the channel: under an hour is strong for email, under a minute for live chat, and under an hour for social media.
It is the metric customers feel before they feel anything else about your support. Resolution can take a while and still leave someone satisfied, but silence after sending a message is the fastest way to make a customer feel ignored. That is why first response time sits at the top of nearly every support dashboard, and why it is worth measuring properly rather than reading off a tool that counts your auto-reply as a response. This guide covers what FRT is, how to calculate it without fooling yourself, what a good number looks like in 2026, how it differs from resolution time, and the seven changes that actually bring it down.
What is first response time?
First response time is the elapsed time from a customer's first message to the first genuine reply from a support agent. It measures responsiveness, not resolution: it tells you how quickly a person acknowledges and engages with the problem, not how long the whole issue takes to close. A customer who gets a thoughtful first reply in ten minutes feels handled even if the fix takes two days, while a customer who waits a day for any human contact feels ignored no matter how fast the eventual solution arrives.
The word that does the work in that definition is "genuine." An automated message that says "Thanks, we got your request, ticket 4471 is open" is useful, but it is not a first response, and counting it as one is the most common way teams flatter their own numbers. The FRT clock should stop only when a person, or an AI agent actually answering the question, engages with the specific issue the customer raised.
How do you calculate first response time?
For a single ticket, first response time is the timestamp of the first human reply minus the timestamp of the customer's first message. To get your team's headline number, you average across tickets over a period.
Average FRT = total time to first response across all tickets / number of tickets. That formula is simple, but two decisions determine whether the result is honest.
Measure in business hours, not calendar hours. If your team works 8am to 7pm and a message arrives at 10pm, answered at 8:05am the next morning, the FRT for that ticket is five minutes, not ten hours. Counting the overnight gap punishes the team for a clock that was never running and produces a number nobody can act on. Configure your help desk to pause the timer outside your support hours, or your FRT will mostly measure your time zone rather than your responsiveness. Where you promise coverage 24/7, calendar hours and business hours are the same thing, and the distinction disappears.
Watch the average versus the median. A handful of tickets that sat for two days will drag the average up and make a fast team look slow. The median, the middle value where half of tickets were answered faster and half slower, is often the more honest read of a typical customer's experience. Report both: the median tells you what most customers feel, and the average tells you whether a long tail of neglected tickets is hiding in the queue.
What is a good first response time?
A good first response time is entirely channel-dependent, because a customer waiting on live chat expects a reply in seconds while a customer who sent an email tolerates hours. Setting one blended target across every channel is the classic mistake: it is simultaneously too slow for chat and too aggressive for email. Measure and target FRT per channel instead. The table below shows realistic 2026 benchmarks.
| Channel | Acceptable | Good | Best in class |
|---|---|---|---|
| Within 24 hours | Under 4 hours | Under 1 hour | |
| Live chat | Under 2 minutes | Under 60 seconds | Under 30 seconds |
| Phone | Under 3 minutes | Under 60 seconds | Under 20 seconds |
| Social media | Within a day | Under 1 hour | Under 15 minutes |
| SMS and messaging | Under 30 minutes | Under 10 minutes | Under 5 minutes |
Treat these as starting points, not gospel. The right target for your team depends on what you have promised, what your customers expect, and what your staffing can actually sustain. A best-in-class chat number that you hit for one week and miss for the next three is worse than a solid "good" number you keep every day. Pick the column you can hold consistently, write it into a target, and improve from there.
What is the difference between first response time and resolution time?
First response time measures how long a customer waits for the first reply; resolution time measures how long the whole issue takes to close. They answer different questions and should never be collapsed into one number. FRT is about responsiveness and reassurance, the moment a customer knows a person is on it. Resolution time is about outcome, the moment the problem is actually fixed. A team can have an excellent FRT and a poor resolution time if it replies fast but then lets tickets drift, or a mediocre FRT and a strong resolution time if it is slow to acknowledge but quick to solve once engaged.
Both belong on your dashboard alongside first contact resolution, the share of issues solved in a single interaction. Read together, they tell the full story: FRT shows how fast you engage, first contact resolution shows how often you solve it in one go, and resolution time shows how long the rest take. For how these fit into a complete measurement set, see our guide to the customer service metrics and KPIs worth tracking, and when you formalize a target, put it in a written customer service SLA so both sides know what "on time" means.
Does first response time include automated replies?
No. A genuine first response time excludes automated acknowledgments. An auto-reply confirming that a ticket was received sets expectations and is worth sending, but it does not answer the customer's question, so counting it stops the clock on a promise you have not kept. The timer should stop only when an agent, or an AI that actually addresses the specific issue, engages with the customer's problem. If your help desk counts auto-replies by default, turn that setting off before you trust the number, because it will otherwise report a two-second FRT while customers wait hours for real help.
How do you reduce first response time?
First response time is mostly a queue and routing problem, not an agent-speed problem. Telling agents to type faster produces almost nothing; changing how work reaches them produces the real gains. These are the seven levers that move FRT, roughly in order of impact.
1. Route and triage automatically. The largest single source of delay is a ticket sitting unassigned while it waits for someone to notice it. Rules that tag incoming tickets by topic and drop them straight into the right queue or agent remove the dead time between arrival and ownership. This is the highest-leverage change most teams can make.
2. Prioritize new and unassigned conversations. Organize the inbox so brand-new tickets are visually unmistakable and always worked first. A message that has had no human contact is the one running up your FRT, so it should jump the line ahead of follow-ups on threads a customer already knows are being handled. Running this well is largely a matter of how you manage a shared support inbox so nothing lands in a gap between agents.
3. Build a library of saved replies. A large share of first contacts are variations on the same few questions. Well-written canned responses and templates let an agent send an accurate, personalized first reply in seconds instead of composing from scratch. The goal is a fast, real answer, not a robotic one, so keep templates specific and edit them per customer.
4. Deflect with self-service. Every question a customer answers themselves is a ticket that never enters the queue, which shortens the wait for everyone still in it. A searchable customer service knowledge base is the cheapest FRT improvement available, because the fastest first response is the one you never had to send.
5. Set an SLA target and surface aging tickets. A number you commit to changes behavior in a way a vague intention never does. Attach an FRT target to incoming tickets, then make the tickets approaching that target impossible to miss with alerts or a countdown view, so the team acts before a breach instead of after.
6. Staff to your volume curve. FRT collapses when volume spikes and coverage does not. Look at when tickets actually arrive across the day and week, and schedule people against that curve rather than a flat headcount. A Monday-morning surge answered by the same staffing as a quiet Friday afternoon is a predictable FRT failure.
7. Use automation for genuine first answers. An AI agent that resolves or meaningfully advances common questions can cut FRT dramatically, because it engages instantly and around the clock. The rule stays the same as with auto-replies: it only counts toward FRT if it actually answers the question rather than acknowledging receipt. Used honestly, automation is how leading teams push email FRT from hours to minutes.
Why is my first response time not improving?
The most common reason FRT stalls is that the team is optimizing agent behavior when the delay lives in the queue. If tickets sit unassigned for an hour before anyone opens them, no amount of faster typing helps, and the fix is routing, not coaching. The second common reason is a definition problem: if your tool counts auto-replies or measures calendar hours instead of business hours, your number is either fictionally good or unfairly bad, and you are chasing a metric that does not reflect reality. The third is volume outrunning staffing, where FRT looks fine on average but blows out during predictable peaks. Before spending effort on speed, confirm the metric is measured honestly, check where the time is actually being lost between arrival and first reply, and fix that specific gap. FRT rarely improves from general effort; it improves from removing the one delay that dominates your queue.
Making first response time a metric you can trust
First response time earns its place at the top of the dashboard because it maps directly to how supported a customer feels, but only if you measure it the way customers experience it: in business hours, excluding automated noise, per channel, and reported as both median and average. Get the definition right first, then work the queue and routing that produce most of the delay, and set a target you can hold every day rather than a heroic number you hit once. Pair it with resolution time and first contact resolution so a fast first reply never becomes an excuse for a slow fix, and keep the whole set consistent through your customer service ticketing system so the numbers mean the same thing every week. Handled this way, FRT stops being a vanity figure and becomes what it should be: an early, honest signal of whether your customer experience operation is keeping up with the people who depend on it.