TL;DR

The chat launcher is the floating bubble in the corner of your site that visitors tap to start chatting; in Eloqra it sits inside a Shadow DOM and opens the chat window.

Key Points

✓

The launcher is the visible trigger for a [[live-chat-widget]] — a floating bubble that expands into the chat panel where a [[website-visitor]] can send a [[chat-message]].

✓

Convention (and usability research) puts it in the bottom-right corner, contrasting with the page so it is easy to find. [1][3]

✓

In Eloqra the launcher is configurable: position (bottom-right or bottom-left), color palette, and a toggleable "Powered by Eloqra" label.

✓

Eloqra renders the launcher and panel inside a [[shadow-dom]] so host-page CSS never leaks in and breaks the button's styling. [4]

✓

Opening the launcher can surface a [[welcome-message]] greeting and, if configured, a [[pre-chat-form]] to capture name and email before the first message.

✓

On mobile the launcher is typically fixed to the bottom corner and should never cover navigation, checkout controls, or sticky bars. [2][3]

What the Launcher Does in Eloqra

In Eloqra the chat launcher is the floating bubble that a website owner gets simply by pasting the tiny script tag (with ELOQRA_CHAT_CONFIG = { projectId }) into their page. When the script boots, it injects the launcher into a Shadow DOM so the host site's CSS cannot leak in and distort the button. ^[4] Clicking the bubble expands the Live Chat Widget panel; the visitor types and sends a Chat Message that opens a Conversation. Because Eloqra uses HTTP Polling rather than a persistent socket, the open panel quietly polls for new replies every few seconds. You can configure the launcher's corner (bottom-right or bottom-left), its color palette, the greeting it shows, and whether a small "Powered by Eloqra" credit appears.

Placement and Discoverability

The launcher only works if visitors can find it. Usability research from Nielsen Norman Group recommends putting the floating button on the right side of the page and giving it strong visual contrast, because side buttons in non-standard positions are routinely overlooked. ^[1] HelpCrunch and other vendors echo that the bottom-right corner is the default because it matches the natural end-point of left-to-right reading and usually sits over empty page space. ^[3] Eloqra defaults to this convention while still letting you flip the launcher to the bottom-left. Whatever the position, the button should never obscure key controls — navigation, checkout, or mobile sticky bars — and a recognizable speech-bubble icon helps visitors understand it is chat at a glance. ^[2]^[3]

From Launcher to Conversation

The launcher is the first step of a short pipeline. A click opens the panel, optionally shows a Welcome Message, and may present a Pre-Chat Form to capture the visitor's name and email. The first message a Website Visitor sends triggers Eloqra to capture page URL, device, and IP-based geolocation, then forward the message to the project owner over Telegram. The owner replies from Telegram or the Mini App inbox, and the answer flows back through a webhook to the same open widget the launcher revealed. There is no queue or routing in Eloqra — the first operator to reply becomes the assigned agent. In short, the launcher is the lightweight doorway that turns a passive page view into a two-way Conversation.

Sources & References

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

Set up and customize the Messenger — Intercom Help ↗

Live Chat Button: How to Install It and Talk to Your Customers Today — HelpCrunch ↗

Using shadow DOM — MDN Web Docs ↗

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.

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.

Welcome Message

A welcome message is the pre-written greeting a live-chat widget shows when a visitor opens it, used to set a friendly tone and prompt the first reply. In Eloqra it is a configurable line of text rendered inside the chat panel before any operator is involved.

Pre-Chat Form

A pre-chat form is a short form shown before a live chat starts that asks the visitor for a small amount of identifying information, typically their name and email. In Eloqra it is the optional collectVisitorInfo step that gates the chat input until the visitor submits their details.

Shadow DOM

Shadow DOM is a browser API that attaches a hidden, self-contained DOM subtree to an element, with its own scoped styles that neither leak out to the host page nor get overwritten by it. [1] Eloqra renders its entire chat widget inside a shadow root so the host site's CSS can never break the widget, and the widget's CSS can never alter the host site.

Telegram Integration

Telegram Integration is the mechanism by which Eloqra routes every website chat into the project owner's Telegram, forwarding visitor messages to a Telegram bot and flowing operator replies back to the widget. It turns Telegram into the operator inbox, so there is no separate agent console to keep open.

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

Chat Launcher