TL;DR

Live chat is an in-page messaging channel that connects website visitors with support or sales in real time, so questions get answered before the visitor leaves.

Key Points

✓

Live chat runs inside a [[live-chat-widget]] launched from a floating [[chat-launcher]], so visitors never leave the page they are on. [2]

✓

Each exchange is a [[conversation]] made of individual [[chat-message]] items, with [[typing-indicator|typing indicators]] signalling that a reply is on the way. [3]

✓

Speed is the core promise: a large share of customers expect a reply within five minutes, so [[first-response-time]] is the metric that matters most. [1]

✓

Because chat implies immediacy, agents typically juggle 2-5 chats at once ([[chat-concurrency]]); [[business-hours]] and an [[offline-message]] keep expectations honest when no one is available. [4][2]

✓

Live chat also drives revenue, not just support: it powers [[lead-capture]] and [[conversational-marketing]] by engaging high-intent [[website-visitor|visitors]] in the moment. [2]

✓

Eloqra is a lightweight live-chat tool that forwards each visitor message to the owner on Telegram and uses [[http-polling]] for real-time delivery instead of a [[websocket]].

How live chat works

A website owner installs live chat by pasting a small snippet of Embed Code that boots a JavaScript Widget. The widget shows a Chat Launcher bubble; clicking it opens the Live Chat Widget, often after a configurable Welcome Message. When a Website Visitor sends a Chat Message, it is delivered to a Support Operator who replies in real time. ^[2] Some products keep the widget isolated from host-page styles using Shadow DOM, and deliver new messages either over a persistent WebSocket or by HTTP Polling every few seconds. Eloqra, for example, polls roughly every 4-5 seconds and relays messages to the owner through a Telegram Integration rather than a separate web dashboard.

Why it matters for support and sales

Live chat is fast and convenient because it gives instant, in-context help without the back-and-forth of phone or email queues. ^[2] It also lets a single agent handle several conversations at once, which improves throughput compared to one-call-at-a-time phone support. ^[2] On the customer side, expectations are steep: Zendesk reports that roughly 28% of customers expect a chat reply within five minutes. ^[1] On the design side, Nielsen Norman Group recommends a clearly labelled launcher in the bottom-right corner, distinct colors for each speaker, and visible typing or timestamp cues so people are not left guessing. ^[3] Beyond support, chat is a natural Lead Capture surface that turns curious visitors into contacts.

Live chat vs. ticketing and async messaging

Live chat is synchronous: both people are present and expect near-instant turns, unlike a Ticketing System built around a Support Ticket that may be answered hours later. ^[4] Many teams blend the two, letting a chat that cannot be resolved live convert into a ticket or move to Asynchronous Messaging so the Conversation continues over hours or days. Heavier platforms layer on a Shared Inbox, canned responses, Conversation Assignment, and CSAT surveys. Smaller tools deliberately stay minimal: Eloqra, for instance, records the first operator to reply as the assigned agent (simple first-responder assignment) and does not ship SLAs, queues, or tags. Picking the right depth depends on your Ticket Volume and team size.

Sources & References

Zendesk: Live chat support - benefits and best practices ↗

Zendesk: Live chat software - definition and how it works ↗

Nielsen Norman Group: The User Experience of Customer-Service Chat ↗

Help Scout: Live Chat Best Practices for Customer Service Teams ↗

Last updated: June 25, 2026

Related Terms

Live Chat Widget

A live chat widget is the embeddable, in-browser chat interface a website loads from a small script so visitors can message a business in real time without leaving the page. In Eloqra it is a floating launcher and chat panel that boots from a single <script> tag and renders inside a Shadow DOM.

Conversation

A conversation is the threaded exchange of messages between a single website visitor and a project's operators, grouped as one unit with a status and unread counters. In Eloqra it is the container that holds every message, the visitor's captured context, and the assigned operator.

Support Operator

A support operator is the human on your side of a live chat who reads visitor messages and replies to them. In Eloqra the operator is whoever has access to the project's Telegram chat or Mini App inbox and answers incoming conversations from there.

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.

Ticketing System

A ticketing system is software that turns customer requests into trackable tickets, then helps a support team categorize, prioritize, assign, and resolve them through a defined lifecycle. It centralizes inquiries from many channels into one queue with status, ownership, and reporting.

Conversational Support

Conversational support is a customer-service model where help happens as an ongoing, natural-language dialogue between a customer and a business rather than a series of disconnected, ticket-style exchanges. The conversation and its context persist across channels and over time, so each reply builds on what came before.

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