Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

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

by Quality Unit, s.r.o. · www.liveagent.com

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

Link to this page

LiveAgent: AI-assisted analysis on whats-best.ai LiveAgent: 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.

LiveAgent at a glance

Vendor
Quality Unit, s.r.o.
Headquarters
Incorporated in Slovakia source, captured 16 Nov 2026
Data hosting
In the EU by default; pages mention the US, Asia and the United States source, captured 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Starting price
“LiveAgent pricing starts at $15 per agent/month (billed annually) with multiple tiers available including Small, Medium, Large, and Enterpri...” (vendor’s words) source, captured 19 Oct 2026
Panel verdict
The AI panel rates LiveAgent 3.5/5, the mean of 6 judges. LiveAgent, a help desk and call center platform from Quality Unit, s.r.o. how scores are made
As of
Vendor pages captured 1 Oct 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

LiveAgent alternatives, European ones first →

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

The Data Protection Officer

Weighted verdict

Sees a ticket archive for what it is: years of personal data customers typed themselves, including the things they should not have. Wants retention that executes, redaction, an audit of who read what, and an answer on whether vendor support can open a ticket.

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

Scored by The Data Protection Officer

Panel median The Data Protection Officer 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 Data Protection Officer
Ticketing, queues & SLA 3.5 of 5 3.5 of 5
Channels in one queue 3.5 of 5 4 of 5
Knowledge base & deflection 3 of 5 3 of 5
Customer data protection 4 of 5 4 of 5
Integrations & API 3 of 5 3 of 5
European sovereignty 4 of 5 4 of 5
Pricing transparency 3.5 of 5 3.5 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 Data Protection Officer

Statuses, tags, split, canned messages and granular per-action permissions are documented, and SLA comes with six target types, business hours, an SLA log and reports by agent, department and channel, plus automated distribution through the To-solve queue. We found no public information on merging tickets or explicit SLA breach warnings and escalation, which keeps this just short of the top band. 4 5 11 13

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 Data Protection Officer

Email, live chat, phone through the built-in call center with IVR and stored call recordings, Facebook, X, Instagram, WhatsApp, Viber, Telegram and contact forms all land as tickets in one inbox under one status set, and the Slack-style separation is absent. A customer portal exists, though we found no public information confirming a requester can view their own ticket list there. 4 6 7 1 14

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 Data Protection Officer

A public, branded help centre with multiple portals, categories, forums, feedback boards, internal articles and customisable search widgets is documented, and the AI chatbot answers customers around the clock from the knowledge base. We found no public information on draft and publish workflow, article versioning, multilingual articles, or reporting on which articles deflect tickets. 8 8 8 1

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 Data Protection Officer

This is close to what I demand: a downloadable, countersigned DPA that even accepts the customer's own template, per-action permissions with custom roles, documented erasure of a contact with all tickets, sessions and tokens plus export and deletion within five business days, regex-based masking of card numbers and other patterns before storage, a published subprocessor list, and support staff who open an account only on request or approval. What holds it back is retention: the documented rules cover the account lifecycle after suspension and termination, and we found no public information on automatic retention or deletion rules per queue or data category, and no evidence that the audit log records agent access to tickets. 10 11 1 3 3 14

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 Data Protection Officer

Over 200 integrations are claimed with Shopify, Slack and HubSpot named, four SIP phone providers are documented, and the REST API is documented in depth across conversations, customers, groups, knowledge base, files and reports with pagination, error codes and multiple response formats. The Slack integration is documented as one-way, and we found no public information on webhooks, SSO or SCIM provisioning, rate limits or a sandbox. 6 12 13 1

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 Data Protection Officer

The contracting entity is Quality Unit, s.r.o. in Bratislava as processor, EU hosting on AWS in Frankfurt and Ireland is selectable at signup, and the subprocessor list is published with locations and legal bases, naming the US and Ukraine entities under Standard Contractual Clauses. The region is fixed after signup and moving it needs the vendor's agreement, we found no self-hosted option as the product is cloud only, and the vendor's own SOC 2 Type II audit is still in progress rather than published. 3 14 1

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 Data Protection Officer

All three tiers carry public per-agent prices with the billing period stated, agent caps, feature lists, a worked five-agent example, no setup fee and no long-term contract. Telephony and messenger costs and VAT treatment are not public, the AI depends on a provider you pay separately with knowledge indexing billed in FlowHunt credits whose price is not stated here, and two price sets run side by side under an offer expiring November 22, 2026. 9 1 1 1

Report an error

European sovereignty — proven facts

3 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 EU by default unverified
Why unverified?

Residency is per-customer: the region is chosen at sign-up and preselected from the customer's country, and other customers' data is hosted in the US, Singapore or legacy UK storage.

2/4 pts 3 Report an error
Hosting options EU region selectable unverified
Why unverified?

The region is fixed at sign-up and cannot be switched by the customer later, and no self-hosted or on-premises option is mentioned anywhere.

1/1 pts 3 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined unverified
Why unverified?

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

— uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about LiveAgent

Is LiveAgent European?

Not determined: the vendor’s pages as captured do not say where LiveAgent is based. Its vendor, Quality Unit, s.r.o., is incorporated in Slovakia, per the vendor’s page captured 16 Nov 2026.

Where does LiveAgent store data?

LiveAgent stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026. The vendor’s pages mention the US, Asia and the United States as hosting locations, per the vendor’s page captured 19 Oct 2026.

Does LiveAgent have a free plan?

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

What are the best alternatives to LiveAgent?

As of 18 Nov 2026, the panel rates Zendesk (3.5/5), Intercom (3.5/5) and Deskpro (3/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: LiveAgent 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.liveagent.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026 Details →
  2. 2 Privacy policy — found from the homepage www.liveagent.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 19 Oct 2026 Details →
  3. 3 Security / trust page — found from the homepage www.liveagent.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 19 Oct 2026 Details →
  4. 4 Ticketing, queues & SLA — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
  5. 5 Ticketing, queues & SLA — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
  6. 6 Channels in one queue — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
  7. 7 Channels in one queue — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
  8. 8 Knowledge base & deflection — found from sitemap www.liveagent.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026 Details →
  9. 9 Knowledge base & deflection — found from sitemap www.liveagent.com Checked 16 Nov 2026 +3 earlier captures: 2 Nov 2026, 19 Oct 2026, 1 Oct 2026 Details →
  10. 10 Customer data protection — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
  11. 11 Customer data protection — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
  12. 12 Integrations & API — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
  13. 13 Integrations & API — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
  14. 14 Subprocessor list — found from the homepage www.liveagent.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →