Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Text S.A. (formerly LiveChat Software S.A.) · www.livechat.com

Report an error on this page Is this your product? →

Link to this page

LiveChat: AI-assisted analysis on whats-best.ai LiveChat: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

LiveChat at a glance

Vendor
Text S.A. (formerly LiveChat Software S.A.)
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates LiveChat 3/5, the mean of 6 judges. LiveChat, from Text S.A., is live chat and omnichannel customer-service software. how scores are made
As of
Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

LiveChat alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

LiveChat, from Text S.A., is live chat and omnichannel customer-service software. Its strongest areas are integrations at 7-8 and omnichannel at 7 with no spread: website chat, email, WhatsApp, Messenger, Instagram, Apple Messages for Business and SMS via Twilio land in one inbox, and the public API surface — REST and WebSocket, webhooks, SDKs, an MCP server — carries per-plan quotas. Sovereignty is the weak point, scored 4 with no spread: EU hosting is selectable with Frankfurt named on Google Cloud, but the captured pages name Text, Inc. of Boston, Massachusetts as the entity, the vendor participates in the EU-U.S. Data Privacy Framework, and we found no public information on a published subprocessor list. Judges spread on ticketing, 4-6: the low mark weighs the January 2025 sunset of native Tickets and accounts created after June 1, 2023 going to HelpDesk.com, while higher scores credit the documented queue rules. Pricing transparency spread 5-6 because omnichannel capabilities sit under Text pricing plans whose prices are not shown; customer data protection spread 5-6, with judges flagging the privacy policy's AI and machine-learning processing purposes.

Report an error

Speaks for it

  • Website chat, email, WhatsApp, Messenger, Instagram, Apple Messages for Business and SMS via Twilio land in one inbox, with transfer history preserved
  • Documented REST and WebSocket APIs, webhooks, SDKs, an MCP server and per-plan quotas of 10,000 calls a month on Essential and 20,000 on Growth, with extra calls at $29.50 per 100,000
  • Shopify orders, cart contents and payment status appear beside chats and tickets
  • Per-agent prices public with the billing period stated — Starter $19/user/month billed annually or $25 monthly, Team $49 or $59, Business $79 or $89 — plus a free 14-day trial with no credit card required
  • Data Processing Addendum with June 2021 Standard Contractual Clauses incorporated into the agreement automatically, and deletion of tagged chats or tickets documented with a verification code

Report an error

Held against it

  • Sovereignty scored 4 with no spread: the captured pages name Text, Inc. of Boston, Massachusetts as the entity, and we found no public information on a published subprocessor list with locations
  • The native Tickets feature was sunset in January 2025, accounts created after June 1, 2023 are directed to HelpDesk.com, and the captured pages give different pictures of ticketing today
  • Omnichannel capabilities sit under Text pricing plans not included in LiveChat plans, with those prices not shown and plan names differing between pages
  • Audit logs sit on the Enterprise plan only, and we found no public information on SLA policies with breach warnings or escalation
  • The privacy policy lists developing and improving artificial intelligence and machine-learning capabilities among its processing purposes

Report an error

Best for

  • You run a Shopify store and want order, cart and payment status beside the conversation while WhatsApp, Instagram and email share one queue
  • Your engineers build custom tooling and need documented APIs, webhooks, SDKs and an MCP server with published quotas and priced overage
  • You want to evaluate before committing, with a free 14-day trial that requires no credit card
  • You serve customers asynchronously and need a chat that continues by email when the visitor leaves the site

Report an error

Avoid if

  • You are buying a native ticketing engine — the help articles state the native Tickets feature was sunset in January 2025 and accounts created after June 1, 2023 are directed to HelpDesk.com
  • You must document an EU contracting chain — the captured pages name Text, Inc. of Boston, Massachusetts, the vendor participates in the EU-U.S. Data Privacy Framework, and we found no public information on a subprocessor list with locations
  • You need the full annual invoice before signing — ask the vendor: the public pages we read do not show it
  • Your data protection lead must approve every processing purpose — the privacy policy lists developing AI and machine-learning capabilities among them, and audit logs sit on the Enterprise plan

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Ticketing, queues & SLA 3 of 5
Channels in one queue 3.5 of 5
Knowledge base & deflection 3 of 5
Customer data protection 3 of 5
Integrations & API 4 of 5
European sovereignty 2 of 5
Pricing transparency 3 of 5

Ticketing, queues & SLA

Show reasoning
How this is scored

The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.

0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.

3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.

5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.

8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.

10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.

Report an error

The Support Lead

Tickets come with status, priority, owner and source, reassignment to agents or groups, duplicate threads merging into one, and first-response and resolution-time reporting by agent and group — enough to run and report on a real queue. I found no public information on SLA policies with breach warnings and escalation. The help centre also states the native tickets feature was sunset from January 2025 and that accounts created after June 1, 2023 are directed to HelpDesk.com tickets, so I would confirm exactly which engine carries my SLA before signing. 4 5 5 4

Report an error

The Agent Advocate

Routing rules by page, domain and country, ticket rules like priority customers skipping the line, four statuses with priority, owner and source pinned to every ticket, first-response and resolution reporting per group and per agent, and an MCP server that searches tickets and transcripts — that is a real engine. But no SLA policy with breach warnings or escalation appears anywhere in the captures, and the help pages say the native ticketing was sunset in January 2025 with accounts created after June 2023 pointed at HelpDesk.com, so I would verify exactly which engine I am buying. 4 5 5 11 4

Report an error

The Data Protection Officer

Tickets carry status, priority, owner and source, standing rules run automatically (priority customers skip the line, duplicates merge into one thread, follow-ups auto-solve after four days), and reports cover first-response and resolution time per agent and group. We found no public information on SLA policies per queue with breach warnings or business-hours escalation. The captured pages give different pictures of ticketing's future: one help article schedules the native Tickets feature for sunset in January 2025 with newer accounts pointed to HelpDesk.com, while other pages describe creating and managing tickets in the Text inbox. 4 5 5 4

Report an error

The Shop Operator

Tickets carry status, priority, owner and source, can be reassigned between agents or groups, auto-solve after four days of customer silence, and come with first-response and resolution-time reports broken down per agent and per group — that is a real engine, and the response-time clock documentation is what I check first. Rules let priority customers skip the line and merge duplicates into one thread, and a chat converts to a ticket that keeps its link to the originating conversation. What holds it back: we found no public information on SLA policies with breach warnings or escalation, and the help articles state the native Tickets feature was sunsetted in January 2025 by plan, with accounts created after June 1, 2023 directed to HelpDesk.com for ticket forwarding. 4 5 5 4

Report an error

The Integrator

Statuses, priorities, assignment to people or groups, and rules such as priority customers skipping the line and duplicate threads merging are documented, together with first-response and resolution-time reports per agent and group and working-hours routing. We found no public information on SLA policies with breach warnings or escalation paths. The captured pages also describe the native Tickets feature as sunset in early 2025, with accounts created after June 1, 2023 directed to HelpDesk.com, so a buyer should confirm which engine today's reports describe. 4 5 5 4

Report an error

The Skeptic

The help pages show a real engine — status, priority, owner and source on every ticket, rules such as priority customers skipping the line, and first-response and resolution-time reports — but they also record that the native Tickets feature was sunsetted in January 2025 and that accounts created after June 1, 2023 are directed to HelpDesk.com for ticketing. I found no public information on SLA policies with targets, breach warnings or escalation, or on search across tickets. Chat routing by page, domain or country is itself gated to the Growth and Enterprise plans. 4 5 5 4

Report an error

Channels in one queue

Show reasoning
How this is scored

Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.

0 — No customer channel of its own; the product only works on tickets entered by hand or by another system.

3 — Email turned into tickets, with a web form or one further channel.

5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.

8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.

10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.

Report an error

The Support Lead

Website chat, forwarded email, WhatsApp, Messenger, Instagram, SMS through Twilio and Apple Messages are documented landing in one inbox, with routing by page, domain or country and history preserved when a chat transfers to another agent. I found no public information on telephony integration with call logging or on a customer portal where a requester can see their own tickets. 5 6 5 6

Report an error

The Agent Advocate

Website chat, email, WhatsApp, Messenger, Instagram, SMS through Twilio and Apple Messages all land in one inbox, transfers keep the conversation history, and one customer profile holds the earlier threads — that is the one-screen answer I want. We found no public information on telephony with call logging, on a portal where a requester sees their own tickets, or on consent handling for the messengers. 5 6 5

Report an error

The Data Protection Officer

Website chat, email forwarded from Gmail or Outlook, WhatsApp, Messenger, Instagram, Apple Messages for Business and SMS via Twilio land in one inbox, with routing by page, domain or country and history preserved when a conversation transfers. Asynchronous messaging lets a customer leave mid-chat and continue by email, so the issue survives a channel change. We found no public information on telephony with call logging, a portal where requesters see their own tickets, or stated consent handling for the messenger channels. 5 6 5 6

Report an error

The Shop Operator

WhatsApp, Messenger, Instagram, SMS through Twilio, Apple Messages for Business and email all land as conversations or tickets in one inbox, with routing by page, country or phone number sending each to the right team — this is the WhatsApp-and-shop-in-one-queue test, and it passes. Better still for my people, Shopify orders, cart contents, recent orders and payment status show beside the conversation, so an agent answers "where is my parcel" without a second login. We found no public information on telephony with call logging or on a portal where a requester can see their own tickets, and consent handling is documented for the chat widget's pre-chat form rather than for the messengers. 5 5 6 1

Report an error

The Integrator

Website chat, forwarded email, WhatsApp, Messenger, Instagram, Apple Messages for Business and Twilio SMS are documented as landing in one inbox with unified customer profiles, and a transfer keeps the conversation history the next agent can read. We found no public information on telephony with call logging or a customer portal where a requester sees their own tickets, which is what would make channel choice an implementation detail. 5 6 5

Report an error

The Skeptic

Counting what actually shares the queue: website chat, WhatsApp, Messenger, Instagram, Apple Messages for Business and SMS via Twilio are all shown landing in one inbox with routing, email becomes tickets with duplicates merged, and a transferred chat carries its history to the next agent. I found no public information on telephony integration with call logging, on consent handling for the messengers, or on a portal where a requester can see their own tickets. 5 6 5 6 1

Report an error

Knowledge base & deflection

Show reasoning
How this is scored

Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.

0 — No knowledge base or self-service of any kind; the product is a ticket inbox only.

3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.

5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.

8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning that flag stale content, and reporting on which articles deflect.

10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.

Report an error

The Support Lead

KnowledgeBase delivers a public help centre with topics, public/internal/draft article states, images and embedded video, and articles reachable inside the agent app; Copilot suggests answers from policies during chats and email drafts are drawn from help-centre content, which is genuine deflection work. I found no public information on multilingual articles, review dates or content versioning, or on reporting that shows which articles deflect. 5 7 5 7 8

Report an error

The Agent Advocate

A help centre with topics and public, internal and draft states, Copilot pulling answers from my returns guide mid-chat, email drafts sourced from the help centre, and an AI resolution rate reported as a number — real deflection, not just filing. We found no public information on multilingual articles, versioning that flags stale content, or reporting on which articles deflect, and the knowledge base arrives as a separate product installed as a plugin. 7 5 5 14

Report an error

The Data Protection Officer

KnowledgeBase publishes a customer-facing help centre with topics, public/internal/draft article states and rich formatting, installable in the agent app where Copilot pulls answers from a returns guide mid-chat; the chat widget also suggests questions matched to the page a visitor is on. We found no public information on multilingual articles, versioning or review dates, or reporting on which articles deflect tickets. Deflection is reported as an AI resolution rate, not as article performance. 5 7 5 7 8

Report an error

The Shop Operator

A help centre with draft, internal and published article states, topics as categories, and an article editor is documented, and the KnowledgeBase plugin surfaces inside the agent app. Suggestion is real in both directions — Copilot pulls answers from the help centre while an agent chats, email replies are drafted from it, and the AI agent answers customers from those sources before any handoff, with a vendor-reported average AI resolution rate of 74 percent. We found no public information on reporting that shows which articles deflect, review dates or versioning that flags stale content, or multilingual articles. 5 7 5 7

Report an error

The Integrator

A customer-facing help centre with public, internal and draft article states and topic categories is documented, an AI agent answers from your help centre sources before an agent joins, and Copilot suggests answers from your policies while an agent replies. We found no public information on article versioning, review dates, multilingual articles, or reporting that shows which articles deflect contacts. 7 7 5 5

Report an error

The Skeptic

KnowledgeBase articles carry public, internal and draft states, sit under Topics, and install as a plugin inside the agent app, while Copilot pulls answers from the help centre during a chat and the email queue drafts replies from it. I found no public information on multilingual articles, review dates or versioning that flags stale content, or on reporting that shows which articles deflect. 7 8 5 5 7

Report an error

Customer data protection

Show reasoning
How this is scored

A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.

0 — The vendor's own terms state that ticket content is used for purposes beyond providing the service, or that a data processing agreement is not offered.

3 — A privacy policy and a data processing agreement (DPA) offered, with agent roles that limit what an agent can do.

5 — A DPA published or signable online, agent roles and group- or queue-level visibility, and deletion of tickets or of a requester's data documented in the help centre.

8 — Automatic retention or deletion rules per queue or data category, attachment handling stated, an audit log of agent access or changes, documented support for access and erasure requests, and redaction of ticket content.

10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.

Report an error

The Support Lead

The data processing addendum is incorporated into the agreement automatically with the June 2021 SCCs for EU/EEA customers, and deletion of tagged chats or tickets plus transcript delivery to the requester are documented procedures with verification codes. Roles limit who sees conversations and audit logs exist, but only on the Enterprise plan, and I found no public information on automatic retention rules per queue or redaction of ticket content. The privacy policy lists developing and improving AI and machine-learning capabilities among its processing purposes, which I would want legal to read against our DSGVO obligations. 2 9 10 13

Report an error

The Agent Advocate

The data processing agreement is incorporated automatically with the June 2021 standard contractual clauses for EU and EEA customers, roles run Owner, Admin and Member with permission-limited conversation access, and deletion is documented: tag the chats, email support, confirm with a verification code. But audit logs sit on the Enterprise plan only, we found no public information on automatic retention rules or redaction of ticket content, and the privacy policy lists researching, developing and training AI and machine-learning systems among its processing purposes — I would want that carved out in writing before archiving tickets here. 10 9 2 13

Report an error

The Data Protection Officer

A Data Processing Addendum with June 2021 Standard Contractual Clauses is incorporated into the agreement automatically, roles limit who sees conversations, and the help centre documents erasure by tagging chats or tickets and emailing support with a verification code, plus transcript retrieval for requesters. Audit logs exist only on the Enterprise plan and record who changed what in the account rather than who read which ticket, and we found no public information on automatic retention rules per queue or data category, or on redaction of ticket content. The privacy policy lists developing and improving artificial intelligence and machine-learning capabilities among its processing purposes, which a buyer should reconcile with the Addendum before trusting years of customer-typed history to it. 2 10 9 10 13

Report an error

The Shop Operator

The Data Processing Addendum is incorporated into the agreement automatically with the June 2021 Standard Contractual Clauses, roles split Owner, Admin and Member with role-based limits on who sees conversations, and deletion of chats or tickets is documented as a tag-and-email procedure backed by a verification code, with transcript access handled the same documented way. Audit logs exist but only on the Enterprise plan, which weakens the everyday case. We found no public information on automatic retention or deletion rules per queue or data category, redaction of ticket content, or a published subprocessor list with named providers and locations. 2 10 9 10 13

Report an error

The Integrator

A data processing agreement is incorporated into the agreement automatically with updated standard contractual clauses, role-based permissions limit which teammates see conversations, deletion and access for a requester follow documented email-verified procedures, and audit logs record who changed what on the Enterprise plan. Two caveats a data-protection lead should weigh: audit logs sit behind the Enterprise plan, and the privacy policy lists researching, developing and training AI capabilities among its processing purposes. 2 10 9 13

Report an error

The Skeptic

A Data Processing Addendum with the June 2021 Standard Contractual Clauses is incorporated into the agreement automatically, deletion of tagged chats or tickets is documented with a verification-code procedure, and Owner, Admin and Member roles limit who sees conversations — though the audit log sits behind the Enterprise plan. The privacy policy names researching and improving artificial intelligence and machine learning among the purposes personal data is processed for, and I found no public information on automatic retention or deletion rules, redaction of ticket content, or a published subprocessor list. 2 10 9 13

Report an error

Integrations & API

Show reasoning
How this is scored

The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.

0 — A closed tool with no API and no integrations; context is copied in by hand.

3 — A handful of named integrations or a connector service such as Zapier, or an API with basic documentation.

5 — Named integrations for common CRM, shop or collaboration tools, a documented REST API, and webhooks or triggers that call other systems.

8 — An app marketplace with maintained bidirectional integrations, customer context from other systems shown inside the ticket, SSO and SCIM provisioning, documented rate limits and a sandbox.

10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.

Report an error

The Support Lead

There are documented APIs over REST and WebSocket with OAuth 2.1, webhooks, a monthly quota of 10,000 calls on Essential and 20,000 on Growth with overage at $29.50 for an extra 100,000 calls, SDKs in JavaScript, Go and Python, an MCP server, and a marketplace with Text-maintained apps. Shopify orders and live cart contents appear beside the conversation, custom skills call Salesforce, HubSpot or any HTTP endpoint mid-chat, and SAML single sign-on is on Enterprise. I found no public information on SCIM provisioning or a sandbox environment. 12 5 9 11 14

Report an error

The Agent Advocate

A marketplace behind 200-plus platforms with a Text team building and maintaining the apps, Shopify orders shown right beside the ticket, documented REST and WebSocket APIs with OAuth 2.1, webhooks, per-plan quotas and a priced overage at $29.50 per extra 100,000 calls, plus SDKs, an Agent App SDK and an MCP server — this is a component, not a dead end. SCIM provisioning, a sandbox and any deprecation policy are the pieces we found no public information on. 11 1 5 14

Report an error

The Data Protection Officer

A public developer platform offers REST and WebSocket chat APIs, configuration and reporting APIs, webhooks, an MCP server and Agent App SDKs under OAuth 2.1, with per-plan API quotas of 10,000 calls a month on Essential and 20,000 on Growth and extra calls at $29.50 per 100,000. Shopify order data appears beside chats and tickets, Salesforce, HubSpot, Mailchimp and Slack are reachable through custom skills and built-in automations, and a Marketplace maintained by the vendor's own team carries the apps. We found no public information on SCIM provisioning or a sandbox environment. 5 12 5 11 14

Report an error

The Shop Operator

This is where the product earns its keep for a shop: an app marketplace whose apps the vendor's own team builds and maintains, Shopify orders and payment status shown beside chats and tickets, order data from other shops arriving through a sales-tracking API, plus webhooks, REST and WebSocket APIs, OAuth 2.1 with personal tokens, SDKs in JavaScript, Go, Python and TypeScript, and an Agent App SDK for building in-app extensions. Skills can call Salesforce, HubSpot, Mailchimp or any HTTP endpoint mid-conversation, and SAML 2.0 single sign-on is available on Enterprise. API call quotas are documented and priced per plan with a stated overage rate; we found no public information on SCIM provisioning or a sandbox. 5 12 5 9 11 14

Report an error

The Integrator

This is what I need for wiring in other systems: a documented REST and WebSocket chat API with OAuth 2.1 and personal access tokens, webhooks that call your backend on events like a new chat or tagged thread, published monthly quotas (10,000 calls on Essential, 20,000 on Growth) with an extra 100,000 calls at $29.50, SDKs in JavaScript, Go and Python, an Agent App SDK for in-ticket extensions, an MCP server, and a marketplace whose Text Team maintains the first-party apps. Two gaps keep it from the top: we found no public information on SCIM provisioning for the identity provider, and no sandbox environment for testing integrations before production. 11 12 5 14

Report an error

The Skeptic

The API surface is unusually public: REST and WebSocket access to chats, webhooks, OAuth 2.1 with personal access tokens, SDKs in Go, JavaScript and Python, an MCP endpoint, and open-source documentation repositories. Shopify orders appear beside chats and tickets, and built-in skills push Salesforce leads or Slack alerts; the documented quota is priced at 10,000 calls a month on Essential, 20,000 on Growth, with an extra 100,000 at $29.50. I found no public information on SCIM provisioning or a sandbox. 11 5 14 14

Report an error

European sovereignty panel opinion

Show reasoning
How this is scored

Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.

0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.

3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.

5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.

Report an error

The Support Lead

EU hosting is selectable and named — Google Cloud in Frankfurt with files in Amazon S3 — and the DPA with updated SCCs is applied automatically, while the group's parent is listed in Wrocław. But the contracting entity on the captured pages is Text, Inc. of Boston, the vendor participates in the EU-U.S. Data Privacy Framework, and I found no public information on a published subprocessor list with locations, so the chain is only partly proven. 9 9 10 13 1

Report an error

The Agent Advocate

EU hosting is selectable with Frankfurt named on Google Cloud, and the data processing agreement carries the 2021 standard contractual clauses for EU and EEA customers — two solid European elements. But the contracting entity across the captures is Text, Inc. of Boston, with the Polish Text S.A. appearing only as parent organization, there is no subprocessor list with locations, and the vendor takes part in the EU-U.S. Data Privacy Framework. 9 13 10 1

Report an error

The Data Protection Officer

The captured pages prove an EU hosting choice with Frankfurt named on Google Cloud and a Data Processing Addendum with SCCs, but every legal page names Text, Inc. of Boston, Massachusetts as the entity, with a Polish parent company appearing only in structured data. No subprocessor list with names and locations is published, uploaded files sit in Amazon S3, and US regions in Texas and Iowa run alongside the EU option. We found no public information on an EU representative or on which region is the default. 2 9 9 10 13 1

Report an error

The Shop Operator

Customers can choose to keep their data in the European Union, with the EU region named as Frankfurt, Germany on Google Cloud and uploaded files stored in Amazon S3, and a DPA with updated SCCs is part of the agreement — those are proven European elements, and the vendor's parent organisation Text S.A. is listed in Wrocław, Poland. Against that, the privacy policy and the captured legal notices name Text, Inc. of Boston, Massachusetts as the entity, and participation in the EU-U.S. Data Privacy Framework is stated. We found no public information on an EU contracting entity or EU representative for the service, a published subprocessor list with locations, or a self-hosted or private-cloud option. 2 9 9 10 1

Report an error

The Integrator

Customers can choose to keep their data in the European Union, with the EU region documented as Frankfurt, Germany on Google Cloud and uploaded files in Amazon S3, and a published data processing agreement that includes updated standard contractual clauses. Against that, the captured pages name Text, Inc. of Boston, Massachusetts as the contracting entity, participation in the EU-U.S. Data Privacy Framework is stated, and we found no public information on a published subprocessor list with locations. 9 9 10 2

Report an error

The Skeptic

Customers can choose to keep their data in the European Union, with application infrastructure on Google Cloud in Frankfurt, Germany and file storage in Amazon S3, and a DPA with SCCs is incorporated automatically. The contracting entity named across the captured pages is Text, Inc. of Boston, Massachusetts — the Polish parent Text S.A. appears only as parent organization — and the vendor takes part in the EU-U.S. Data Privacy Framework; I found no published subprocessor list with locations. 9 9 13 10 1 14

Report an error

Pricing transparency

Show reasoning
How this is scored

Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price or one priced tier, per agent or flat.

5 — Per-agent prices public for the main tiers with the billing period stated and the main features per tier listed.

8 — Every tier and add-on priced publicly with per-agent maths, telephony or messenger costs and light-agent or contact limits given, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.

10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.

Report an error

The Support Lead

Per-agent prices are public with billing periods stated — Starter from $19/user/month billed annually ($25 monthly), Team $49 annually ($59 monthly), Business $79 annually ($89 monthly) — plus a 14-day free trial with no credit card and API overage at $29.50 per 100,000 calls. However, the platform pages state the omnichannel capabilities sit under Text pricing plans and are not included in LiveChat plans, and I found no public information on VAT treatment, minimum term, light-agent pricing or channel costs, so I could not compute a full annual invoice from public pages alone. 1 5 9 11 1

Report an error

The Agent Advocate

Three tiers priced per agent in both billing periods — Starter, Team and Business from $19, $49 and $79 per user per month billed annually, $25, $59 and $89 monthly — with a 14-day trial that needs no card and API quotas plus priced overage. But the captures state neither VAT treatment nor minimum term nor what SMS or WhatsApp cost, and they show different plan families — Starter, Team, Business against Essential, Growth, Enterprise — so I cannot compute one clean annual invoice. 1 11 1 5

Report an error

The Data Protection Officer

Per-agent prices are public with the billing period stated — Starter at $19/user/month billed annually or $25 monthly, Team at $49 annual or $59 monthly, Business at $79 annual or $89 monthly — plus a free 14-day trial without a credit card and metered API overage at $29.50 per extra 100,000 calls. The captured pages give different plan names for the same product — Essential and Growth on the API page against Starter, Team, Business and Enterprise elsewhere — which makes mapping priced tiers to features harder. We found no public information on VAT treatment, minimum term, or light-agent and contact limits. 1 9 11 1

Report an error

The Shop Operator

Per-agent prices are public for the main tiers with the billing period stated — Starter from $19 per user per month, Team from $49, Business from $79, billed annually, with monthly figures also shown — plus a free 14-day trial without a credit card, and API quotas of 10,000 calls a month on Essential and 20,000 on Growth with an extra 100,000 calls at $29.50. But the captured pages state the omnichannel features run under separate Text pricing plans that are not included in LiveChat plans, and those plan prices are not shown, so I cannot compute the annual invoice for the capabilities this evaluation actually covers. We found no public information on VAT treatment, minimum term, or what SMS or messenger channels cost. 1 5 11 1

Report an error

The Integrator

Three tiers carry public per-agent prices with both billing periods stated — Starter from $19, Team from $49 and Business from $79 per user per month billed annually, with monthly variants at $25, $59 and $89 — alongside a free 14-day trial with no credit card required and public API overage pricing. What stops a support lead computing the full invoice: the captured pages give different plan names on the API pricing page (Essential and Growth) than on the pricing page, and we found no public information on VAT treatment, minimum term, or what the Twilio SMS channel adds to the bill. 1 11 1

Report an error

The Skeptic

The LiveChat tiers are public with per-agent maths and billing period stated: $19, $49 and $79 per user per month billed annually, $25, $59 and $89 monthly, a 14-day trial with no credit card, and public API-call pricing. But the captured pages state the omnichannel and ticketing capabilities sit under Text pricing plans and are "not included in LiveChat plans", with availability, limits and pricing depending on the Text plan — and the pages give different tier names such as Essential and Growth with no numbers attached. I found no public information on messenger or telephony costs, light-agent or contact limits, minimum term, or VAT treatment. 1 1 11 5

Report an error

European sovereignty — proven facts

0 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about LiveChat

Is LiveChat European?

Not determined: the vendor’s pages as captured do not say where LiveChat is based.

Where does LiveChat store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does LiveChat have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to LiveChat?

As of 18 Nov 2026, the panel rates Zendesk (3.5/5), LiveAgent (3.5/5) and Intercom (3.5/5) highest among the other 35 Customer Service & Helpdesk products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Zammad (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: LiveChat alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (14)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.livechat.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 22 Sep 2026 Details →
  2. 2 Legal notice — found from the homepage www.livechat.com Checked 16 Nov 2026 Details →
  3. 3 Ticketing, queues & SLA — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
  4. 4 Ticketing, queues & SLA — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
  5. 5 Channels in one queue — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  6. 6 Channels in one queue — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  7. 7 Knowledge base & deflection — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  8. 8 Knowledge base & deflection — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  9. 9 Customer data protection — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  10. 10 Customer data protection — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  11. 11 Integrations & API — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  12. 12 Integrations & API — found from sitemap www.livechat.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  13. 13 Security / trust page — found from the homepage www.livechat.com Checked 16 Nov 2026 Details →
  14. 14 Code repository (open-source licence) — found from the homepage github.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 1 Nov 2026 Details →