Support metric guide
First-response time explained
Learn how to calculate customer-support first-response time, distinguish human replies from acknowledgements and improve the slowest waits without gaming the metric.
Formula per ticket = first qualifying agent reply time minus ticket creation time.
Publish the clock, channel, exclusions and chosen summary statistic beside the number.
Improve triage and coverage before encouraging empty speed-only replies.
Product shortlist
Tools for response reporting
Ask each provider to reproduce your first-human-reply definition and show the slowest unanswered cases on the plan you intend to buy.
Freshdesk
Best for: Growing teams that need proper ticketing, self-service, automation and reporting
A broad email-first help desk with ticketing, a shared inbox, a customer portal, knowledge base and out-of-the-box reporting on its entry paid plan.
$19 per agent/monthGrowth, billed annually; checked September 2026
Useful strengths
- Ticketing, shared inbox and knowledge base on Growth
- Clearer route into routing, SLAs and custom reporting
Watch for
- Omnichannel needs differ from the email-first Freshdesk plan
- AI and connector usage can add cost
- Free trial
- Email-first help desk
- Per-agent pricing
Zendesk
Best for: Teams that expect multiple channels, mature routing and increasing operational complexity
The Support Team plan supplies core email ticketing, routing, analytics and automations. The broader Suite adds live chat, messaging, telephony and a knowledge base.
£15 per agent/monthSupport Team, paid yearly; checked September 2026
Useful strengths
- GBP pricing and a clear entry ticketing plan
- Strong upgrade path for multichannel operations
Watch for
- Suite Team rises to £45 per agent/month
- Small teams may buy more process than they need
- 14-day trial
- GBP pricing available
- Per-agent pricing
Zoho Desk
Best for: Budget-conscious teams and businesses already using the Zoho ecosystem
The free edition covers three users and email ticketing. Paid tiers add broader messaging, knowledge-base, reporting, automation and telephony capabilities in stages.
Free for 3 usersPaid plans vary by selected billing currency; checked September 2026
Useful strengths
- Three-user free edition
- Broad channel and Zoho integration range
Watch for
- Plan and currency selectors make budgeting less immediate
- Live chat and advanced routing are plan-dependent
- 15-day trial
- Free edition
- Three users on free plan
HelpDesk
Best for: Small teams that want ticketing, website chat and useful automation without an enterprise platform
A focused support workspace combining ticketing, a shared inbox, website chat, messaging channels, automation and reporting in one entry plan.
$19 per user/monthEssential, billed annually; checked September 2026
Useful strengths
- Ticketing, website chat and messaging channels on Essential
- 14-day trial without a credit card
Watch for
- There is no permanent free plan
- Extra AI resolutions can add usage cost
- 14-day trial
- Email, chat and messaging
- Per-user pricing
First-response time (FRT) is the wait from a customer's initial support request to the first reply that meets your reporting rule. It answers a narrower question than resolution time: when did somebody respond? It does not tell you whether the answer was correct, whether the customer had to write again or how long the issue ultimately lasted.
Zendesk's first-reply explanation starts at ticket creation and stops at the first public agent response, with calendar- and business-hour variants. Live conversations can have channel-specific rules. Use that as an example of why “first response” needs a written definition, not as an assumption that every product calculates it identically.
Calculate the time for one ticket
First-response time = timestamp of first qualifying agent reply − timestamp the ticket was created. A request received at 09:00 and answered at 10:30 has a calendar first-response time of 90 minutes. If the request arrived at 17:30 on Friday and the agent replied at 09:30 on Monday, the calendar wait is much longer than the staffed-hours wait. Neither clock is inherently wrong; using the wrong one for the published service promise is.
Decide what starts the clock when a customer begins in chat then follows up by email. Decide whether agent-created tickets, spam, internal tests and imported history belong in the population. An auto-receipt should be tracked as a delivery event, not a solved conversation. Freshdesk's SLA guidance distinguishes a system-generated Send Reply action from a qualifying first response for its SLA.
Summarise without hiding the slow cases
For a period, calculate the duration for each eligible ticket, then show the median, the 90th percentile and the number still awaiting a first reply. If 90 tickets received a reply quickly and 10 waited all weekend, one average obscures the customer experience at the tail. Open tickets without a first reply do not yet have a completed FRT; do not silently drop them from an operating dashboard.
Split email from live chat and urgent cases from routine questions. Compare like schedules and periods. A change from calendar to business hours can make the chart appear to improve even when customers wait just as long. Annotate policy, channel and staffing changes. If you use an SLA compliance percentage, show the denominator and whether unsent first replies are included.
Diagnose and improve the wait
Start with the slowest real cases. Was the ticket unassigned, misrouted, created after closing time, waiting on a specialist, or hidden by a channel integration? Those causes need different fixes. A daily unassigned-ticket sweep and a clear backup owner are often more useful than a new target. If arrivals cluster at opening time, adjust coverage or triage. If the first reply takes long because agents need context, improve the form or customer history visible in the inbox.
Keep response quality in view. A copy-pasted “we're looking into it” can stop a timer while giving the customer no next step. Sample replies for acknowledgement of the specific problem, a useful action or an honest expected update. Pair this page with ticket resolution time and CSAT so speed does not become the only incentive.
Check the product rather than the label
Freshdesk and Zendesk document response measures and SLA reporting, while Zoho Desk and HelpDesk may suit teams wanting a simpler queue. Reporting access and customisation vary by edition. In a trial, create a Friday-after-hours ticket, an automated acknowledgement and a real first reply. Verify which event stops the native clock and whether you can display unanswered work. The help desk pilot provides a broader test method.
Sources
- Zendesk: understanding ticket reply time
- Freshdesk: support SLA response rules
- Zendesk: Support metric definitions
The calculation examples and operational recommendations are Support Sorted's editorial guidance.
Frequently asked questions
Questions readers ask before choosing
What is first-response time in customer support?
It is the elapsed time between a new customer request and the first qualifying support reply. Specify whether the reply must be public and human, and whether the clock runs in calendar or business hours.
Does an automatic acknowledgement count as a first response?
It is useful as a receipt, but it is not a human answer. Some products exclude it from their native first-response measure; report acknowledgements separately so readers understand what customers actually received.
Should we report average or median first-response time?
Report a typical measure such as the median alongside a tail measure, for example the 90th percentile or the oldest unanswered tickets. Averages are easily distorted by a few extreme waits.
What is a good first-response-time target?
There is no universal target. Set one by channel, urgency and staffed hours, then test whether the team can meet it without sending superficial replies or leaving harder cases behind.