LiveAgent
Provenance unknown Report an errorPanel 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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
LiveAgent, a help desk and call center platform from Quality Unit, s.r.o. of Bratislava, scored strongest on sovereignty, a uniform 8, and customer data protection, 7-8: EU accounts sit on AWS in Frankfurt and Ireland with the region fixed at sign-up, the subprocessor list is published with locations and safeguards, a downloadable DPA accepts your own template, erasure of a contact and their tickets is promised within five business days, and card numbers are masked before storage. Ticketing scored a uniform 7 on deep SLA timers; omnichannel 7-8, with email, chat, phone and the social and messenger channels landing as tickets in one inbox. Weakest are knowledge self-service, 5-6, and integrations, a uniform 6, where the Slack integration is documented one-way, historical tickets cannot serve as a knowledge source, and we found no public information on deflection reporting, single sign-on, provisioning or rate limits. The one-point splits carry stated reasons: lower data-protection marks cited the Business-only audit log and account-level retention, lower pricing marks the missing telephony, messenger and VAT figures. Persona-weighted totals ranged from 6.4 to 7.6.
Speaks for it
- Sovereignty scored a uniform 8 — Quality Unit, s.r.o. of Bratislava is the named processor, EU accounts sit on AWS in Frankfurt and Ireland, and the subprocessor list is published with locations and safeguards.
- Customer data protection scored 7-8 — DPA templates for the EU, US and Asia with your own template accepted, erasure within five business days, export to PDF, HTML or CSV, and regex masking of card numbers before storage.
- The SLA engine offers separate first-answer, next-answer, first-resolve and call-answer timers, business hours that extend rather than pause them, and an SLA log feeding compliance reports.
- Email, live chat, phone with IVR, Facebook, Instagram, X, WhatsApp, Viber and Telegram all land as tickets in one shared inbox.
- Every tier carries a public per-agent price with both billing periods and agent caps — Starter $15 annually or $19 monthly up to 5 agents, Team $29 or $35 up to 15, Business $49 or $59 — with no setup fee, no long-term contract and AI on every plan.
Held against it
- Integrations scored a uniform 6 — the Slack integration is documented one-way, and we found no public information on single sign-on, user provisioning, documented rate limits or a sandbox.
- Knowledge self-service scored 5-6 — the setup pages state historical tickets cannot be used as a knowledge source, and we found no public information on draft states, versioning, review dates or reporting on which articles deflect.
- Telephony and messenger usage costs and VAT treatment are not published, AI runs on a provider you pay separately, and knowledge indexing consumes FlowHunt credits bought separately.
- The audit log arrives only on the Business plan, and documented retention covers account-level timelines rather than rules per queue or data category.
- LiveAgent itself holds no SOC 2 or ISO 27001 yet — a SOC 2 Type II audit is in progress — and the captured pages give different figures on self-hosting, with the pricing page saying cloud only while telephony guides address self-hosted licences.
Best for
- You need GDPR paperwork an auditor can read today — DPA templates that accept your own version, erasure within five business days, export in three formats and masking before storage.
- You want EU hosting with a published subprocessor list — AWS in Frankfurt or Ireland, chosen and preselected at sign-up.
- You run up to 15 agents and want phone, social channels and SLA in one inbox at a published per-agent price.
- You are migrating from Zendesk, Freshdesk, Help Scout, Intercom, Zoho Desk or HubSpot — migration is free.
Avoid if
- Your workflow depends on two-way Slack interaction — the integration is documented one-way, with actions in Slack unable to trigger anything in LiveAgent.
- You want to seed self-service from past conversations — the setup pages state historical tickets cannot be used as a knowledge source.
- You need the audit log below the Business tier — it arrives only on that plan.
- You may need to move data between regions later — the region is fixed at sign-up and moving it needs the vendor's agreement.
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 3.5 of 5 |
| Channels in one queue | 3.5 of 5 |
| Knowledge base & deflection | 3 of 5 |
| Customer data protection | 4 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 4 of 5 |
| Pricing transparency | 3.5 of 5 |
Ticketing, queues & SLA
Show reasoningHide 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.
The Support Lead
The SLA machinery is real: separate first-answer, next-answer, first-resolve and call-answer timers, business hours that extend the clock rather than pause it, a To-solve queue distributed by importance, and an SLA log with compliance and load reports I could actually take to a quarterly review. Rules and time rules handle routing at ticket creation, and tags, canned messages, department-level roles and ticket splitting are documented. I found no public information on warnings before a timer breaches, escalation paths, ticket merging, or assignment by skill, so it sits a notch below the top of this scale. 4 5 13 1
The Agent Advocate
The engine is deep in the ways that matter on the hundredth reply: six SLA timer types from first answer to call pickup, business hours that extend the clock rather than pause it, an SLA log with compliance reports by agent and department, canned and predefined messages, and ticket split with assignment to the right department. What holds it down is silence on the parts an agent feels daily: I found no public information on merging tickets, on breach warnings or escalation when a timer expires, or on skills- or load-based routing — the To solve distribution is named but its logic is not described. Search across ten thousand tickets is likewise not documented, and that is the first thing I look for. 4 5 11 13
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
The Shop Operator
The SLA machinery is documented in real depth — six SLA types from first answer to call answer, business hours that extend rather than pause the timers, an SLA log feeding reporting, tickets ordered by importance, and a To-solve distribution, with canned messages and rules all in the permissions list. What I found no public information on is breach warnings or escalation, ticket merging, or assignment by skills or load, which keeps this a notch below the managed-workload level. 4 5 11 13
The Integrator
Departments, statuses, tags and ticket split are documented, and the SLA engine is deep — separate clocks for first answer, first resolve and next answer, business hours that extend the timers rather than pausing them, and an SLA log that feeds the compliance reports I can pull through the API. We found no public information on breach warnings or escalation, ticket merge, or skills-based assignment, which keeps this below the top band. 4 5 13 11
The Skeptic
The engine is real: tickets carry statuses, tags and a split action, and SLA is a defined feature with first-answer, next-answer, first-assign and first-resolve levels, business hours (timers extended rather than paused outside them), an SLA log, and report endpoints for SLA compliance, load and agent performance. My tier-reading: SLA starts on Team at $29 billed annually or $35 monthly, and even unlevelled tickets get an internal 7-day answer time feeding the ticket grid's Importance ordering. I found no documentation of ticket merge, breach warnings or escalation on breach, or skills- or load-based assignment beyond the To-solve distribution. 4 5 13 11
Channels in one queue
Show reasoningHide 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.
The Support Lead
Email, live chat, calls through the built-in call center with IVR, WhatsApp, Viber, Telegram, Facebook, Instagram and X all land as tickets in one shared inbox with one history — that is the Monday-morning test passed. Telephony runs through SIP providers including Twilio, Vonage, TeleCube and VIPTel, and customers get a portal where they can manage their own profile. I found no public information on consent handling specific to the messenger channels, which is the one element keeping this just below the top band. 1 6 7 12 3
The Agent Advocate
Email, live chat, calls, Facebook, X, Instagram, WhatsApp, Viber and Telegram all land as tickets in one inbox, and phone is a first-class channel with its own answer-time SLA, IVR that routes callers and issues callbacks, and recordings stored alongside the rest of the account data. That is one screen rather than four tabs, which I prize. I stop short of full marks because I found no public information stating a WhatsApp consent-handling position, and no statement that the customer portal shows a requester their own tickets rather than only knowledge content. 1 6 7 14 13
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
The Shop Operator
Email, live chat, calls, WhatsApp, Viber, Telegram, Facebook, Instagram and X are all documented landing in one inbox, with IVR on the phone side and call recordings stored alongside the rest of the account data — WhatsApp and the phone queue genuinely share the queue. I found no public information on a portal where a requester sees their own tickets, nor on messenger consent handling, so I stop short of the top level. 6 7 1 14
The Integrator
Email, chat, phone via SIP providers with IVR, Facebook, Instagram, X, WhatsApp, Viber and Telegram all land as tickets in one inbox, with calls living inside tickets and call recordings stored alongside the account data. We found no public information on consent handling for the messengers or on a portal where a requester can see their own tickets — the portal pages cover knowledge bases, forums and profile deletion. 1 6 7 12 14 1
The Skeptic
The channel list is documented channel by channel and lands as tickets in one shared inbox: email, live chat, phone via SIP providers (Twilio, Vonage, TeleCube, VIPTel) with call recordings stored in LiveAgent, Facebook, Instagram, X, WhatsApp via Twilio or 360dialog, Telegram, Viber and contact forms, with IVR per number. I found no public information on WhatsApp consent handling, or on a customer portal where a requester sees their own tickets, and the Viber guide itself says bots could not be created by users since 5 February 2024. Phone and social channels begin on Team, not Starter. 1 8 4 6 12 7 14
Knowledge base & deflection
Show reasoningHide 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.
The Support Lead
A public help centre with categories, multiple per-brand portals, custom colours, four themes and internal-only articles for agents is documented, and the AI chatbot answers customers around the clock from the knowledge base, website and documents. For knowledge gaps the vendor's documented advice is to create FAQ articles from tickets by hand. I found no public information on draft and publish states, article versioning or review dates, article suggestions to agents while answering, or reporting on which articles deflect. 8 8 1 9
The Agent Advocate
The knowledge base is a real public help centre — categories, articles, forums, feedback boards, branded themes, customisable search widgets, internal-only articles for agents — and the AI chatbot answers customers in chat from the knowledge base, website and documents before a ticket ever exists, which is deflection pointed the right way. But the gaps are telling for a team that wants knowledge managed: historical tickets cannot be used as a knowledge source, and I found no public information on draft and publish states, article suggestions inside an agent's reply, versioning or review dates, or reporting on which articles deflect. Knowledge here is organised, not yet measured. 8 1 9 8
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
The Shop Operator
A public, searchable, branded help centre with categories, four themes, per-brand portals, forums, feedback boards and agent-only internal articles is documented, and the chatbot answers from the knowledge base round the clock and hands off to a human with full context — a real deflection lever. But I found no public information on article suggestions before a customer submits, review dates or versioning, or reporting that says which articles cut the ticket count, which is the number I would want to see by December. 8 9 1
The Integrator
Public self-service portals come with categories, four themes, custom search widgets, forums, feedback boards, agent-only internal articles and a portal per brand, plus a chatbot answering from the knowledge base around the clock. We found no public information on draft and publish states, versioning or review dates, or reporting on which articles deflect, and the chatbot setup pages state that historical tickets cannot be used as a knowledge source. 8 8 8 8 9
The Skeptic
A customizable self-service portal with categories, articles, forums, feedback boards, four themes, brand colour control, search widgets and internal-only articles, plus an AI chatbot that answers in 100+ languages from the knowledge base and hands off with context — that is genuine pre-submission answering. The deflection claim is a purpose statement, not a measured number; I found no draft and publish workflow, review dates, stale-content flagging, or reporting on which articles deflect, and the setup pages state historical tickets cannot be used as a knowledge source. 8 8 8 1 1 9
Customer data protection
Show reasoningHide 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.
The Support Lead
A data processing agreement with EU, US and Asia templates is offered, our own template is accepted, and it is governed by Slovak law; a contact and all their tickets can be deleted permanently, with erasure promised within five business days and export to PDF, HTML or CSV. Granular agent permissions with department-level overrides, an audit log on the Business plan, and Search & Replace rules masking card numbers and other sensitive strings in incoming messages before storage are all documented, as is vendor support access only on request or with approval, alongside a published subprocessor list. I found no public information on automatic retention or deletion rules per queue or data category — the documented retention covers account lifecycle after termination or suspension. 10 11 1 3 14
The Agent Advocate
Erasure is genuinely worked out: delete a contact with all their tickets and purge them permanently, export as PDF, HTML or CSV within five business days of a written request, and customers can delete their own portal profile. Redaction before storage is real too — search-and-replace rules mask card numbers and similar strings on arrival, with the original optionally kept in a custom field — and granular custom roles with department-level precedence limit what an agent may touch. What keeps it off the top band: no automatic retention or deletion rules per queue or data category are documented, and the audit log arrives only with the Business plan. 10 11 3 3 1
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
The Shop Operator
The paperwork a data-protection officer asks for is there: DPA templates to sign and countersign, our own template accepted, a contact and all their tickets permanently deleted within five business days of a written request, export in three formats, and card numbers masked in incoming messages before storage. Granular agent roles, an audit log on the top plan, support staff opening an account only when I ask or approve, and a published subprocessor list with locations complete the picture; what I found no public information on is automatic retention or deletion rules per queue or data category. 10 11 3 3 14
The Integrator
The GDPR pages are unusually concrete: a downloadable DPA accepted in the vendor's or your own template under Slovak law, deletion of a contact and all their tickets within five business days, export as PDF, HTML or CSV, granular agent permissions with department-level override, and regex masking of card numbers and other sensitive strings before storage. The audit log arrives only on the Business plan, retention rules are account-level timelines rather than per queue, and the vendor documents that its teams open an account only when you ask or approve — consent-gated support access is exactly what I want to show an auditor. 3 10 11 1 3 3 14
The Skeptic
DPA templates for EU, US and Asia are downloadable and countersigned with the customer's own template accepted; a contact and their tickets can be deleted permanently with portal self-deletion, export runs to PDF, HTML or CSV, and deletion on request is promised within 5 business days. Custom roles are granular per permission with department-level precedence, Search & Replace masks card numbers and other patterns before storage, the subprocessor list is published with locations, and vendor support opens an account only on request or approval. Against the higher marks: the audit log arrives only on the Business plan, and retention is documented as account-level timelines rather than per-queue or per-category automation. 3 3 11 10 1 14 3
Integrations & API
Show reasoningHide 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.
The Support Lead
Over two hundred integrations are claimed with Shopify, Slack and HubSpot named, and the REST API reference is genuinely deep — endpoints for tickets, customers, companies, files and reports, error codes, pagination limits, and a deprecation notice pointing to a newer endpoint version my team could build against. Telephony connects through several SIP providers and the Business plan adds MCP. I found no public information on single sign-on or SCIM provisioning, rate limits, a sandbox, or CRM context shown inside the ticket, and the Slack integration is documented as working one way only. 13 1 6 12
The Agent Advocate
A complete and honest REST API reference — authentication, pagination limits, error codes, even deprecation notes pointing to successor endpoints — plus 200+ integrations with Shopify, Slack and HubSpot named, four SIP providers for the call centre, and MCP on the Business plan. But the Slack integration works one way only, and I found no public information on an app marketplace with maintained bidirectional integrations, SSO or SCIM provisioning, documented rate limits or a sandbox. Customer context from other systems inside the ticket is documented only for the chatbot's order-status integration, which needs your team's help to build. 13 1 6 12 1
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
The Shop Operator
Two hundred plus integrations with Shopify, Slack and HubSpot named, a fully documented REST API with authentication, pagination, error codes and report endpoints, MCP on the top plan, and free migration off six competitors — enough hooks for the shop. But the Slack integration is documented as one-way only, and I found no public information on single sign-on or user provisioning, documented rate limits or a sandbox; order data in front of the agent appears to be custom chatbot work rather than a maintained integration. 6 12 13 1
The Integrator
The REST API is properly documented — conversations, customers, companies, files, knowledge base entries and SLA reports with pagination limits, error codes and API-key authentication — next to 200+ named integrations including HubSpot, Shopify and Slack, telephony through Twilio and other SIP providers, and free migration from six rival helpdesks. From my chair the gaps are real: we found no public information on webhooks, rate limits, SCIM or SSO provisioning, or a sandbox, and the Slack integration is stated to work one way only, with actions in Slack unable to trigger anything in LiveAgent. 13 12 6 1 1
The Skeptic
200+ integrations are claimed with Shopify, Slack and HubSpot named, and the REST API reference is genuinely complete — API-key authentication, conversations, customers, companies, files and report endpoints, pagination limits, error codes, even a deprecation notice — with telephony guides for four SIP providers and MCP on the Business plan. The Slack integration is documented as one-way only, and I found no public information on rate limits, a sandbox, SSO or SCIM provisioning. 13 1 12 6 1
European sovereignty
panel opinion
Show reasoningHide 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.
The Support Lead
The contracting entity and processor is Quality Unit, s.r.o. of Bratislava, EU hosting on AWS in Frankfurt and Ireland is selectable and preselected for European customers at sign-up, and the subprocessor list is published with every non-EU processor named alongside its safeguard, Standard Contractual Clauses or the EU–US Data Privacy Framework; the data processing agreement is governed by Slovak law. Two caveats hold it below the top: the region is fixed at sign-up and cannot be switched later, and the captured pages give different figures on hosting — current pages name AWS, older ones name Linode with data centres in Germany, the UK and Slovakia — while the pricing page says cloud only even as telephony guides address self-hosted licences. 3 14 2 2
The Agent Advocate
The chain is published and mostly European: Quality Unit, s.r.o. in Bratislava as the contracting processor, EU residency selectable and preselected at signup with Frankfurt and Ireland, a countersigned DPA under Slovak law, and a subprocessor list with locations, safeguards, written notice and ten days to object. Non-EU processing is named with its legal basis — Standard Contractual Clauses for the US sales entity, the Ukraine support entity and Twilio, the EU–US Data Privacy Framework for website analytics. It stops short of the top band: no certification is published yet (a SOC 2 Type II audit is in progress), several subprocessors sit outside the EU, and the captured pages give different figures for the data-centre provider and for self-hosting, with the marketing pages stating cloud only while a telephony guide refers to self-hosted licenses. 3 14 14 3 12 1
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
The Shop Operator
The archive can live in Frankfurt or Ireland on AWS, Quality Unit s.r.o. in Bratislava is named as the processor, the DPA is signed on request, and the subprocessor list is published with locations and Standard Contractual Clauses or Data Privacy Framework safeguards named for the US and Ukraine entries. LiveAgent itself holds no SOC 2 or ISO 27001 certificate yet — an audit is in progress — the region is fixed at sign-up, and the captured pages give different figures on self-hosting, with the homepage saying cloud only while the integration guides mention self-hosted licences. 12 1 3 14
The Integrator
Quality Unit, s.r.o. in Bratislava is the named processor and contracting entity, EU accounts sit on AWS in Frankfurt and Ireland with the region fixed at sign-up, and the subprocessor list updated in October 2026 names each processor with its location and legal basis — Standard Contractual Clauses for the US and Ukraine entries, a data processing agreement for the Amsterdam one. Non-EU processors stay in the chain with safeguards, LiveAgent itself holds no certification yet with a SOC 2 Type II audit under way, and the captured pages give different pictures on self-hosting: the pricing page says cloud only while a telephony guide addresses self-hosted licences. 3 14 3 14 12 1
The Skeptic
Quality Unit, s.r.o. in Bratislava is named as the processor, EU customers are hosted on AWS in Frankfurt or Ireland with the region chosen at sign-up (and fixed afterwards), and the subprocessor list is published with locations and legal bases — SCCs for the US and Ukraine entities, an Amsterdam server for tag management, a US sales entity under SCCs. Against the end-to-end mark: LiveAgent itself holds no SOC 2 or ISO 27001 (only the AWS data centres are certified), and the captured pages give different figures on self-hosting — a positioning statement says cloud only while one integration guide addresses self-hosted (downloadable/standalone) customers — with the copyright footer naming Quality Unit, LLC. 3 14 1 1 12
Pricing transparency
Show reasoningHide 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.
The Support Lead
Every plan carries a public per-agent price with the billing period stated — Starter at $15 billed annually or $19 monthly for up to five agents, Team at $29 or $35 up to fifteen, Business at $49 or $59 for any team size — plus a worked example of five agents paying $110 a month on offer, no setup fee and no long-term contract. The edges are murkier: AI needs your own provider account, chatbot knowledge indexing consumes FlowHunt credits paid separately, and I found no public information on telephony call costs or VAT treatment. 1 1 1 9
The Agent Advocate
A support lead can compute the invoice: every tier priced per agent with both monthly and annual figures, special and regular prices, agent caps of 5 and 15, no setup fee, no minimum term, cancel or change anytime, and even a worked team-of-five example showing the monthly total. Feature splits per tier are stated plainly — phone and SLA arrive at Team, the audit log at Business. What holds it back: I found no public prices for telephony usage and no VAT treatment, and part of the AI cost sits outside these pages since you pay your own AI provider and FlowHunt credits are required for indexing. 1 1 1 9
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
The Shop Operator
Per-agent prices for all three tiers are public with billing period, agent limits, annual totals and even a worked team-of-five example, plus no setup fee and no long-term contract — I can compute most of the annual invoice myself. AI sits in every plan with no per-resolution fees but runs on my own provider's billing, and I found no public information on call or messenger costs or VAT treatment, which is what an ops lead still has to chase. 1 1 1
The Integrator
All three tiers are priced per agent with monthly and annual figures, agent caps and feature lists — Starter $15 billed annually or $19 monthly for up to 5 agents, Team $29 or $35 up to 15 with phone, social and SLA, Business $49 or $59 — with the billing period stated, no setup fee, no long-term contract and a worked example for a five-agent team. We found no public information on telephony or messenger usage costs, VAT treatment or overage; AI is bring-your-own-provider with no per-resolution fee from LiveAgent, though indexing knowledge sources consumes FlowHunt credits bought separately. 1 1 1 9
The Skeptic
Per-agent prices are public for all three tiers with both billing periods and agent caps — Starter $15 or $19 for up to 5 agents, Team $29 or $35 for up to 15 with phone, social media and SLA, Business $49 or $59 for any team size with the audit log — plus a worked example (a team of 5 on Team pays $110 a month instead of $145), no setup fee and no long-term contract. The AI line is stated as included on every plan with no per-resolution fees, but you bring your own provider key, FlowHunt indexing credits are paid separately, and legacy plans are documented to exclude AI. I found no public information on VAT treatment or on telephony and messenger usage costs. 1 1 1 14 9
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in SK
unverified
Why unverified?The site's copyright footer names Quality Unit, LLC and a US sales entity exists, but no excerpt spells out the group structure; Quality Unit, s.r.o. is simply named as the company that develops and runs LiveAgent. |
2/2 pts | 3 Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The site's copyright footer names Quality Unit, LLC and a US sales entity exists, but no excerpt spells out the group structure; Quality Unit, s.r.o. is simply named as the company that develops and runs LiveAgent.
- Weak sourcing — Hosting location. 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.
- Weak sourcing — Hosting options. 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.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 40 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 17 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 12 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.liveagent.com Checked 16 Nov 2026 +3 earlier captures: 9 Nov 2026, 2 Nov 2026, 19 Oct 2026 Details →
- 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 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 Ticketing, queues & SLA — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
- 5 Ticketing, queues & SLA — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
- 6 Channels in one queue — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
- 7 Channels in one queue — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
- 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 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 Customer data protection — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
- 11 Customer data protection — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
- 12 Integrations & API — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
- 13 Integrations & API — found from sitemap support.liveagent.com Checked 16 Nov 2026 Details →
- 14 Subprocessor list — found from the homepage www.liveagent.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →