TL;DR

The share of incoming chats or messages your team actually answers, expressed as a percentage.

Key Points

✓

Formula: response rate = (conversations that got a reply / total conversations) x 100; the inverse is the missed chat rate, which Gorgias suggests keeping under 5% [3].

✓

It answers "did we respond?" while [[first-response-time]] and [[average-response-time]] answer "how fast?" - track both together for a full picture.

✓

A low response rate usually points to staffing gaps, awkward [[business-hours]] coverage, or chats arriving while operators are away rather than slow typing.

✓

Set an [[offline-message]] or a clear [[welcome-message]] so conversations opened after hours are captured and can still be answered, protecting the rate.

✓

Response rate is a coverage metric, not a quality one - pair it with [[first-contact-resolution]] and [[customer-satisfaction-score]] so you are not just replying but resolving [1].

✓

On a [[telegram-integration|Telegram-based]] setup like Eloqra, every visitor message is forwarded to an operator, so the practical lever for response rate is making sure those notifications get seen and answered.

How response rate is calculated

Response rate divides the number of conversations that received at least one operator reply by the total number of inbound conversations, then multiplies by 100. The complementary view is the missed chat rate - the percentage of chat requests that get no answer - which Gorgias defines as missed chats divided by total chat requests, recommending under 5% as good and under 3% as excellent ^[3]. Decide upfront whether automated replies count: a Welcome Message or Autoresponder fires automatically and can inflate the number, so most teams count only human responses. Because the metric ignores timing, a conversation answered an hour late still counts as answered, which is why response rate is read alongside speed metrics rather than on its own.

Response rate versus response time

Response rate and response-time metrics measure different things and are easy to confuse. First Response Time (FRT) captures how long a Website Visitor waits for the first reply, while Average Response Time averages reply speed across a Conversation; both assume a reply eventually happened ^[1]^[2]. Response rate steps back and asks whether a reply happened at all. A team can have an excellent first response time and still leak conversations if some chats are never picked up. Help Scout notes that for speed metrics the median often reflects the true visitor experience better than the average, since a single lost chat skews the mean ^[2]. Reviewing response rate first, then speed, prevents a fast-but-incomplete team from looking healthier than it is.

Improving and protecting your response rate

The biggest wins come from coverage, not typing faster. Define realistic Business Hours and use an Offline Message to capture out-of-hours chats so they are answered later instead of abandoned. Reduce friction at entry - a heavy Pre-Chat Form can deter a Website Visitor before they ever send a message, hurting the denominator and the rate. Make sure incoming alerts are impossible to miss: in a Telegram workflow such as Eloqra, every visitor message is pushed to the operator's phone, so a high response rate comes down to notification discipline rather than a staffed queue. Finally, watch response rate next to Chat Abandonment Rate - visitors who leave before any reply drag both metrics down and signal where to add coverage ^[3].

Sources & References

12 Key Live Chat Metrics & KPIs to Measure Agent Analytics - REVE Chat ↗

8 Actionable Live Chat Metrics to Start Tracking Today - Help Scout ↗

14 Live Chat KPIs Every Ecommerce Brand Should Track - Gorgias ↗

Last updated: June 25, 2026

Related Terms

First Response Time (FRT)

First Response Time (FRT) is the elapsed time between a customer's first message in a conversation and the first human reply from a support agent. It measures how quickly your team acknowledges an inbound request, not how long it takes to resolve it.

Average Response Time

Average Response Time (ART) is a support metric measuring the mean time customers wait for an agent reply across all messages in a period, not just the first one. It is calculated as total wait time divided by the number of replies sent.

Chat Abandonment Rate

Chat abandonment rate is the percentage of live-chat conversations that visitors start but leave before connecting with an agent or reaching a resolution. It is a support-quality metric that surfaces friction caused by long waits, confusing UX, or being ignored.

First Contact Resolution (FCR)

First Contact Resolution (FCR) is the percentage of customer issues fully resolved in a single interaction, with no transfer, callback, or follow-up needed. It measures how often a support team solves a problem the first time the customer reaches out.

Customer Satisfaction Score (CSAT)

Customer Satisfaction Score (CSAT) is a support metric that measures how happy a customer is with a specific interaction, product, or service, usually captured by a short post-interaction survey. It is expressed as the percentage of respondents who rate their experience as satisfied or very satisfied.

Business Hours

Business hours are the configured windows of days and times during which a support team is staffed and expected to answer live conversations. They let a chat tool switch between a live, real-time experience and an after-hours fallback so customers always know whether someone is available.

Collect testimonials that build trust

Eloqra gives you a lightweight live chat widget that routes every visitor message to your Telegram — free while in early access.

Get Started Free

Response Rate