TL;DR

A typing indicator is the little animated dots that show the other person is writing a reply; in Eloqra both the visitor and the operator get one, driven by short HTTP polling rather than a live socket.

Key Points

✓

It mirrors a face-to-face cue, the awareness that someone is about to speak, so the waiting party stays in the [[conversation]] instead of leaving or sending duplicate messages [3].

✓

Eloqra has typing indicators in both directions: the [[website-visitor]] sees the [[support-operator]] typing, and the operator sees the visitor typing.

✓

Because Eloqra uses [[http-polling]] (~4-5s) and not a [[websocket]], the [[live-chat-widget]] pings a /typing endpoint and learns about the other side's typing on its next poll rather than instantly [4].

✓

A typing cue is a softer signal than a [[read-receipt]]: it says a reply is being written now, not just that a [[chat-message]] was seen.

✓

It directly addresses perceived wait time, which UX research frames around hard response-time limits of roughly 0.1s, 1s, and 10s for holding attention [1].

✓

Operators replying through [[telegram-integration]] can still trigger the visitor-facing typing state, so the cue stays useful even though Eloqra has no always-open connection.

What a typing indicator is

A typing indicator is a small real-time signal, most often an animated ellipsis of three pulsing dots, that appears while the other participant is composing a Chat Message ^[3]. It re-creates a cue we rely on in person: the sense that someone is about to respond, which keeps the waiting party engaged and discourages them from firing off duplicate messages or abandoning the thread ^[3]. The pattern is now standard across consumer messaging and live chat alike, so visitors arriving at a Live Chat Widget expect it. In Eloqra the indicator is bidirectional and sits alongside other presence cues like the Welcome Message and an optional Read Receipt-style seen state, giving both the visitor and the Support Operator a lightweight sense of the other person being present.

How Eloqra drives it over polling

Eloqra's real-time layer is HTTP Polling, not a WebSocket: the Live Chat Widget requests /messages every few seconds and pings a /typing endpoint to publish and read typing state ^[4]. So when a Website Visitor starts typing, the widget posts that to Eloqra, and the operator sees it after their side's next poll; the reverse happens when an operator is composing. This means the cue is near-real-time rather than instant, arriving on the same short, predictable interval as new messages. Typing events are deliberately cheap to send, which is why polling-based products can afford to ship them frequently ^[4]. The trade-off is a small lag of a few seconds, acceptable for a Conversation where the goal is reassurance, not millisecond precision.

Why it matters for waiting

Waiting on a reply is where chat experiences fray, and a typing indicator is one of the cheapest ways to manage that. UX research on interaction sets three response-time limits, roughly 0.1 second for feeling instantaneous, 1 second for keeping thought flow, and about 10 seconds before attention drifts, after which users want feedback that the system is still working ^[1]. A typing cue is exactly that feedback: it tells the visitor an answer is coming so they hold the tab open. Some vendors gate it, Intercom only shows the agent-typing cue once that teammate has already replied in the thread, to avoid confusing customers ^[2]. Eloqra keeps its model simpler and bidirectional, pairing the indicator with first-responder Conversation Assignment so the first operator to engage is the one whose typing the visitor sees.

Sources & References

Response Time Limits: 3 Important Limits (Nielsen Norman Group) ↗

Real-time messaging explained (Intercom Help) ↗

What are typing indicators? (Sendbird) ↗

How a Typing Indicator Enables Chat Engagement (PubNub) ↗

Last updated: June 25, 2026

Related Terms

Read Receipt

A read receipt is a visual cue that tells the sender of a message that the recipient has opened and viewed it, usually shown as a 'Seen' label, a colored check, or a timestamp. In live chat it closes the loop between sending a message and knowing it landed.

Chat Message

A chat message is a single text exchange inside a live-chat conversation, sent by either a website visitor or a support operator. In Eloqra each message is stored with a direction (In or Out) and an author (Visitor or Operator), and belongs to one Open or Closed conversation.

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.

HTTP Polling

HTTP polling is a real-time technique where the client repeatedly sends HTTP requests on a fixed interval to ask the server whether new data is available, instead of holding a persistent connection. Eloqra's chat widget uses short polling roughly every 4-5 seconds to fetch new messages and typing state.

WebSocket

WebSocket is a protocol (standardized as RFC 6455) that opens a single, persistent, full-duplex connection between a browser and a server, letting either side push data at any time without re-issuing HTTP requests. It is the transport many real-time apps reach for when they need low-latency, bidirectional messaging.

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.

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