What Is First Response Time? Meaning, Formula and a Support Example
For support managers and team leads: measure how long customers wait for a first reply, set fair targets by priority, and meet them.
What is first response time? First response time (FRT) is how long a customer waits between raising a ticket and receiving the first reply from a person on your team. It is one of the most watched support measures because it shapes the customer's first impression.
An automatic acknowledgement does not count. The clock stops when an agent actually responds, even if the issue is not yet solved.
This page explains how to measure it, a worked example, an illustrative support team, and how Apragya tracks first response targets on every ticket.
First response time meaning and formula
First response time for a ticket is the time of the first human reply minus the time the ticket was created, counted in business hours if your SLA uses them. Average first response time is the total of those times divided by the number of tickets that received a reply.
A worked example: a team works 9 am to 6 pm. A ticket arrives at 5:30 pm and is answered at 9:45 am the next day. In clock time that is 16 hours 15 minutes. In business hours it is 30 minutes on the first day plus 45 minutes on the second, or 1 hour 15 minutes.
If three tickets took 15, 45 and 120 minutes, the average is 60 minutes. With a 60 minute target, two out of three, or 67%, met it.
- Record when each ticket was created.
- Record the first reply from a person.
- Subtract, counting business hours if your SLA does.
- Average across tickets, and track the share within target.
What slow first responses cost
Repeat contacts
Customers who hear nothing write again, adding tickets.
Lost trust
A long silence feels worse than a slow fix.
Missed SLAs
Contract terms with business customers are breached.
Hidden urgency
Urgent issues wait in the same queue as simple questions.
An example: a Noida software support desk
Take an illustrative support team of eight for a billing software product, with tickets coming by email and WhatsApp. Urgent tickets were waiting as long as routine ones.
One urgent ticket, from arrival to reply
Ticket arrives
A customer cannot raise invoices; WhatsApp message.
Priority set
Marked urgent by the routing rule.
Due time set
First response due within one business hour.
Warning before breach
The lead is alerted as the time nears.
Agent replies
First response recorded, inside target.
After a month with priorities and due times, urgent tickets were answered first and the team's breaches dropped. Routine questions waited a little longer, which customers accepted because the targets were published.
How first response time SLA works in Apragya
Step 1 of 5
SLA policies
First response and resolution targets set per priority.
- SLA policies: First response and resolution targets set per priority.
- Business hours: Targets count working hours and holidays from a shared schedule.
- Due and actual times: Each ticket carries its first response due time and the time it was met.
- Pause when waiting: The clock pauses while the ticket waits on the customer.
- Warnings and escalation: Pre-breach warnings and escalation rules act before a target is missed.
Average first response time: measure it fairly
An average can hide a long tail. A team with a two hour average may still leave some customers waiting a day. Track the share of tickets answered within target by priority, and look at the worst cases as well as the average.
A shared inbox, against Apragya
| Feature | Shared inbox | Apragya Support |
|---|---|---|
| Priority | Decided by whoever opens it | Set by rules on arrival |
| Target | Informal | SLA policy per priority |
| Working hours | Ignored | Business hours and holidays counted |
| Breach warning | None | Alert before the target is missed |
| Reporting | Counted by hand | Support reports on SLA |
Checked against public information on 16 September 2026.
What sets Apragya apart for support
Channels
Email, WhatsApp Business and Twilio SMS messages become tickets.
Knowledge base
Articles help agents answer faster.
Canned replies
Saved replies for common questions.
One customer record
Tickets sit with the customer's orders and invoices.
AI with human review
Agents can suggest routing and replies for a person to approve.
Access by role
Agents, leads and managers see what they should.
See SLA policies, routing rules, support reports and the AI agent for support ticket routing.
How to reduce first response time
- Define priorities and a first response target for each.
- Set business hours and holidays.
- Route tickets to the right group on arrival.
- Use canned replies for common questions.
- Review breaches every week and fix the cause.
Most gains come from routing, not from asking agents to type faster.
What it costs to start
First response time SLA, answered
Does an automatic acknowledgement count as a first response?
Should first response time use business hours?
What is a good first response time?
Does the clock stop when we wait for the customer?
What does it cost to start?
Answer the right tickets first
Set SLA policies by priority and let every ticket carry its own due time.