First Response Time Calculator
Paste your ticket timestamps or enter your averages. See your mean, median, and p95 response times vs. industry benchmarks.
One row per ticket. Two timestamps separated by a comma: customer message, first reply. Up to 1,000 rows.
What is first response time?
First response time (FRT) is the elapsed time between when a customer sends a message and when they get a human reply. Not an auto-acknowledgement. Not a ticket-created webhook. A real human response.
It matters because it is the single support metric customers feel most directly. Resolution time matters for closure. CSAT matters for sentiment. FRT matters for whether a customer thinks anyone is listening.
Mean vs. median vs. p95
Mean
The average. Gets pulled up by a handful of tickets that sat in the queue over a weekend. Useful as a headline number, misleading if you use it alone.
Median
The middle value. Half your tickets were answered faster; half were slower. This is the honest "typical customer" number and the one to track day-to-day.
P95
95% of your tickets were answered within this time; 5% were slower. This is the worst-case-experience number. A great median with a bad p95 means most customers are happy but a small group is getting ignored — and they are the ones writing reviews.
First response time benchmarks by channel
| Channel | Excellent | Good | Average | Slow |
|---|---|---|---|---|
| < 1 hr | 1–4 hr | 4–12 hr | > 12 hr | |
| Live chat | < 1 min | 1–5 min | 5–15 min | > 15 min |
| Social | < 30 min | 30 min – 2 hr | 2–12 hr | > 12 hr |
What moves first response time
- Coverage during peak hours — most teams are understaffed in the first hour of the day
- A triage step before tickets hit the specialist queue
- Saved replies for the top 5 question types — usually 50% of all tickets
- Inbox routing rules so urgent tickets surface first
- A first-responder-on-call rotation, especially for small teams
First response time is not everything
FRT is a leading indicator; resolution time and CSAT are lagging indicators. A 30-second "got it!" followed by three days of silence is worse than a two-hour real reply. Teams that optimize only for FRT end up sending fast, low-quality replies that kick the conversation further down the queue.
From calculator to dashboard
The calculator runs once. A help desk with real-time FRT tracking keeps you honest every day. Auxx.ai shows FRT live on every ticket and by channel, so you can spot a problem the same hour it starts — not the week after.
Frequently asked questions
Related free tools
Track first response time live, not once a quarter.
Auxx.ai puts FRT, resolution time, and SLA compliance in one dashboard — updated on every ticket.
See how Auxx.ai works