Userlike
EU-Made Report an errorPanel 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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Userlike — the captured pages announce "Userlike ist jetzt Lime Connect" — is a messaging-first customer service product from Cologne, Germany, pitched on German hosting. The bench is strongest on customer data protection and omnichannel, both 6–7: website chat, WhatsApp over the official Business API, Facebook Messenger, Instagram, Telegram, Threema, SMS and email all arrive in one message center, backed by a data processing agreement on request with a subprocessor list, configurable retention with automatic deletion and ISO 27001 certified servers. Ticketing core clusters at 4: widget, group and skills routing is documented, but we found no public information on SLA targets, priorities or response-time and resolution reporting. The genuine split is knowledge self-service at 4–7: the low score rests on no public information about a branded help centre, article suggestions for agents or deflection reporting behind a claimed 89 percent AI Agent resolution rate, while higher scores credit the knowledge base feeding the AI agents and Copilot. Pricing transparency scores 5–6: Free at 0 € /Monat and Pro Ab 87 € /Monat are public; Enterprise is Auf Anfrage.
Speaks for it
- Website chat, WhatsApp over the official Business API, Facebook Messenger, Instagram, Telegram, Threema, SMS and email all arrive in one message center
- A data processing agreement on request includes the full subprocessor list, retention is configurable with automatic deletion, and search, filter, download and deletion functions cover access and erasure requests
- Roles scope conversation visibility by group and organisation, with view and interact as separate levels and audit-log access permissioned
- The central knowledge base with folders, multilingual content, versioning and search feeds the AI agents and the operator Copilot
- The vendor states servers in Germany under German and EU law, ISO 27001 certified, with no customer data used to train external AI models
Held against it
- We found no public information on SLA targets, priorities, or response-time and resolution reporting for conversations
- Voice appears only as an automated voice agent marked alpha, and we found no public information on a customer portal where requesters see their own conversations
- We found no public information on named CRM or shop connectors or an app marketplace, and full API access sits behind the Enterprise plan
- Pro is Ab 87 € /Monat from three seats without per-agent maths, Enterprise is Auf Anfrage, and the Team package named for the WhatsApp channel carries no public price
- The register number appears without a court or city, and we found no public information naming the data-centre provider or subprocessor locations
Best for
- You answer customers across many messaging apps — website chat, WhatsApp, Messenger, Instagram, Telegram, Threema, SMS and email — and want one team working one inbox
- Your purchase must pass a data protection or works council review — German hosting statements, a DPA with subprocessor list on request, auditable AI logging and employee anonymisation are documented
- You want a single knowledge base powering AI deflection and an operator Copilot from the same content
- You have developers to wire your own systems via the custom channel and HTTP chatbot hooks
Avoid if
- You run support against contractual SLAs — we found no public information on SLA targets, priorities or response-time and resolution reporting
- You need ready-made CRM or shop integrations with order context inside the conversation — the captured pages name categories, not products
- You must compute the full annual invoice for a fixed headcount before buying — from prices, an on-request Enterprise tier and a Team package the pages do not price stand in the way
- You need telephony with call logging today — voice is documented only as an automated voice agent marked alpha
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 2 of 5 |
| Channels in one queue | 3.5 of 5 |
| Knowledge base & deflection | 3 of 5 |
| Customer data protection | 3.5 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 3 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
Conversations land in one message center with assignment to operators and a documented unassigned fallback area, and routing is genuinely rule-based: per-widget routing, group selection, and skills-based matching where an operator must hold every skill in a set, with advanced routing on the top plan. I found no public information on priorities, SLA targets, timers that warn before breach, first-response or resolution reporting, or search across conversations, so this stops short of what I need to run a team against a promised SLA. 4 5 7 2 10
The Agent Advocate
Routing is documented properly: three modes including skills-based matching where an operator must hold every skill in a set, per-widget configuration, and unmatched conversations falling to an Unassigned inbox section. But the measured half of the engine is dark — I found no public information on SLA targets, priorities, escalation, macros, or first-response and resolution reporting, and nothing shows an agent can search the archive for a half-remembered old thread. 4 5 7 10
The Data Protection Officer
Conversations are routed per widget to operator groups or to operators matching complete skill sets, with an unassigned fallback in the Message Center and email arriving as conversations. We found no public information on SLA targets, response-time reporting, priorities, ticket statuses or search across conversations, so the workload is organised rather than measured. 4 5 6 7
The Shop Operator
Conversations are routed by real rules — a widget bound to an operator group, customer-chosen groups, or skills-based assignment that ignores groups and falls back to an unassigned inbox — with read/write permission levels per operator role. That is a message router with assignment, not a workload manager: we found no public information on priorities, SLA targets or breach warnings, response-time reporting, merge and split, or search across the conversation archive. The email add-on forwards events with JSON attachments to an external inbox rather than working them as tickets. 4 5 7 10
The Integrator
Widget-level routing is well documented — Standard, group selection and Skills modes that match operators against complete skill sets, with unmatched conversations falling to an unassigned inbox area — and roles scope which groups' conversations an operator may touch. I found nothing on priorities, statuses, SLA targets, escalation, or first-response and resolution reporting, which is what I would need before wiring queue policy to this engine. 4 5 10
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
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
Website chat, email answered directly in the message center, WhatsApp over the official Business API, Facebook, Instagram, Telegram, Threema, SMS and a custom channel are all documented as arriving in one message center, with a consent notice before chat and GDPR wording around WhatsApp. What the captured pages do not show is telephony with call logging — a voice agent is marked alpha — or a customer portal where a requester can see their own tickets. 1 3 6
The Agent Advocate
Website chat, email answered directly in the Message Center, WhatsApp, Facebook Messenger, Instagram, Telegram, Threema and SMS are all documented to land in one message center — the one-screen answer I want, with WhatsApp over the official API and a consent notice before chat that can be required. The gaps: voice is an alpha-status automated agent rather than telephony with call logging, and I found no public information on a customer portal where a requester sees their own conversations. 1 3 6 3
The Data Protection Officer
Website chat, email, WhatsApp, Telegram, Facebook Messenger, Instagram, Threema and SMS all land in one Message Center with one history, and WhatsApp runs over the official Business API with a consent notice shown before a chat starts. Voice is documented only as an alpha automated voice agent, and we found no public information on a customer portal where requesters see their own conversations. 6 1 3
The Shop Operator
Website chat, email answered directly in the Message Center, WhatsApp over the official Business API, Facebook Messenger, Instagram, Telegram, Threema and SMS all land in one message center — the WhatsApp-and-shop-in-one-queue test passes, and a privacy notice requiring consent before a chat starts is documented. Voice appears only as an alpha automated voice agent. We found no public information on telephony with call logging or a customer portal where a requester can see their own conversations. 1 3 6
The Integrator
The channel pages document website chat, email answered directly in the message center, WhatsApp, Facebook Messenger, Instagram, Telegram, Threema, SMS and a custom message channel all landing in one message center, with WhatsApp on the official Business API and a consent notice customers must accept before chatting. The phone channel is marked alpha as an automated voice agent, and we found no public information on a customer portal where a requester can see their own conversation history. 6 3 1
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
Knowledge base & deflection
panel disagrees
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 structured, searchable knowledge base with folders, versioning and multilingual content is documented, and every question/answer pair feeds the AI agents that answer customers around the clock — a real deflection mechanism, though a claimed 89 percent AI resolution rate is exactly the kind of number I would check against the queue on a Monday morning. I found no public information on a customer-facing help centre with its own branding, on draft and publish states, or on reporting that shows which articles actually deflect. 1 8 9
The Agent Advocate
A central knowledge base with unlimited folders, multilingual content, versioning and search feeds every module of the AI Automation Hub, so the same answers serve the automated agent and the Copilot that operators can be permitted to use. What I found no public information on is a public help centre under the customer's own branding, or per-article deflection reporting — the 89% AI resolution figure is a headline, not measurement a team can act on. 1 8 9 10
The Data Protection Officer
A searchable knowledge base with folders, multilingual content and versioning feeds an AI Automation Hub under create-and-publish permissions, with the vendor claiming an 89 % AI agent resolution rate. We found no public information on article suggestions before submission or while agents answer, stale-content review dates, or reporting that shows which articles deflect. 8 9 10 1
The Shop Operator
A knowledge base with infinite folders, full-text search, multilingual content and versioning is documented, feeding an AI agent that answers customers around the clock with a claimed 89 percent resolution rate and over 80 percent automation, alongside an AI Copilot for operators. Automation-rate claims aside, we found no public information on a public, self-branded help centre or on reporting that shows which articles actually deflect tickets. 1 8 9 10
The Integrator
The central knowledge base of the AI Automation Hub is documented with folders, search, multilingual content, versioning and website or file import, and every question and answer pair feeds the automated modules, with marketing pages citing an 89% AI Agent resolution rate. We found no public information on a branded public help centre, on article suggestions to agents in replies, or on reporting that shows which content deflects tickets. 8 9 1
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
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 including the full subprocessor list is offered, retention with automatic deletion after a time I define is documented, subject requests are covered by search, filter, download and deletion functions, and roles are granular enough that agents only see their own group's conversations, with an audit log whose access is itself permissioned. Attachment handling and redaction of conversation content are the pieces I found no public information on. 3 10 3 10
The Agent Advocate
A data processing agreement is offered on request including a full subprocessor list, retention is configurable with automatic deletion of chat logs, and documented search, filter, download and deletion functions serve access and erasure requests. Permissions run deep — agents see only their own group's conversations, with view and interact as separate levels and conversation deletion, export and audit-log access each permissioned. I found no public information on redaction of message content or attachment handling, and I will credit the employee anonymisation that keeps the tool out of behaviour-surveillance territory. 3 10 3 10
The Data Protection Officer
Retention is documented to execute — chat logs and messages are deleted automatically after a customer-defined period — and search, filter, download and deletion functions are documented for access and erasure requests, alongside granular roles with group-scoped visibility and a permission-gated audit log. We found no public information on redaction of conversation content, attachment handling, retention rules per queue or data category, or the vendor's own support access to customer conversations; the DPA comes on request with the subprocessor list included. 3 3 10 10
The Shop Operator
A data processing agreement is offered on request including a full subprocessor list, storage periods and automatic deletion are configurable, and search, filter, download and deletion functions are documented for access and erasure requests — with granular operator roles, group-level conversation visibility and an audit log on top, all on ISO-27001-certified servers. We found no public information on retention set per queue or data category, attachment handling, or redaction of conversation content. 1 3 10 3 10
The Integrator
A data processing agreement is offered on request including a full subprocessor list, retention periods with automatic deletion are configurable, and search, filter, download and deletion functions are documented for access and erasure requests. Granular read and write roles per conversation category, an audit-log permission and auditable AI logging cover much of what I need to run, though we found no public information on attachment handling or redaction of message content. 3 3 10 10
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
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
Developer documentation covers a JSON API for conversations, contacts and operators with rate limits acknowledged, a custom-channel framework, an add-on frontend API, HTTP connections for existing chatbots and an analytics API for CRM or tracking data, and the top plan includes SCIM and SSO. I found no public information on an app marketplace or on customer context from other systems shown inside the conversation, and the captured pages name integration categories rather than specific CRM or shop products. 1 7 11 12 2
The Agent Advocate
The developer story is real: a JSON API with rate limits named, a custom channel that attaches your own SMS gateway or email server, chatbots wired in over HTTP, a frontend API for add-ons inside the Message Center, and SCIM/SSO on the Enterprise plan. But I found no public information on named, maintained CRM or shop integrations or an app marketplace — only the loose phrase naming CRM, ERP and internal tools — and the fullest API access sits behind the Enterprise plan. 1 11 12 2
The Data Protection Officer
A documented developer API exposes conversations, contacts and operators with rate limits noted, plus a custom channel for any message-based system, a frontend add-on builder inside the Message Center, bot connection over HTTP and SCIM/SSO on the top plan. We found no public information on an app marketplace or vendor-maintained named integrations for CRM or shop systems. 11 2 7
The Shop Operator
The developer documentation shows a real API — data export and remote management with rate limits noted, a custom channel for any message-based system such as an own email server or SMS gateway, HTTP chatbot connection, a frontend add-on API and an email callback — plus SCIM/SSO at the enterprise tier. CRM, ERP and internal tools appear only as a category phrase. We found no public information naming shop or CRM connectors, and nothing showing a customer's order data from another system inside the conversation — my people would still need a second login. 1 11 12 2
The Integrator
The developer pages name a JSON API that exports and remotely manages conversations, contacts and operators with rate limits explicitly flagged, plus a custom channel for any message-based system, a chatbot connection over HTTP, an email callback to your own server, a frontend add-on API, and SCIM and SSO listed under the Enterprise plan. For someone like me the catch is that full API access sits behind Enterprise, and we found no public information on named CRM or shop connectors, an app marketplace, a sandbox, or webhook retry behaviour. 11 2 7 1
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
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
Hosting in Germany is stated on the vendor's own pages with ISO 27001 certified servers, the contracting entity is a German company with a register number, a DPA including the subprocessor list is offered, third-party access without a court order is ruled out under German law, and a data protection officer is named. The data-centre provider is not named, the subprocessor list's locations are not published on the page, and the German entity rests on the register format and German-language context rather than a stated country, so this is strong but not evidenced end to end. 1 3 3
The Agent Advocate
The trust pages state the server location as Germany under German and EU law, third-party data access is said to require a German court order, and the contracting entity is a German GmbH — though the register number is quoted without a court or city, so the German reading rests on the register format and the German-language pages. A DPA with a full subprocessor list, a named data protection officer and no customer data used for external AI training round it out. I found no public information on the data-centre provider's name, subprocessor locations, or a self-hosted option. 1 3 3
The Data Protection Officer
Hosting is stated as servers in Germany under German and EU law, the contracting entity is Lime Connect (Userlike) GmbH with a German register number, third-party data access is said to require a German court order, and the DPA includes the full subprocessor list. We found no public information naming the data-centre provider, publishing subprocessor locations, or documenting whether vendor support can open a customer conversation. 3 1 3
The Shop Operator
German hosting is stated as the standard — server location Germany with all data under German and EU law, on ISO-27001-certified infrastructure — the contracting entity is a German GmbH (register number shown without a court or city name), and third-party access only by court order under German law is stated. The subprocessor list comes with the DPA on request rather than published with locations. We found no public information naming the data-centre provider or offering a self-hosted option. 1 3
The Integrator
Hosting in Germany on ISO 27001 certified servers, a German contracting entity with register number, a DPA available on request with the subprocessor list included, no third-party access without a German court order, and no use of customer data to train external AI models. The register entry appears without a named court or city, the data-centre provider is unnamed, and subprocessor locations are only in the contract rather than published, so the chain is proven but not evidenced end to end. 3 1 3
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
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
A free tier at 0 € per month, a Pro tier from 87 € per month with a minimum of three seats, and the add-ons are public — AI agent from 99 € per month, copilot from 19 € per month per user, WhatsApp campaigns from 20 € per month plus the Meta fee for 1000 campaign messages, workflows from 50 € per month for 1000 runs — with VAT stated as excluded and a monthly/annual toggle shown. The Enterprise tier is on request, a Team plan is referenced without a price on the captured pages, and the from-prices do not let me compute the real annual invoice for twelve agents. 2 2
The Agent Advocate
Free at 0 € /Monat, Pro ab 87 € /Monat with minimum three seats, and add-ons priced publicly down to usage units — ab 50 € /Monat für 1000 Workflow-Ausführungen, ab 20 € /Monat plus Meta-Gebühr for WhatsApp campaigns, Copilot ab 19 € /Monat pro Nutzer — with a monthly/annual toggle and VAT stated as excluded. Enterprise is Auf Anfrage, fair for custom work. But the per-agent maths on the base plan stays unclear to me, I found no public information on minimum term or an annual figure, and one page references a Team package whose price these pages do not show. 2 2
The Data Protection Officer
Free and Pro carry public figures (Pro Ab 87 € /Monat) with seat, channel and conversation limits per tier, VAT stated as excluded, monthly or annual billing, and add-ons priced: AI agent Ab 99 € /Monat, AI Copilot Ab 19 € /Monat pro Nutzer, workflows Ab 50 € /Monat für 1000 Workflow-Ausführungen, WhatsApp campaigns Ab 20 € /Monat + Meta-Gebühr für 1000 Kampagnennachrichten; Enterprise is Auf Anfrage. We found no public information on whether the plan figure is per agent, the annual price, or minimum terms. 2 2
The Shop Operator
Two tiers carry public monthly figures — Free at "0 € /Monat" with one seat and 200 conversations, Pro at "Ab 87 € /Monat" from three seats, prices marked "zzgl. MwSt." with a monthly/annual toggle — and four add-ons are priced, including WhatsApp campaigns at "Ab 20 € /Monat + Meta-Gebühr für 1000 Kampagnennachrichten". Enterprise is "Auf Anfrage", a Team plan is referenced (WhatsApp channel available from Team) and we found no public information on its price, on per-seat scaling, or on a minimum term — so I cannot compute the full annual invoice for a given agent count. 2 2
The Integrator
A free tier at 0 €/Monat, the Pro plan from 87 €/Monat with minimum three seats, and publicly priced add-ons — AI Agent from 99 €/Monat, AI Copilot from 19 €/Monat pro Nutzer, WhatsApp campaigns from 20 €/Monat plus Meta fee for 1000 campaign messages, workflows from 50 €/Monat for 1000 workflow runs — with prices marked exclusive of VAT and monthly and annual billing offered. Enterprise is priced on request, the plan prices are starting figures without per-seat maths, and a Team package is referenced as the entry point for the WhatsApp channel without a price on the captured pages, so the annual invoice is not fully computable. 2 2
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
European sovereignty — proven facts
1 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 DE
unverified
Why unverified?The register number appears without a court, city or country name — Germany is derived from the HRB register format and the site's German-language context; no excerpt names a parent company or group seat. |
2/2 pts | 1 Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 31 Aug 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, Transfer impact assessment, Hosting location. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The register number appears without a court, city or country name — Germany is derived from the HRB register format and the site's German-language context; no excerpt names a parent company or group seat.
- 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.
- 60 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
- 23 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
- 13 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
- 9 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
- 5 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
- 3 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
- 2 hosting 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are 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 (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.userlike.com Checked 16 Nov 2026 +2 earlier captures: 11 Sep 2026, 31 Aug 2026 Details →
- 2 Pricing www.userlike.com Checked 16 Nov 2026 +1 earlier capture: 5 Oct 2026 Details →
- 3 Security / trust page — found from the homepage connect.lime-technologies.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
- 4 Ticketing, queues & SLA — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
- 5 Ticketing, queues & SLA — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
- 6 Channels in one queue — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
- 7 Channels in one queue — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
- 8 Knowledge base & deflection — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
- 9 Knowledge base & deflection — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
- 10 Customer data protection — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 11 Integrations & API — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
- 12 Integrations & API — found from sitemap docs.lime-connect.com Checked 16 Nov 2026 Details →
- 13 Structured-data backfill: markup only, no text or screenshot www.userlike.com Checked 8 Nov 2026 Details →