Short answer: every widget on this list will put a working chat bubble on your website this afternoon, and several do it for free. The differences that matter at month six are the ones nobody demos: which domains may mount the widget, what the pre-chat form is allowed to ask, who answers first (a person, a bot, or both in order), where the transcript lives after the visitor closes the tab, and whether the invoice is one line or a seat count. This guide walks those six axes across Tidio, LiveChat.com, Intercom, Crisp, Tawk.to, and Devotel Orbit's native web chat, then says plainly where standalone widgets win and when folding chat into a CPaaS inbox is the better call.
Vendor columns below describe each product's public positioning as of October 2026: the shape of its install, its published feature tiers, and its pricing model at a high level. Check current published pricing pages before deciding; the Orbit column cites shipped settings you can open in the product today.
The vendor matrix
| Vendor | Install and domain control | Pre-chat form | AI first-line, human hand-off | Mobile and in-app parity | Transcript continuity | Billing shape |
|---|---|---|---|---|---|---|
| Tidio | Snippet plus a deep CMS plugin bench (WordPress, Shopify, Wix) | Configurable pre-chat questions on published tiers | Lyro AI agent add-on with hand-off to the shared inbox | Web-first positioning; in-app needs separate tooling | Conversations stay inside Tidio's inbox; CRM sync via integrations | Free entry tier, then paid plans; the AI agent is priced on top |
| LiveChat.com | Script snippet and a partner/plugin ecosystem | Published pre-chat survey with configurable fields | Bot add-ons from the same vendor family, routing into the agent app | Publishes a mobile SDK for in-app chat | Ticketing and reporting inside LiveChat; customer data via integrations | Per-agent seat licensing |
| Intercom | Snippet with a customizable launcher | Lead-capture bots and custom bots gather detail up front | Fin AI agent answers first, billed per resolution, escalation to humans | First-party mobile SDKs | Intercom is the system of record; the CDP is Intercom's own | Per-seat platform fee plus per-resolution AI usage |
| Crisp | Single script, fast self-serve setup | Pre-chat form on published tiers | Chatbot builder on paid tiers, hand-off to the shared inbox | Web and messaging channels; mobile apps for operators | Crisp inbox holds the history; per-workspace data model | Flat per-workspace pricing, not per-seat |
| Tawk.to | Free script, broad CMS plugin coverage | Offline and pre-chat form basics | Paid AI add-on; hired human agents as a service | Web-first; the free tier is the product | History lives in Tawk.to; export available | Free core, paid add-ons (branding removal, hired agents, AI) |
| Devotel Orbit | One-line snippet or CSP-friendly loader from the Install tab, plus a tenant-owned origin allowlist | Field builder with five types, required flags, and a 12-field cap; answers attach to the conversation | Any published AI agent fronts the widget; unresolved threads hand off to the shared inbox with the transcript | Native mobile SDKs and an in-app messaging channel on the same inbox | Every thread lands in the shared inbox attached to the customer profile | One usage-based bill across chat, SMS, WhatsApp, email, and voice |
Read down any column and the pattern is visible: the standalone vendors are strong at the bubble and honest about being a bubble. Identity, journeys, and the rest of the channel mix live in integrations. Orbit's column is the opposite bet: the widget is one ingress into a platform that already owns the profile, the queue, and the other channels.
Installation snippet and domain allowlist
All six install the same way in spirit: a script tag on your pages, or a plugin that injects it for you. Tidio and Tawk.to lean hardest on the CMS plugin bench, which is a genuine advantage if your site is WordPress or Shopify and nobody on the team touches HTML. Orbit's Install tab hands you two forms of the same embed: a single-line HTML snippet for the page head, and a dynamic loader for sites whose content security policy forbids third-party script tags. The bundle serves from Orbit's CDN and carries your organization's widget identifier, so one snippet is correct on every page.
The control that separates the six is what happens on domains you did not approve. A snippet is copyable: a scraper or a phishing look-alike can mount your widget and mint conversations in your inbox. Orbit's Privacy tab ships an origin allowlist, the explicit list of origins allowed to mount the widget, with a separate confirmed opt-in if you deliberately want an open posture. That is a tenant-owned control, not a support ticket. The standalone vendors generally treat the snippet as public by design and handle abuse reactively; if widget impersonation is in your threat model, compare the published controls before you care.
Pre-chat form fields
Pre-chat forms decide whether your team opens a conversation with a name and a reason, or with a blank page. Tidio, LiveChat, Intercom (via bots), Crisp, and Tawk.to all collect detail up front in some tier; the depth and the tier it sits on vary, so check the current plan pages.
Orbit's pre-chat form is a field builder rather than a fixed template. The Pre-chat tab lets an owner or admin compose up to twelve fields from five types (short text, email, phone, dropdown, long text), mark each required or optional, set placeholders and dropdown options, reorder the list, and give the form its own heading and submit label. An enabled form must have at least one labeled field before it can save, and dropdowns must carry at least one option, so a half-configured form can never ship to visitors. The answers attach to the conversation before routing, which is the detail that matters downstream: triage reads the reason, and the profile gains the email.
AI agent first-line, human hand-off
Every vendor on this list now puts an AI agent in front of the queue, and the commercial models differ more than the feature lists: Intercom prices Fin per resolution, Tidio prices Lyro as an add-on, Tawk.to prices AI and human agents as services, and LiveChat routes you toward a companion bot product. Orbit's model is different in shape: the widget does not ship a separate bot product, it mounts one of the AI agents you already publish on the platform. The Branding tab names which AI agent fronts the widget (or none, if the team prefers humans first), the agent answers from the same knowledge and guardrails it uses on every other channel, and anything it cannot resolve hands off to a human in the shared inbox with the full transcript attached. One agent definition, every channel, instead of a widget-specific bot to maintain.
Mobile SDK and in-app parity
A website widget only meets visitors who are on the website. If your product has an app, the chat surface has to follow. Intercom and LiveChat publish first-party mobile SDKs, and that is a real point in their favor for app-first teams. Tidio, Crisp, and Tawk.to are web-first by positioning; in-app chat means another vendor. Orbit ships native mobile SDKs and an in-app messaging channel that works the same shared inbox as web chat, so a conversation that starts in the browser widget can continue in the app without a second transcript.
Transcript-to-profile continuity
This is the axis that decides what your data looks like in a year. In the standalone tools, the transcript lives in that tool's inbox and reaches your CRM through an integration you configure and maintain; the chat history and the customer record are two systems agreeing with each other. In Orbit, a web chat thread is simply a conversation on the shared inbox, attached to the customer profile the platform already maintains: same identity, same history as the SMS, WhatsApp, email, and voice threads that customer generates. Pre-chat answers, page context, and the hand-off note all land on the same record the next channel will read.
One bill versus per-widget seats
Standalone pricing shapes: Tawk.to's free core with paid add-ons, Tidio and Crisp entry tiers that grow into paid plans, LiveChat's per-agent seats, Intercom's seat fee plus per-resolution AI meter. None of these is dishonest; the issue is stacking. A widget seat, a bot meter, a help-desk seat, a CDP contract, and an SMS validator are five renewals that never share a customer record. Orbit bills per message on one usage-based statement that already covers the channels you run, and the web chat widget rides on it without a separate licence line.
What a chat widget actually owns: identity and hand-off
Strip the feature pages away and a chat widget owns exactly two things. It owns the first moment of identity: the name, email, and reason a visitor volunteers before the conversation starts. And it owns the hand-off: the rule for when a bot stops and a human begins, and what the human receives when that happens. Everything else (colors, position, greeting copy) is decoration.
Judge a widget on those two axes. A pre-chat form that cannot mark a field required, or whose answers never reach the person answering, wastes the identity moment. A hand-off that drops the transcript, or routes the thread to a queue that cannot see the customer's other conversations, wastes the second. The matrix above is those two questions asked six times.
Where standalone widgets win
Credit where it is due. Tawk.to's free core is the right answer for a site that needs a bubble and a human on the other end, full stop, at zero cost. Tidio's and Crisp's entry tiers, and Tidio's CMS plugin bench, suit a solo operator on WordPress or Shopify who wants chat today without a platform decision. LiveChat is a fine specialist choice for a support team that already has its CRM, CDP, and messaging vendors settled and only needs the website leg. Intercom's Fin, priced per resolution, is an honest fit for teams that live in Intercom already. If your program is "a chat bubble on the marketing site," buying a platform to get one is overbuying, and this post says so.
When to fold chat into the CPaaS inbox
The fold happens when any of these becomes true:
- The support team already works WhatsApp, SMS, or email in a queue, and the website thread is the only conversation living in a separate tool.
- The business wants the chat transcript on the same customer record as the order history, the SMS thread, and the call outcome, without maintaining an integration.
- An AI agent should front more than the website: the same knowledge and guardrails on voice, WhatsApp, and web, maintained once.
- Compliance needs tenant-owned controls over the widget: which origins may mount it, what the pre-chat form asks, which hours it offers, and what the privacy copy says. Orbit's native chat settings put each of those in the tenant's hands (origin allowlist, pre-chat builder, business hours, and a Privacy and GDPR tab), which matters when your regulator or your DPA cares who controls the surface.
- The renewal calendar has become a stack of seat counts and per-bot meters, and finance wants one usage-based bill.
None of those is a widget failing at being a widget. They are the moments the widget stops being the whole program and becomes one channel among several, at which point the channel belongs in the inbox that works the rest.
Worked example: pre-chat capture flowing into a CDP journey
A visitor reads the pricing page and opens the widget. The pre-chat form asks three things: name (short text, required), work email (email, required), and a dropdown, "What brings you today?", with options like pricing question, setup help, and something else. She picks pricing question and starts the chat.
The AI agent named on the Branding tab answers first from the published knowledge base, cites the pricing page, and offers the relevant plan math. She asks a follow-up the agent is not sure about, and the thread hands off to a human with the transcript, the three pre-chat answers, and the page context attached. The agent in the shared inbox does not re-ask her name or her reason; the inbox shows both, alongside every other conversation tied to that email.
Behind the scenes the email resolves against the customer profile. If she is known, the thread attaches to her existing record and the human sees her SMS and email history before replying. If she is new, the profile is created from the pre-chat answers at first touch. Either way, the dropdown answer ("pricing question") and the page context sit on the profile as signals the CDP can act on: an audience of pricing-question conversations from the last seven days, enrolled in a journey that sends a follow-up email the next morning and, if she has opted in to SMS and quiet hours allow, a short text with a link back to the same thread. The follow-up uses the same channels, the same consent records, and the same bill as the chat that started it. That loop, capture to answer to hand-off to profile to journey, is the part no standalone widget closes on its own, because the journey engine and the channel layer live in other vendors' systems.
Frequently asked questions
Is Tawk.to really free, and what is the catch?
The core widget is free, and for a site that needs a bubble with a human behind it that is a legitimate zero-cost answer. Revenue comes from paid add-ons: branding removal, hired agents who answer for you, and AI. The catch is not a trick; it is that transcript history, customer identity, and your other channels remain separate systems you connect yourself.
Can the Orbit web chat widget hand off to a human?
Yes. The widget can front a published AI agent, and anything the agent does not resolve lands in the shared inbox as an ordinary conversation with the full transcript, where a human continues it. Teams can also run humans first by leaving the AI agent unassigned.
What stops someone from mounting my widget on a site I do not own?
On Orbit, the origin allowlist in the Privacy tab: only origins you list may mount the widget, unless you deliberately confirm the open posture. Treat any vendor's default-snippet behavior as a question to ask before signing, not after an incident.
Where do pre-chat answers go in Orbit?
They attach to the conversation before routing, so the first human reply already has them, and the captured identity (typically the email) feeds the customer profile the platform maintains across every channel.
Related reading
- What is live chat, and where does handoff belong? defines the channel and the hand-off contract this guide assumes.
- Web Chat as an owned channel explains why a website thread has no carrier leg and what that means for delivery.
- Orbit vs Crisp and Orbit vs Intercom go deeper on the two vendors whose overlap with Orbit is largest.