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 Integrator

Weighted verdict

Has to wire the helpdesk into a CRM, a shop and an identity provider that all predate it. Wants a documented API with rate limits, webhooks that retry, SCIM, and a sandbox. Reads a partner-contact form on an integrations page as a missing API.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Integrator

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

Ticketing, queues & SLA

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 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

Channels in one queue

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 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

Knowledge base & deflection

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 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

Customer data protection

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 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

Integrations & API

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 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

European sovereignty

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 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

Pricing transparency

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 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

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 →