First Response Time
First response time (FRT) is how long a customer waits between sending a support request and getting the first reply from a person. It is usually reported as a median, in business hours, and it is one of the strongest drivers of customer satisfaction.
What is first response time?
First response time measures the wait before a customer hears from a human. The clock starts when the request arrives and stops at the first reply from your team. Automatic acknowledgements don't count, because they don't move the customer forward.
Report it as a median, not an average. A handful of conversations that sat over a long weekend can drag an average up and hide how fast you usually are. Look at the distribution too: how many replies land within an hour, within four hours, within a day.
What good looks like
Expectations depend on the channel. Customers in live chat expect a reply in minutes. Email customers accept hours. Whatever your targets, measure them in business hours so the numbers reflect when your team is actually working.
How to bring it down
Most FRT problems are routing problems. Conversations sit unassigned, or land with someone who is offline. Assign automatically to available teammates, give each team its own view, and sort the queue by SLA deadline rather than arrival time.
Then remove work from the queue. Macros cut the time to write common replies. A help center and an AI agent answer the questions that don't need a person, so your team's first replies go to the ones that do.
First response time in Quackback
Quackback's support report shows first response time and its distribution, next to time to close, resolution rate and teammate performance. A default SLA you set puts a first-response target on every new conversation, with clocks that follow your office hours. Auto-assign can hand new conversations to the least-loaded teammate who is online, and Copilot drafts a first reply from your help center and past conversations so the agent starts from something.
Common questions
What is first response time?
First response time is how long a customer waits between sending a support request and getting the first reply from a person. Automatic acknowledgements do not count.
Should first response time be measured as an average or a median?
A median. A few slow outliers can pull an average far above what most customers experience. Pair the median with a distribution, such as the share of replies within one hour.
How do you reduce first response time?
Route new conversations to available teammates automatically, sort the queue by SLA deadline, use macros for common replies, and deflect simple questions to a help center or AI agent.
Have another question? Talk to the team.