Quick answer
A chat widget is the small chat window embedded in a web page: a launcher button in a corner that opens a conversation with a live agent or bot. Whether it is used depends on three choices: where it sits, what makes it open (nothing, a teaser, a timed invite), and the first line it shows.
What is a chat widget?
A chat widget is the chat window that lives inside a web page. In its closed state it is a small launcher (a round button or a tab) fixed to a corner of the screen; when a visitor clicks it, a window opens where they can message a live agent or a bot. A script on the page loads it and connects it to a chat service. "Chat widget", "chat bubble" and "chat launcher" are the same thing seen from different angles.
The widget is the visitor-facing surface. The conversation system behind it, with agents, routing and history, is live chat, and that is not repeated here. The thesis of this page: whether the widget is used depends on three small choices, where it sits, what makes it open, and what its first line says, and each can be measured.
What are the parts of a chat widget?
| Part | What it is | What to decide |
|---|---|---|
| Launcher | The button or tab in the corner | Position, color, label, whether to show on phones |
| Teaser | A small card above the launcher | Whether to show one, and its text |
| Window | The conversation panel | Brand name, logo, language, light or dark |
| Greeting | The first line inside the window | Different text when agents are online or offline |
| Invite | A message that opens on its own | Which pages, after how many seconds, how often |
| Presence signal | A dot or status line | Whether it tells visitors someone is online |
Where should it sit, and when should it open?
| Choice | Options | What it costs the visitor | Use when |
|---|---|---|---|
| Position | Bottom right | Nothing by default; collides with cookie banners and sticky bars in that corner | The default for left-to-right languages |
| Position | Bottom left | Nothing; slightly less expected | The right corner is already used |
| On phones | Show | Covers part of a small screen | Support is a main reason people visit |
| On phones | Hide | Loses phone visitors who want help | Checkout or app-install bars would be covered |
| Trigger | None (launcher only) | None | Safe default; low open rate |
| Trigger | Teaser card a few seconds after arrival | Low: small card, easy to ignore | Pages where people look for help |
| Trigger | Timed invite on specific pages | Medium: it interrupts reading | High-intent pages such as pricing |
| Trigger | Agent writes to a live visitor | High: a person is watching them | Valuable visitors, with a human ready |
A good default is: bottom right, a launcher everywhere, one invite on the one or two pages where visitors have questions, and nothing on pages where an interruption costs more than it earns (checkout payment step, a form in progress). For writing and timing invites in detail, see proactive chat invites and the glossary entry on proactive chat.
What should the first message say?
The first line has one job: make replying easy. Two versions of the same invite for a pricing page:
- Weak: "Hello! How can we help you today?" It is open-ended and could come from any site.
- Stronger: "Comparing plans? Ask us anything about what is included. We reply in a few minutes." It names what the visitor is doing and sets a time expectation.
Rules of thumb: refer to the page, keep it under about 20 words, ask a question that can be answered in one line, and change the text outside office hours ("Leave your question and email; we reply tomorrow") rather than showing a greeting nobody will answer.
How do you measure a widget?
Three numbers describe a widget or one of its invite rules:
| Metric | Formula | What it tells you |
|---|---|---|
| Open rate | opens ÷ impressions | Whether the prompt is noticed and judged relevant |
| Reply rate | replies ÷ impressions | Whether it started a real conversation |
| Replies per open | replies ÷ opens | Whether the first line made it easy to answer |
Add two counts that live in the chat system: conversations started, and the share of those that get a human answer quickly.
Sample data: two invite rules over 30 days.
| Rule | Impressions | Opens | Open rate | Replies | Reply rate | Replies per open | Impressions per reply |
|---|---|---|---|---|---|---|---|
| A: pricing page, after 20 s | 1,400 | 98 | 7.0% | 42 | 3.0% | 42.9% | 33.3 |
| B: blog posts, after 10 s | 6,000 | 90 | 1.5% | 24 | 0.4% | 26.7% | 250.0 |
Recomputation: 98 ÷ 1,400 = 7.0%; 42 ÷ 1,400 = 3.0%; 42 ÷ 98 = 42.9%; 1,400 ÷ 42 = 33.3. For rule B: 90 ÷ 6,000 = 1.5%, 24 ÷ 6,000 = 0.4%, 6,000 ÷ 24 = 250.
The decision: rule B interrupts 6,000 readers to start 24 conversations, 250 interruptions per conversation, 7.5 times as many as rule A (250 ÷ 33.3). Retire B or move it to a page with questions. Keep A and test a better first line, since 57% of the people who opened it did not reply (1 − 42.9%).
What should you check for accessibility and speed?
- Target size. WCAG 2.2 success criterion 2.5.8 sets a minimum target size of 24 by 24 CSS pixels for pointer targets such as the launcher.
- Focus not hidden. Success criterion 2.4.11 requires that a keyboard-focused element is not entirely covered by content you added. A launcher or open window must not sit on top of a focused link or button.
- No layout shift. The launcher should be fixed to the viewport (CSS
position: fixed) so it does not push content. Google's web.dev treats a cumulative layout shift of 0.1 or less as good; test with the widget on. - Load after content. Load the widget script asynchronously so the page is usable first.
- Do not cover primary actions. On a phone, check the launcher against "Buy", "Next" and cookie buttons.
Common mistakes
- Opening an invite on every page. Most pages have no questions to answer.
- Triggering within a few seconds, before anyone has read anything.
- A greeting that promises a fast answer outside office hours.
- A window that blocks the checkout button on phones.
- Judging a widget by "messages received" alone, with no impressions to divide by.
- Never retiring rules: each unanswered invite is a small cost to the reader.
- Asking for an email before the visitor can type a question.
Chat widget settings in TapCub
Use the example above on your own site:
- Turn it on. If the analytics script is already installed, open Live chat › Chat settings › Appearance, switch on Enable live chat and save. Reload the site and the bubble appears; no second snippet. To keep it off a page, add
data-chat="false"to that page's script tag. - Set position and phones. On Appearance choose bottom right or bottom left, set brand name and color, and decide whether to Hide bubble on mobile (under 640 pixels or a mobile browser).
- Write the first lines. On Live chat › Chat settings › Greeting & translation there is one greeting for when agents are online and one for offline, plus a bubble teaser that appears about 4 seconds after arrival, once, and not to visitors who already have a conversation.
- Add invites. On Live chat › Chat settings › Proactive invites, set a page match, a dwell time of 3 to 600 seconds and text up to 300 characters. The rule list shows impressions, open rate and reply rate, which is the table in the example: retire the line nobody answers.
- Check the outcome. Live chat › Reports shows conversations, resolution rate, first response, satisfaction and hot pages (where chats started); Conversion attribution compares visitors who chatted with those who did not.
TapCub's widget has no pre-chat form; if you need an email, ask in the conversation or use the offline message.
Sources
- W3C, Web Content Accessibility Guidelines (WCAG) 2.2, success criteria 2.5.8 Target Size (Minimum) and 2.4.11 Focus Not Obscured (Minimum).
- web.dev, Cumulative Layout Shift (CLS).
- MDN Web Docs, position (CSS).
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Product Experience Specialist
Writes about product experience, practical workflows, and growth, turning complex processes into clear steps for everyday decisions.