Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

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

by Userlike UG · www.userlike.com

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

Link to this page

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

Userlike at a glance

Vendor
Userlike UG
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 5 Oct 2026
Panel verdict
The AI panel rates Userlike 3/5, the mean of 6 judges. Userlike — the captured pages announce "Userlike ist jetzt Lime Connect" — is a messaging-first customer service product from Cologne, Germany, pitched on German hosting. how scores are made
As of
Vendor pages captured 31 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Userlike alternatives, European ones first →

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

The Skeptic

Weighted verdict

Counts the channel logos on the marketing page, then asks which of them share one queue and one history. Reads for the tier where SLA policies begin, what a "light agent" may actually do, and whether the AI summariser is included or metered.

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

Scored by The Skeptic

Panel median The Skeptic 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 Skeptic
Ticketing, queues & SLA 2 of 5 2 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.5 of 5 3.5 of 5
Integrations & API 3 of 5 2.5 of 5
European sovereignty 3 of 5 2.5 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 Skeptic

Conversations are assigned and routed per widget by operator group or by skills sets, with an unassigned fallback area of the inbox and visibility limited by group and organisation — real routing, documented in the help centre. But the engine checks a helpdesk buyer runs fail: we found no public information on SLA policies, priorities, response-time or resolution reporting, macros, or merge and split. That is conversation routing, not managed ticketing. 4 5 10

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 Skeptic

I counted the channel logos and the documentation confirms they share one message center: website chat, WhatsApp over the official Business API, Facebook Messenger, Instagram, Telegram, Threema, SMS/MMS and email all arrive in one inbox, with a privacy notice that requires consent before a chat starts. Two steps up remain unevidenced: the voice offering is an automated voice agent in alpha rather than telephony with call logging, and we found no public information on a customer portal where a requester sees their own tickets. 6 3

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 Skeptic

The knowledge base is a real asset: folders and subfolders, multilingual content, search, versioning, website and file import, with create and publish permission states, and it feeds the AI hub whose over-80-percent automated-resolution claim is the deflection story. Deflection, however, is claimed only as an automation rate; we found no public information on reporting which articles deflect, on suggestions to the agent while answering, or on a public help centre with its own branding. 1 8 9 10

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 Skeptic

The compliance pages earn their credit: a data processing agreement on request including a full subprocessor list, configurable retention with automatic deletion, documented search, filter, download and deletion for access and erasure requests, ISO 27001 certified servers, no customer data in external AI training, audited AI actions, and role permissions down to group and organisation conversation visibility. We found no public information on redaction of message content or attachment handling, and the agreement is offered on request rather than signable online. 3 3 10

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 Skeptic

The developer documentation is genuine: a JSON API for conversations, contacts and operators with rate limits referenced, a custom channel for any message-based system, HTTP chatbot connection, callback URLs, an add-on frontend API, and SCIM/SSO on the Enterprise plan. CRM and ERP appear only as generic categories, however, and we found no public information on named CRM or shop integrations, an app marketplace, bidirectional maintained connectors, or a sandbox. 1 11 2

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 Skeptic

Germany is stated as the server location with German and EU law applying, the contracting entity is Lime Connect (Userlike) GmbH with register number HRB 73211, a data processing agreement with subprocessor list is offered on request, third-party access requires a German court order, and customer data stays out of external AI training. The register number is published without a court or city, and we found no public information naming the data-centre provider or the subprocessors' locations. 1 3

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 Skeptic

Two tiers carry public numbers with feature lists — Free at 0 € /Monat and Pro ab 87 € /Monat — and the add-ons are individually priced: AI Agent ab 99 € /Monat, AI Copilot ab 19 € /Monat pro Nutzer, WhatsApp campaigns ab 20 € /Monat plus Meta-Gebühr for 1000 Kampagnennachrichten, Workflows ab 50 € /Monat for 1000 Workflow-Ausführungen, all marked Preise zzgl. MwSt. But Pro is a from-price with minimum seats and no stated per-agent basis, Enterprise is auf Anfrage, and we found no public information on the annual billing figure, minimum term, or a price for the Team package the WhatsApp channel reportedly starts at. 2 2

Report an error

European sovereignty — proven facts

1 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 unverified
Why unverified?

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

— uncited Report an error
Transfer impact assessment Not determined unverified
Why unverified?

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

— uncited Report an error

Questions about Userlike

Is Userlike European?

Yes. whats-best.ai classifies Userlike as EU-Made. Its vendor, Userlike UG, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does Userlike store data?

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

Does Userlike have a free plan?

Yes. Userlike has a free plan, per the vendor’s page captured 5 Oct 2026.

What are the best alternatives to Userlike?

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: Userlike 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 (13)

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

  1. 1 Vendor homepage www.userlike.com Checked 16 Nov 2026 +2 earlier captures: 11 Sep 2026, 31 Aug 2026 Details →
  2. 2 Pricing www.userlike.com Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
  3. 3 Security / trust page — found from the homepage connect.lime-technologies.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  4. 4 Ticketing, queues & SLA — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
  5. 5 Ticketing, queues & SLA — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
  6. 6 Channels in one queue — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
  7. 7 Channels in one queue — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
  8. 8 Knowledge base & deflection — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
  9. 9 Knowledge base & deflection — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
  10. 10 Customer data protection — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  11. 11 Integrations & API — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
  12. 12 Integrations & API — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
  13. 13 Structured-data backfill: markup only, no text or screenshot www.userlike.com Checked 8 Nov 2026 Details →