Quick answer
A chat box is the window where a conversation happens: a header, a scrolling list of messages and an input field. On a website it opens from a small button, called the chat bubble; the whole embedded component is the chat widget.
What is a chat box?
A chat box is the window where a conversation happens: a header, a scrolling list of messages, and a field where you type. On a website it usually opens from a small button in a corner, and the same name is used for the message area inside a chat app or a chat room.
The word is loose. Some sources use "chat box" for the whole popup on a page, others only for the message area inside it. When you read a requirement or a vendor page, check which one is meant, because the checks for a launcher button and for a message list are different. This page uses the narrower meaning, the window itself, and keeps the launcher button separate. For the embedded component as a whole, with its position and trigger choices, see chat widget.
Chat box vs bubble vs widget vs live chat vs chatbot vs chat room
These six words overlap in everyday use. Here is one way to keep them apart.
| Term | What it refers to | Example sentence |
|---|---|---|
| Chat box | The window with messages and an input field | "The chat box shows the last five messages." |
| Chat bubble (launcher) | The button that opens the chat box | "The chat bubble sits bottom right." |
| Chat widget | The whole embedded component: bubble, teaser, chat box | "We load the chat widget on every page." |
| Live chat | A conversation with a person in real time | "Live chat is staffed 9 to 6." |
| Chatbot | Software that replies automatically | "The chatbot answers from the help centre." |
| Chat room | A shared space with many participants | "Everyone in the chat room sees each message." |
The first three describe the interface and the last three describe who or what is on the other end. A chat box can show live chat, a chatbot or both, and the same chat box looks the same to the visitor either way. For an article on the app side, see live chat app.
Anatomy of a chat box
A working chat box has the same seven parts in almost every product. Use the table as a checklist when you review one.
| Part | What it does | What to check |
|---|---|---|
| Header | Shows who you are talking to: a name, a logo or avatar, a subtitle | The name matches the brand; the logo is sharp at small sizes |
| Status line | Says whether people are online and when they usually reply | It changes when no one is available |
| Message list | Shows the conversation, newest at the bottom | New messages scroll into view; the list can be read with a screen reader |
| Greeting | The first message or prompt | It differs when agents are online and when they are not |
| Input field and send button | Where the visitor types and sends | A visible label or placeholder; the send button is big enough to tap |
| Notices | Short legal or system text, such as that a conversation is recorded | It links to the privacy policy |
| Footer and exit | Brand line, close button, option to open in a new window | The close button is easy to find and big enough to tap |
When the agents are away, the box often turns into something else: a form that collects an email address and a question. That is still the same chat box in a different state, and it needs the same checks.
The states a chat box moves through
A chat box is not one screen, it is a handful of states, and each needs a design.
- Closed. Only the launcher is visible, sometimes with a presence dot showing that someone is online.
- Teaser. A short card appears above the launcher. It should be easy to dismiss.
- Open, agents online. The greeting for online hours, the message list and the input.
- Open, agents offline. A different greeting and, usually, a form for an email and a question.
- In conversation. Messages move both ways; the box needs a way to show that a message was sent.
- Resolved and returning. After a conversation is closed, a visitor who writes again soon after should return to the same thread rather than start a new one.
When you test a chat box, step through all six, not only the happy path where an agent answers at once.
Accessibility checks: target size and status messages
Two success criteria from the Web Content Accessibility Guidelines (WCAG 2.2) apply directly to a chat box.
Target size. Success criterion 2.5.8 (Level AA) requires pointer targets to be at least 24 by 24 CSS pixels. A target smaller than that can still pass if a 24-pixel circle centred on it does not overlap another target or another undersized target's circle. The criterion also has exceptions for inline links, for controls whose size the browser sets and for another control that does the same job.
Worked example, sample data: a close button and a minimise button are each 20 by 20 pixels, side by side with a gap of g pixels. Each is undersized, so each gets a 24-pixel circle. The two circles do not overlap if the distance between the centres is at least 24 pixels. The centres are 20 + g apart, so the rule needs 20 + g ≥ 24, which gives g ≥ 4 pixels. Also, each circle must not reach the other button's box: the nearest edge is 10 + g from the centre and the circle's radius is 12, so g ≥ 2. The stricter of the two decides: a gap of at least 4 pixels, or make both buttons 24 pixels.
Status messages. Success criterion 4.1.3 (Level AA) requires status messages to be programmatically determinable through a role or property, so assistive technology can announce them without moving focus. Examples of status messages in a chat box are "Message sent", "Sending", and a count of unread messages. Whether an incoming message from a person is a status message is less clear in the criterion, so test with a screen reader that a new reply is announced.
Check one more thing with a keyboard: can you open the box, type, send and close it without a mouse?
How to measure a chat box
You cannot improve what a chat box shows if you do not count how often it is opened. Four counts cover most of it, using the sample below.
Sample data: a proactive invite is shown 1,000 times in a week. 90 visitors open the chat box and 27 of them send a message.
- Open rate = opens ÷ impressions = 90 ÷ 1,000 = 9.0%.
- Reply rate = visitors who write ÷ opens = 27 ÷ 90 = 30.0%.
- Messages started per 1,000 impressions = 27 ÷ 1,000 × 1,000 = 27.
Definitions differ between tools, so write down the denominator you use. A low open rate points to the launcher or the teaser; a high open rate with a low reply rate points to the greeting or to an input field that is hard to find.
Common mistakes with chat boxes
- Designing only the online state. Visitors arrive when nobody is there; the offline state needs a greeting and a way to leave a question.
- Using the same text for online and offline. "We reply in minutes" is false at 2 a.m.
- Covering page content on phones. A large open box can hide the page on a small screen. Many products offer an option to hide the launcher on narrow windows.
- Hiding the exit. A tiny or low-contrast close button traps people.
- Treating the interface language as translation. Setting a box to show buttons in one language does not translate what people write.
The chat box in TapCub
TapCub's chat box is part of the same script as its analytics, so it appears when you switch on live chat, with no second snippet.
- Header and look. In Live chat › Chat settings › Appearance set the brand name and subtitle, primary colour, a square logo of at most 200 KB, bubble position (bottom right or left) and dark mode (follow the system, light or dark). An empty brand name uses the site name.
- Greeting and states. In Live chat › Chat settings › Greeting & translation write one line for agents online and one for agents offline; the offline line is used outside office hours. A green presence dot shows on the bubble when an agent is online. When no one is available, visitors can leave an email and a question, which land in Live chat › Chat settings › Offline messages.
- Teaser and invites. A bubble teaser appears about four seconds after arrival, once, and not for visitors who already have a conversation. Invite rules in Live chat › Chat settings › Proactive invites trigger after 3 to 600 seconds on a matching page, with text of at most 300 characters, and the list records impressions, open rate and reply rate.
- Notices. The bottom of the window says that the conversation is recorded, and the link beside it comes from the privacy notice URL you set. The Free plan keeps a clickable brand line at the bottom; Pro and above can remove it.
- Phones and exits. Hide bubble on mobile hides the bubble when the window is narrower than 640 pixels or the browser is a phone. Visitors can choose Open in a new window to continue the same conversation on a standalone page. The widget language setting chooses Chinese or English for buttons and prompts and does not translate messages.
Sources
- W3C, Understanding Success Criterion 2.5.8: Target Size (Minimum), WCAG 2.2: pointer targets at least 24 by 24 CSS pixels, with spacing, equivalent, inline, user agent and essential exceptions. Checked 2026-11-21.
- W3C, Understanding Success Criterion 4.1.3: Status Messages, WCAG 2.2: status messages must be programmatically determinable (Level AA). Checked 2026-11-21.
- TapCub documentation, chat install and appearance, proactive messages (docs.tapcub.com). Checked 2026-11-21.
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.