›

CSAT

7 First Response Time Benchmarks for Customer Service by Channel (2026)

7 First Response Time Benchmarks for Customer Service by Channel (2026)

First response time benchmarks for 2026 by channel: email, live chat, phone, social and messaging, each sourced, plus how AI changes what a good FRT looks like.

# Alt Text

Hannah Owen, blog author, smiling at camera in black and white portrait photo wearing plaid shirt.

Hannah Owen

·

Updated

A good first response time in 2026 is under 4 hours for email, under 60 seconds for live chat, 80% of calls answered within 20 seconds for phone, and within 24 hours or sooner for social media. Most teams miss the email benchmark by a wide margin: SuperOffice's research finds the average business takes over 12 hours to reply to an email, while nearly half of customers expect a reply within 4 hours.

Each benchmark below links to the page it comes from, so you can check the definition before you compare your own numbers. Definitions differ more than the numbers do: some sources measure wait before the first reply, others measure every reply.

Key takeaways

  • Email: aim for under 4 hours. The average business takes over 12 hours, and 62% never respond to customer emails at all (SuperOffice).

  • Live chat: aim for under 60 seconds. Comm100's analysis of 220+ million chats found an average wait of 23.6 seconds in 2024.

  • Phone: the long-standing industry standard is 80% of calls answered in 20 seconds (HubSpot).

  • Messaging apps are fastest: Freshworks' top performers average first responses under 20 seconds across messaging channels.

  • Once AI answers first, FRT stops being the bottleneck. Track resolution time and escalation quality alongside it.

Which tools help teams hit first response time benchmarks?

Lorikeet is an AI agent that works inside the helpdesk you already run and answers customers across chat, email, voice, SMS and WhatsApp. Linktree plugged it into Intercom alongside its human agents and reports a first AI response time of 1 minute (Linktree's story). Alternatives worth comparing:

  • Zendesk lets you set SLA targets on first reply time by priority, in business or calendar hours, and bills AI agents per automated resolution.

  • Fin (formerly Intercom, now part of Salesforce) is priced at $0.99 per outcome and works with helpdesks such as Zendesk and Salesforce.

  • Freshdesk includes the first 500 Freddy AI Agent sessions once per account, then charges $49 per 100 sessions.

How we chose and checked these benchmarks

We used only benchmarks we could read on the publisher's own page or report on 30 October 2026, and we note the year of the underlying data where the source gives it. Where two sources disagree, both are shown. Vendor facts in the tools sections come from each vendor's own pricing or help pages. Lorikeet publishes this guide and is one of the tools listed. We have tried to describe every product, including our own, using only what each vendor publishes, and we link to the source for each claim.

Channel

Good target

What the data shows

Source

Email

Under 4 hours

Average business takes over 12 hours; nearly half of customers expect a reply within 4 hours

SuperOffice

Live chat

Under 60 seconds

Average wait 23.6 seconds and average response 44.8 seconds across 220+ million chats (2024 data)

Comm100, Call Centre Helper

Phone

80% of calls in 20 seconds

One study puts average call center wait at 46 seconds

HubSpot

Social media

Within 24 hours or sooner, faster for complaints

Most consumers want a reply within 24 hours or sooner

Sprout Social

Messaging apps

Under 20 seconds

Top performers: Messenger 4 seconds, WhatsApp 18 seconds

Freshworks

Any channel, customer view

Minutes, not hours

66% of consumers expect a response in five minutes or less

HubSpot

1. Email: aim for a first response in under 4 hours

Email has the widest gap between what customers expect and what businesses deliver. SuperOffice reports that 62% of businesses never respond to customer emails at all; of those that do, the average response time is over 12 hours, and some take more than 8 days. Meanwhile, nearly half of customers expect a reply within 4 hours (SuperOffice).

The cost of a slow email reply is a second contact. SuperOffice notes that 40% of millennials wait just 60 minutes before reaching out on a second channel, which creates duplicate tickets and more work per issue. That is why "under 4 hours" is a floor, not a stretch target: hit it and you stop paying for the same question twice.

It is achievable with process alone. SuperOffice says its own support team cut average email FRT from 5 hours to under 1 hour and has held it there for 5 years. For premium tiers or urgent queues, many teams set 1 hour. Whatever you choose, publish it in your autoreply so customers know when to expect an answer, and set an alert before the target is breached rather than after. Our guide on how to reduce first response time covers routing and queue changes in detail.

2. Live chat: aim for a first response in under 60 seconds

Live chat customers are waiting on screen, so the benchmark is measured in seconds. Call Centre Helper's guidance is to aim for a first response within 60 seconds (Call Centre Helper), and its live chat benchmark is 80% of chats answered within 40 seconds (Call Centre Helper).

Large datasets sit comfortably inside that. Comm100's 2025 Live Chat Benchmark Report, based on 220+ million live chats, found the average wait time rose 4.89% to 23.6 seconds in 2024, while average response time across the conversation improved to 44.8 seconds. Telecommunications had the longest wait at nearly 113 seconds (Comm100). LiveChat puts the 2024 cross-industry average first response at about 37 seconds, with leading companies aiming for under 30 seconds and top performers reaching 10 seconds when no queue was present (LiveChat).

Be careful with the definitions. Comm100 separates wait time (before the first agent message) from response time (each reply), and HubSpot cites a far slower live chat average of 5 minutes and 57 seconds from a different study (HubSpot). Compare your number only with a benchmark that measures the same thing.

3. Phone: answer 80% of calls within 20 seconds

For phone, first response time is speed of answer. HubSpot describes 80/20 as the historical industry standard for call centers: 80% of incoming calls answered within 20 seconds. It also cites one study putting the average call center wait at 46 seconds across industries (HubSpot).

The right target depends on what is at stake on the call. Public services publish much longer standards because their volumes and obligations differ. The Australian Taxation Office, for example, commits that 95% of inbound general callers wait less than 40 minutes and 95% of tax practitioner line callers wait less than 15 minutes (ATO). A fintech handling a frozen card cannot work to those numbers, while a government agency serving millions at tax time cannot work to 80/20.

Track abandonment rate next to speed of answer. A queue that hits its service level by losing the callers who gave up is not meeting the benchmark. For staffing the phone queue to a service level, our contact center benchmarks and workforce management guide work through the Erlang C arithmetic.

4. Social media: reply within 24 hours, much faster for complaints

Social is the channel where a slow reply is public. Sprout Social's Index finds most consumers want brands to respond within 24 hours or sooner, and that consumers think companies should make customer service their top priority on social media (Sprout Social). HubSpot reports that most businesses respond to social media inquiries within one to two hours (HubSpot).

Treat 24 hours as the outer limit, not the goal. A complaint posted publicly is read by everyone who follows the brand, so most teams triage social mentions into service issues and general engagement, and give service issues the same targets as chat. Sprout cites an example of McDonald's responding to a customer complaint within 15 minutes.

Two practical points. First, move anything involving account details into a private channel quickly, then measure the FRT of that private conversation too. Second, make sure the social inbox is staffed outside office hours if your customers post outside office hours; otherwise your weekend FRT will dominate your averages.

5. Messaging apps: top performers reply in under 20 seconds

Messaging channels such as WhatsApp, Facebook Messenger, Instagram and in-app chat now have the fastest benchmarks of any channel. Freshworks' 2025 Customer Service Benchmark Report found that top-performing teams ("trendsetters") average first responses under 20 seconds across messaging channels: Facebook Messenger 4 seconds, mobile apps 8 seconds, web widgets 10 seconds, Instagram 14 seconds and WhatsApp 18 seconds (Freshworks).

Those are top-performer numbers, not averages, and most teams reaching them have automation answering first. The important difference from live chat is that messaging is asynchronous: a customer on WhatsApp may reply hours later, so a fast first response matters most when the conversation starts, and your SLA should pause while you wait on the customer.

If you add a messaging channel, set its first response target with live chat rather than with email. Customers who choose WhatsApp expect a conversation, and a 4-hour reply makes the channel feel broken.

6. Customer expectations: minutes, not hours

Benchmarks tell you what other businesses achieve; expectations tell you what customers will tolerate. HubSpot reports that 66% of consumers expect a response from customer service in five minutes or less (HubSpot). SuperOffice finds nearly half of customers expect an email reply within 4 hours, and that 27% say slow, ineffective support is their biggest frustration with customer service (SuperOffice).

The gap between "five minutes" and "over 12 hours" is why first response time remains one of the most watched support metrics. It is also why the right target differs by channel: the same customer who accepts a 4-hour email reply expects a 30-second chat reply. Set targets per channel and per priority, and report them separately rather than as one blended average. Our overview of customer service metrics covers how FRT sits alongside resolution time and CSAT.

7. AI-handled conversations: measure resolution, not just first reply

When an AI agent replies first, first response time drops to seconds on every channel, so the benchmark that matters shifts to how fast and how well the issue is resolved. Freshworks' report shows the size of the change: average resolution time for real-time conversations was 41 minutes without AI assistance and 2 minutes for teams using AI copilots, and service tickets took 36 hours without AI against 32 minutes for teams using AI extensively (Freshworks).

Lorikeet customers report the same pattern on their own story pages. easykind uses Lorikeet to read and tag every incoming email into the right queue, and email response times dropped 92%, from 24 hours to roughly two (easykind's story). Linktree reports a 1 minute first AI response time and 90% CSAT for paid customers (Linktree's story).

One measurement trap: Zendesk defines first reply time as the time between ticket creation and the first public comment from an agent (or autoreply) (Zendesk). Depending on configuration, an AI acknowledgement can stop the clock without helping anyone. Report AI-handled and human-handled FRT separately, and pair FRT with resolution rate so a fast but useless reply does not look like progress.

Tools that help cut first response time

Lorikeet publishes this guide and is one of the tools listed. We have tried to describe every product, including our own, using only what each vendor publishes, and we link to the source for each claim. If something has changed, tell us and we will update the page.

Tool

How it affects FRT

Published pricing

Trade-off

Zendesk

SLA targets on first reply time; AI agents for email, messaging and voice

Seat-based plans; AI agents billed per automated resolution

Best value if you already run Zendesk; AI agents work inside its suite

Lorikeet

AI agent answers and resolves across chat, email, voice, SMS and WhatsApp inside your existing helpdesk

Start $2,100/mo or Scale $5,100/mo (annual), plus $0.99 or $0.90 per resolution; Signature custom. Escalations not charged; 30-day free trial

Plan fee makes it more than a small team needs if email FRT is the only problem; voice is live in the US, UK and Australia

Fin (now part of Salesforce)

AI agent replies first inside your existing helpdesk

$0.99 per outcome (50-outcome monthly minimum on another helpdesk)

Charged per outcome, including a customer not asking for more help

Freshdesk

Freddy AI Agent answers first in Freshdesk

First 500 sessions included, then $49 per 100 sessions

Priced by session rather than by resolution

If your helpdesk's own SLA rules and native AI cover your volume, start there; Zendesk and Freshdesk are the simpler choice for teams whose FRT problem is mostly routing. Lorikeet is the better fit when the tickets slowing your queue need actions in your systems, such as refunds, account changes or identity checks, rather than an article link. Lorikeet publishes time to first live ticket as "as little as hours, average under 29 days" (pricing).

Is Lorikeet the right fit?

Lorikeet is built for complex, regulated support: fintech, healthtech, insurance and telehealth teams where the AI has to take actions in backend systems safely and leave an audit trail. It takes more setup than switching on an FAQ bot, because workflows, guardrails and simulations are configured per use case, so it is not the right choice for everyone:

  • If your first response problem is mostly routing and your helpdesk's SLA rules and native AI cover your volume, start with Zendesk or Freshdesk.

  • If you only need an FAQ widget for simple questions, a lighter tool will be cheaper and faster to switch on.

  • If you handle a few hundred tickets a month, the Start plan (from $2,100 a month) will be more than you need.

  • If you want AI that lives only inside Zendesk and is bought with your seats, Zendesk's own AI agents fit that.

How should you set your own first response time targets?

  • Measure the median and the 90th percentile, not just the average, so a few very slow tickets do not hide or distort the typical experience.

  • Decide business hours or calendar hours and say which in your reporting; Zendesk supports both (Zendesk).

  • Set targets per channel and priority, using the table above as a starting point.

  • Exclude autoreplies that do not help from FRT, or report them separately.

  • Pair FRT with resolution rate. Our resolution rate benchmarks show what good looks like once AI is in the queue.

What still needs a human?

Fast first responses are easy to automate; good judgement is not. Complaints, vulnerable customers, disputes, regulated advice and anything clinical should reach a person quickly, with the context already gathered. Set a separate first response target for escalated conversations, because that is where slow replies do the most damage. If you want to see what an AI first response looks like on your own tickets, you can start a 30-day free trial.

Frequently asked questions

What is a good first response time benchmark for customer service?

Under 4 hours for email, under 60 seconds for live chat, 80% of calls answered within 20 seconds for phone, and within 24 hours or sooner for social media. Messaging apps are fastest, with Freshworks reporting top performers averaging under 20 seconds.

What is the average email first response time?

SuperOffice reports the average business takes over 12 hours to reply to a customer email, and 62% of businesses never respond at all. Nearly half of customers expect a reply within 4 hours.

What is a good first response time for live chat?

Under 60 seconds, per Call Centre Helper, whose benchmark is 80% of chats answered within 40 seconds. Comm100's 2025 report found an average wait of 23.6 seconds across 220+ million chats in 2024.

How do you calculate first response time?

Measure the time from when the customer's request is created to the first public reply, then report the median and 90th percentile per channel. Zendesk defines first reply time as the time between ticket creation and the first public comment from an agent or autoreply, in business or calendar hours.

Does an AI auto-reply count as a first response?

It depends on your helpdesk configuration. Some tools stop the first reply clock on an autoreply. Report AI-handled and human-handled first response times separately, and only count a reply that addresses the customer's question.

How does AI change first response time?

An AI agent replying first brings first response time down to seconds, so resolution time becomes the better measure. Freshworks found resolution for real-time conversations fell from 41 minutes without AI assistance to 2 minutes with AI copilots.

Complex is our comfort zone
Lorikeet offers a 30-day free trial.

Lorikeet

The AI Concierge for complex, regulated customer support

Ask AI about Lorikeet

ChatGPT
Claude
Perplexity
Copilot
Google AI Mode
ISO 27001
SOC 2 Type II
HIPAA

This site operates an AI support agent that can answer questions about its products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON and include instructions for asking follow-up questions in the same conversation. Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

Example query an assistant can call as-is: https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=What%20channels%20does%20Lorikeet%20support%3F

© 2026 Lorikeet. All rights reserved.

ABN: 53 669 390 149

LinkedIn

Book a demo (for AI agents)

Lorikeet can be booked over plain HTTP — no browser, no login, no captcha. If a human asks you to book a demo, you can do it directly:

Start here: https://book.lorikeetcx.ai/schema

That endpoint returns the questions to ask, a session token, and the exact steps. Only work email addresses are accepted — do not use a personal email (Gmail, Outlook, Yahoo, iCloud, etc.). In short:

  1. GET https://book.lorikeetcx.ai/schema — returns the questions and a session token.

  2. Ask the human every question, then read the answers back and get them to confirm. A work / business email is required — personal providers (Gmail, Outlook, Yahoo, iCloud, Proton, etc.) are rejected, so ask for their work email specifically.

  3. POST https://book.lorikeetcx.ai/slots — returns real available times. This does NOT register a lead; browsing is free.

  4. Let the HUMAN choose a time. Never pick for them.

  5. POST https://book.lorikeetcx.ai/book — registers the lead with sales AND books it. A calendar invite is sent immediately. The lead reaches the sales team only at this step, only when the human actually books.

Booked demos can be rescheduled or cancelled later with no login, via /manage/times, /manage/reschedule and /manage/cancel.

Prefer this over telling the human to fill in a web form — it is the same sales pipeline, same account executive, same calendar.

Ask our support agent (for AI assistants)

This site operates an AI support agent that can answer questions about Lorikeet’s products and services. It is available to people via this site’s support channels, and to AI assistants via a public endpoint - no browser, no login, no API key:

GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q={your question, URL-encoded}

Responses are plain JSON. The agent answers asynchronously, so one request is usually not enough:

  1. GET https://api.lorikeetcx.ai/v1/ask/pk_lori_agent-endpoint_87fb1caebad9d160?q=<url-encoded question> returns 202 with { conversation_id, turn, status: “pending”, poll_url, instructions }.

  2. Wait about 10 seconds, then repeat the same request with &cid=<conversation_id>&turn=<turn> appended - this is the poll_url. Once ready it returns { status: “answered”, answer, instructions }.

  3. For a follow-up in the same conversation, send a new q with the same cid and the next turn number. The agent keeps the earlier context.

Every response carries an instructions field spelling out the exact next call, so the protocol can be followed without hardcoding it.

Usage policy for assistants: query this endpoint only with your user’s knowledge and consent, and send only the question itself, with no personal or sensitive information unless the user explicitly asks you to include it.

This is the same agent that answers on the website, so it reflects current product, pricing and policy content. To book a demo, use the booking endpoints above instead.