If you've spent any time browsing chat tools for your site, you've seen both phrases. "Live chat" gets thrown around for Intercom, Tawk.to, Drift. "Embedded chat" gets used for our category, for kits like Sendbird, for product-page comment widgets. The terms overlap enough that buyers end up comparing apples to oranges.
Here are the two definitions that actually hold up.
Live chat: 1:1 conversation with your team
A visitor lands on your page. A small bubble in the corner says "Hi! How can we help?". Visitor clicks, types a question, an agent on your team replies. The conversation is private to the two of them. When the visitor closes the page or comes back tomorrow, they pick up the same thread.
This is the Tawk.to / Crisp / Intercom / Drift / Tidio shape. It is fundamentally customer support:
- Built around an agent inbox. Your team logs in, sees pending threads, picks one up.
- Pricing usually scales with agent count, conversation count, or both.
- Empty-state default is "an agent will be with you shortly".
- SLA matters more than vibe.
Use it when: you have agents, your visitors have questions only your team can answer, the conversation is private (e-commerce returns, SaaS pre-sales).
Embedded chat: group chat on a website
A visitor lands on your page. They see a room — recent messages, people typing, reactions. They can read along, post, react, reply. Other visitors see them. The conversation is many-to-many.
This is our category. Discord-shaped chat, but living on your domain instead of theirs:
- Built around a room (or per-page rooms). Visitors see each other.
- Pricing usually scales by site, not per agent.
- Empty-state default is "Be the first to say hi" or a pinned message.
- Vibe matters more than SLA — the room has to feel alive.
Use it when: you run a content site, a livestream, a community storefront, a niche audience that wants to talk to each other (not just to you).
Where the categories overlap (the confusing middle)
Some tools advertise both. Crisp has a "team inbox" model (live chat) but added a "Status page chat" feature (closer to embedded). Tidio for Shopify has a customer-support bubble that can also surface other buyers' chats. The categories aren't sealed.
The honest signal: look at where the tool's marketing material spends most of its time.
- If most screenshots show an agent dashboard with a queue of tickets → it's a live-chat tool that bolts group on.
- If most screenshots show a room with avatars and reactions → it's an embedded-chat tool.
When to use both
Many storefronts run both. Tawk.to in the corner for "I have a return question" (1:1 support). Embedded Chat as a community section on the homepage / product pages for buyers to talk to each other ("does this run small?"). They don't conflict — they serve different user moments.
Picking
Ask three questions:
- Does your visitor want to talk to your team, or to other visitors? If "your team" only → live chat. If "other visitors" or "both" → embedded chat.
- Do you have an agent rota? If yes → live chat works. If no → live chat will mostly show "we'll get back to you" messages that erode trust.
- How many visitors do you expect chatting at peak? 1–5 concurrent → live chat. 5+ concurrent → embedded chat (it gets better with more people, while live chat just adds queue depth).
Practical examples
- Shopify store with a small team: probably both. Tawk.to / Tidio for returns inbox; embedded chat on community pages.
- Solo creator with a YouTube/Twitch audience: embedded chat on your site. Live chat is overkill — you're not running a support desk.
- SaaS with paid tiers: live chat for pre-sales + onboarding. Embedded chat doesn't fit unless you want a "community discussion" tab.
- Live-stream radio / podcast site: embedded chat. Live chat is the wrong shape entirely. See our Kniteforce case study.
Side-by-side comparison if you're picking between specific tools: Embedded Chat vs Tawk.to. The pricing-and-features table makes the category split very concrete.