Sign up for
Get started

What is a first response time (FRT)?

Definition: First response time (FRT) is a metric that measures the time that passes between a customer submitting a ticket and the support responding to it.

It is a key support metric that shows how quickly customers receive responses, which greatly impacts customer satisfaction.

How to calculate the first response time

It is a time measure represented in minutes, hours, or days depending on the timeframe the support team decides upon.

FRT is calculated by adding all the times it took the support to respond to tickets and dividing it by the number of tickets responded to.

First Response Time = Sum of Individual First Response Times / Total Number of Tickets

Note: This metric is also known as Average FRT. 

Note: Automated responses (chatbots, email automation, self-service) don’t count toward the total number of tickets.

For example, a support team had 100 tickets in the past month, and the combined time between the submitted tickets and responses to them was 5600 minutes.

FRT = 5600 / 100

FRT = 5,6 minutes is the average time the support takes to respond to a ticket.

Good first response time 

A benchmark for good FRT depends on the industry the company is in and the channels being used for support.

FTR based on the channel: 

  1. Live chat: 1 minute
  2. Social media 15 minutes
  3. Email: 60 minutes
  4. Phone: 3 minutes

FTR based on the industry:

  1. Finance: 30 minutes
  2. Real estate: 60 minutes
  3. Logistics: 60 minutes
  4. Retail: 30 minutes
  5. Software: 20 minutes

A business should set benchmarks based on its current FRT and work on lowering it without sacrificing quality. Once it’s consistently beneath the benchmark, a new benchmark should be set.

How to improve first response time?

There are two ways to lower FRT. The first is to reduce the time it takes for support to respond to a ticket, and the second is to lower the number of ticket requests.

To accomplish this, companies use these tactics:

  • Utilizing automation like chatbots and emails for common and easy-to-solve tickets contributes to them being responded to immediately and leaving the support room to work on complex tickets. Implementing self-service also helps lower the number of tickets by allowing customers to solve problems without needing support.
  • Using ticket routing reroutes new tickets to support representatives that can respond quickly due to their backlog and have the experience to solve the issue quickly.
  • Multiple support channels let customers choose how they want the ticket to be approached. It distributes tickets without putting strain on one channel.
  • Building a knowledge base lets support find answers quickly, letting them respond to the tickets immediately instead of researching what they will say to the customer. This is further improved by implementing standard procedures for ticket-solving across the team.

It’s essential to track FRT for every new strategy implemented and see if and how it impacts the speed of responses.

Wonder what your customers want?
Discover Mindmesh

Article FAQs

How do you calculate first response time?
Individual FRT is calculated by subtracting the on-the-clock time when the customer submitted the ticket and when the support responded to it. Another way is by tracking the time the ticket remains unopened with software.
What is the first response rate?
FRR measures the percentage of customer tickets that received a response within the established FRT benchmark. It is calculated by dividing the number of responses within the FRT benchmark by the total number of tickets.
What are the limits of FRT?
It only measures the support team's speed in responding to tickets without considering how much time they spend on resolving the ticket or the quality of the customer support being provided.‍

Recommended Terms


Get started

Hundreds of tech workers have already
tried Mindmesh and use it daily

Get Started

A monthly newsletter delivered straight to your inbox