First Response Time (FRT)
Definition
First Response Time (FRT)
First response time (FRT) is the clock between a customer’s ticket and an agent’s first substantive human reply, measured in business hours on every channel. A fast first reply earns patience for a slower fix, so FRT leads most service dashboards.
Definitions shift by channel. Chat FRT is usually seconds, email FRT is measured in hours, and social sits somewhere between. Faster is better, right up to the point where the reply stops being useful.
Most contact centres read FRT next to average handle time and resolution time. FRT carries extra weight because it is the first signal a customer gets after asking for help — and it shapes how the rest of the ticket feels.
Key takeaways
- FRT tracks the wait between a customer’s first message and an agent’s first human reply, not the full resolution.
- Benchmarks vary widely by channel: seconds for live chat, minutes for social, hours for email.
- Slower FRT correlates with lower customer satisfaction (CSAT) scores and higher churn.
- Automation, tiered routing, and follow-the-sun outsourcing shrink FRT without ballooning headcount.
- Median beats mean: a single overnight outlier will distort any average you report.
How it works
FRT is the timestamp gap between a customer’s inbound message and the agent’s first substantive reply. Automated acknowledgements do not stop the clock. Helpdesk platforms apply business-hour filters so an overnight ticket is not scored against the morning shift.
The formula is simple. Sum every first-response gap over the period, divide by ticket count, and report the median rather than the mean. A single 20-hour outlier — one overnight ticket — skews any average you publish.
Working targets differ sharply by channel. The bands below are the operational benchmarks support leads tend to set, not published research figures, so treat them as a starting point and tune them against your own queue.
| Channel | Good FRT | Great FRT |
|---|---|---|
| Live chat | Under 60 seconds | Under 30 seconds |
| Social media | Under 1 hour | Under 15 minutes |
| Messaging apps | Under 30 minutes | Under 5 minutes |
| Under 12 hours | Under 4 hours | |
| Phone | Under 3 rings | First ring |
| In-app support form | Under 8 hours | Under 2 hours |
Helpdesk platforms like Zendesk and Freshdesk calculate FRT automatically. If you are still running support out of a shared inbox, you will rely on plugin exports or spreadsheets, and the number always arrives late.
According to Zendesk’s CX Trends report, 72% of customers expect immediate service.
Few teams clear that bar on the first attempt. The gap between what customers expect and what your queue actually delivers is the figure worth managing, not the raw FRT on its own.
Business-hour rules matter. A ticket landing at 11pm should not count against Monday morning. Configure your ticketing system to respect timezone, holidays, and channel-specific windows before you trust the reported figure.
Some teams strip weekend hours entirely, others count them at half weight. That choice moves the reported number more than the arithmetic ever does.
An FRT of four hours reads very differently against a 24/7 service level agreement (SLA) than against a Monday to Friday window.
Most platforms let you set channel-specific FRT targets and alert supervisors when a queue drifts. Pair that with a live wallboard and agents self-correct before the SLA breaches — cheaper than explaining a miss after the fact.
Examples
Real teams tune FRT to their channel mix and staffing model. A Manila business process outsourcing (BPO) provider handling US chat traffic runs a 45-second overnight FRT. An in-house SaaS team can live with a four-hour email FRT.
In 2024, HubSpot’s State of Service report found top-quartile teams reply to chat in under 60 seconds and to email in under four hours. Bottom-quartile teams took more than 24 hours on email, a 6x spread on the same channel.
Manila outsourcers running follow-the-sun coverage for US and UK clients regularly clear sub-60-second chat FRT. They hand the queue to the next timezone at shift end, so no ticket sits overnight.
Our top BPO firms in the Philippines roster lists providers offering round-the-clock cover.
The seventh edition of Salesforce’s State of Service study found high-performing service teams are 1.8x more likely than underperformers to have adopted AI triage.
That routing shift alone compresses FRT on tier-1 tickets by roughly 40%, because the easy questions never reach a human queue at all.
Retail teams show a third pattern. Ahead of a Black Friday peak they pre-stage canned first replies and add a weekend shift, holding chat FRT near 60 seconds, then stand the extra cover down in January.
Demand for offshore support keeps climbing. Industry reporting shows offshore outsourcing volumes still rising through 2024.
Response speed is a big part of why. When a buyer compares two customer service outsourcing proposals, the FRT commitment in the SLA is usually the first line they read.
Related terms
FRT sits inside a family of service metrics, and each one measures a different slice of the response journey. The cluster below stops at the metrics FRT directly touches. Read them side by side rather than ranking them.
- Average Handle Time (AHT): total minutes an agent spends actively working a ticket.
- Service Level Agreement (SLA): the contract clause that fixes the FRT target and the penalty for missing it.
- Customer Satisfaction (CSAT): the post-contact survey score FRT most directly moves.
- Net Promoter Score (NPS): a longer-arc loyalty gauge that responds slowly to FRT changes.
- Help Desk: the tooling that queues tickets and reports FRT.
- Customer Experience (CX): the umbrella practice FRT feeds into.
FAQ
Support leads ask the same handful of questions about FRT: what counts as good, whether automation counts, and how it differs from resolution time. The answers below apply across chat, email, social, and phone queues.
What’s a good first response time?
It depends on channel. Under 60 seconds is strong for live chat, under four hours for email, and under 15 minutes for social. Phone lines usually aim for a first-ring pickup.
Does an auto-reply count as a first response?
No. FRT measures time to the first substantive human reply, so an automated acknowledgement does not stop the clock in most helpdesk platforms. Some teams report a separate auto-ack figure for compliance, kept well away from the headline number.
How is FRT different from resolution time?
FRT captures the initial reply, while resolution time captures the full journey to ticket close. A team can win on FRT and still fail on resolution, or the reverse, so read the pair together. Treated alone, either number flatters the queue.
Can outsourcing improve FRT?
Yes. Follow-the-sun coverage from a Manila or Cebu provider removes the overnight queue, and tiered routing pushes simple tickets to faster responders. Most clients see 30–50% FRT reductions in the first quarter after go-live.
How do you measure FRT across channels?
Report it per channel first, then roll up. Blending live-chat FRT with email FRT into one figure hides the story, since seconds and hours do not belong in the same average. Most helpdesk dashboards filter by channel out of the box.
What causes high FRT?
The usual suspects are understaffed shifts, poor ticket routing, no self-service deflection, and treating email as batch work.
Ready to shrink your FRT with outsourced support? Explore our outsourcing hubs.
Independent
