TL;DR

The share of chats people begin but quit before getting help, usually because the wait was too long.

Key Points

✓

Formula: (abandoned chats / total initiated chats) x 100, where an abandoned chat ends without the [[website-visitor]] reaching an agent or resolution [2].

✓

It is driven mostly by wait time: roughly 38% of customers abandon after waiting more than 30 seconds, and about half abandon once a response takes over an hour [3].

✓

Benchmarks vary by sector. Many teams target below 5%, while SaaS B2B commonly sees 15-25% and e-commerce 30-45% [1][2].

✓

Distinct from a missed chat: abandonment counts visitors who quit, while a missed chat is one the team never answers. Both hurt [[response-rate]].

✓

Closely tied to [[first-response-time]] and [[average-response-time]] - the faster the first reply, the fewer people walk away.

✓

Cut it with adequate staffing, a clear [[welcome-message]], honest wait expectations, and [[proactive-chat]] or a [[chatbot]] to cover gaps [4].

How to measure and interpret it

Chat abandonment rate is calculated as abandoned chats divided by total initiated chats, multiplied by 100 ^[2]. A chat counts as abandoned when the visitor opens the Live Chat Widget and sends a Chat Message but leaves the Conversation before an agent connects or the issue is resolved ^[1]. Treat it as a leading indicator rather than a verdict: a rising rate usually points upstream to slow First Response Time (FRT) or thin coverage rather than to agent quality itself. Because it captures lost contacts, abandonment also distorts other support metrics - abandoned sessions never produce a CSAT response and can mask your true First Contact Resolution (FCR). Always read it alongside volume and wait-time data for the same period.

Why chats get abandoned

The dominant cause is waiting. Around 38% of customers give up after more than 30 seconds without a first response, and roughly half abandon once the wait stretches past an hour ^[3]. Abandonment spikes most often trace to understaffed peak windows, so pulling historical chat volume by hour and day and scheduling around real traffic is the highest-leverage fix ^[4]. Beyond staffing, friction in the Live Chat Widget itself - a clunky Chat Launcher, a long Pre-Chat Form, or poor mobile layout - pushes people out before they ever connect. Setting expectations with a Welcome Message and honest wait estimates keeps more visitors in the queue while operators catch up.

Reducing abandonment in a lightweight setup

Small teams cannot always staff every hour, so the practical goal is to never leave a visitor in silence. A configurable Welcome Message sets a realistic tone, and an Offline Message or capturing an email lets you follow up asynchronously when nobody is live. Eloqra forwards each visitor message to the owner on Telegram so a solo founder can reply from their phone within seconds, which directly attacks the wait-time driver behind most abandonment ^[3]^[4]. For routine questions, a Knowledge Base or Self-Service Support deflects load so live agents stay free for the conversations that matter most. Measuring abandonment week over week tells you whether these changes are working.

Sources & References

The Ultimate Guide to Live Chat Metrics - LiveChat ↗

15 Live Chat Metrics & KPIs to Track with Benchmarks - Hiver ↗

What Is Live Chat Abandonment Rate in Ecommerce? - Alexander Jarvis ↗

Live Chat Performance Metrics: The Complete Guide - Kayako ↗

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.

Response Rate

Response rate is the percentage of inbound customer conversations that receive at least one human reply, calculated as answered conversations divided by total conversations over a period. It measures coverage (did anyone respond at all), not speed.

Live Chat

Live chat is a real-time, text-based support channel embedded in a website or app that lets visitors message a business and get answers within the same browsing session, without phoning or emailing. It pairs a customer-facing chat window with an agent or bot interface on the other side.

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.

Proactive Chat

Proactive chat is a live-chat tactic where the business initiates a conversation with a website visitor automatically, based on behavior or context, instead of waiting for the visitor to open the chat first. The message is triggered by rules such as time on page, the URL being viewed, or whether the person is a returning visitor.

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