AGENT PROFILES

Lime Connect

Lime Connect (Userlike) GmbH · Specialist agents

Customer communication platform from Cologne, formerly Userlike, with AI agents that act in connected systems through API actions, MCP and workflows.

Typical tasks

Availability in Europe
Added to the catalog on Customer communication platform from Cologne, formerly Userlike, with AI agents that act in connected systems through API actions, MCP and workflows.Details
01

What it does

7 features

Lime Connect · Customer communication platform with AI agents

Product and access

Lime Connect has been the new name of Userlike since 10 September 2025. According to the documentation Userlike has belonged to Lime Technologies from Lund, Sweden, since 2021. The company is called Lime Connect (Userlike) GmbH and is based in Cologne.

Core features

7 features from provider sources · checked on 5 November 2026. Availability and limits are directly below.

  • AI agent in customer conversations

    The AI agent answers requests from the knowledge base through website chat, WhatsApp, email and other channels. According to the page it also handles orders, complaints and appointments.

    Source 2
  • API actions

    The agent sends HTTP requests to external systems with GET, PATCH, POST, PUT or DELETE. You define when it triggers the action and filter the response with JMESPath.

    Source 18
  • MCP servers

    MCP servers connect, for example, CRM, ticketing or shops. In the agent you enable individual actions, for example for Shopify. According to the documentation OAuth is not supported, but an auth token is.

    Source 13
  • Workflows

    Rule-based processes in the visual editor. Triggers are new conversation, webhook (beta), handover from the agent, a time from a contact field or manual start. Workflows are an add-on.

    Source 23
  • AI Copilot

    The Copilot suggests answers from the knowledge base to staff and summarises conversations as a note. It does not chat directly with contacts.

    Source 14
  • Guidelines

    Fixed rules apply to every action of the agent, at most 20 per setup and 2,000 characters each. Above 100% "instruction load" the AI follows the rules less reliably according to the documentation.

    Source 16
Show all 7 features
  • Execution history

    The view shows the agent's sessions, ratings and resolution rate, with a detail view for each AI answer. The page does not describe error messages and retention.

    Source 15

Usable AI models

Models not stated

According to the vendor, the models run exclusively on Microsoft Azure and AWS Bedrock with server locations in the EU. The pages checked do not name the models behind this. They also describe no model choice or keys of your own.

Model families named

None named

Model choice
Not stated
Your own API key
Not stated
Router or custom endpoint
Not stated
Local models
Not stated

The rating covers the generally available main access. Not publicly established · Sources accessed on

Lime Connect: AI automation · Lime Connect Docs: Connect AI · Lime Connect: AI info

02

Does it fit my task?

2 practical tasks · 6 requirements and limits

A good fit if …

  • you want to automate customer requests across several channels and hand over to your team
  • the agent should fetch and change data from CRM or shop through API actions or MCP
  • you want to start with a small agent budget per conversation

Less suitable if …

  • you want an agent for internal tasks or processes without a customer conversation
  • each write action has to be confirmed by a person in advance
  • you want to check the model provider and the sub-processors publicly before making a request

Editorial assessment based on provider documentation. Not a product test.

Practical tasks

Editorial examples based on documented features. No product tests performed.

01

Fetch order data in chat

Your input
An AI agent with an API action on the shop system and a clear trigger condition.
Possible result
The agent fetches the data and answers in chat, filtered to the relevant fields.
What to check
Limit the response with JMESPath and check it in the detail view of the execution history.
02

Capture a meter reading through a workflow

Your input
A workflow action that hands over to a workflow with the start "On Connect AI handover".
Possible result
The workflow collects details in a rule-based way and saves them to the contact profile.
What to check
Check the faulty node in the execution log and create fallback paths for missing input.
EDITORIAL EXAMPLE

Have an AI agent fetch order data through an API action and hand over to the team after a bad rating.

Your possible prompt

Handle this customer request using the approved knowledge sources. Prepare a sourced response and hand unclear cases to the service team. Check permissions before taking actions in customer systems.

Adjust the task, data and permissions.

Requirements and limits

  • Requirement

    AI agent is an add-on

    The AI agent costs an additional EUR 99 per month and requires Pro or Enterprise. The Free plan does not include it.

    Source 4
  • Limitation

    AI Automation Hub is being discontinued

    According to the documentation the hub will be discontinued on 31 December 2026; its successor is Connect AI.

    Source 20
  • Limitation

    Few actions recommended

    The documentation advises keeping the number of actions small, because otherwise errors and confusion increase for the AI.

    Source 12
  • Not yet confirmed

    Models and model providers

    The product page names Azure and AWS Bedrock as hosting for the models, but no model name and no model provider. The documentation also names no model choice.

    Source 2
  • Not yet confirmed

    Approval before actions

    The reviewed pages describe no confirmation before an API or MCP action. Workflows only say generally that people can be brought in when needed.

    Source 13
  • Not yet confirmed

    Independent multi-step work

    The pages describe individual actions and rule-based workflows. They do not say how the agent chains several steps itself, handles errors or returns to the conversation.

    Source 19
03

Can I use it?

With requirements

Europe & regional availability

Privacy page, DPA page, privacy policy and AI product page reviewed. The data processing agreement itself and the sub-processor list are available only on request and were not seen.

Reviewed scope: Hosted platform; data in Germany according to the provider, AI models in the EU
Reviewed on:

  • Available

    Chat data in Germany

    According to the privacy page chat data is stored on servers in Germany and processed exclusively in Europe. The DPA page names ISO 27001-certified server infrastructure in Germany, but not its operator.

    Region, reason and source

    Region covered: Germany and Europe

    Documented reason: Provider statement. According to the text the certificate refers to the infrastructure, and the page names no operator. The AI product page, by contrast, speaks of servers in Europe.

    Official source · connect.lime-technologies.com · Official source · connect.lime-technologies.com · Official source · connect.lime-technologies.com

  • With requirements

    AI models on Azure and AWS Bedrock

    According to the AI product page the models run exclusively on Microsoft Azure and AWS Bedrock, with all server locations in the EU. The page does not name which models and regions these are.

    Region, reason and source

    Region covered: EU

    Documented reason: Model name, model provider and region open.

    Official source · connect.lime-technologies.com

  • With requirements

    Training on customer data

    In a feature card the privacy page rules out training external AI models on customer data without exception. Its FAQ qualifies this: not "without an appropriate legal basis".

    Region, reason and source

    Region covered: EU/EEA

    Documented reason: The two statements differ; the data processing agreement would be decisive.

    Official source · connect.lime-technologies.com

  • Available

    Data processing agreement and sub-processors

    You request the data processing agreement through a form; according to the page it contains the full sub-processor list. The public page names only Cloudflare Turnstile for the form. The privacy policy names for the website among others AWS and 360dialog, and no AI provider.

    Region, reason and source

    Region covered: EU/EEA

    Documented reason: Requesting the agreement is documented; content and names are not public.

    Official source · connect.lime-technologies.com · Official source · connect.lime-technologies.com · Official source · connect.lime-technologies.com

  • Availability still unclear

    Third countries and "GDPR compliant"

    According to the privacy policy WhatsApp also stores data outside the EU, over which the provider says it has no influence. For the website it names US services and partly still refers to the EU-US Privacy Shield. "GDPR compliant" is a provider claim.

    Region, reason and source

    Region covered: EU/EEA and beyond

    Documented reason: The non-public agreement applies to the product; the policy mainly concerns the website. No authority assessment found.

    Official source · connect.lime-technologies.com · Official source · connect.lime-technologies.com

Europe and regulation explained

Accounts & permissions

Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use.

Configuration covered: Hosted platform with roles for operators

Sources reviewed:

Show all 3 points
  • Documented with conditions

    Account used

    SSO uses OpenID Connect. In the advanced setup the identity provider provisions operators and roles. The pricing page lists SCIM/SSO only on Enterprise; the documentation refers those interested to the provider.

    Evidence · Evidence
  • Documented

    Admin approval

    The roles are Owner, Manager, Admin, Staff, Analyst and Agent. In higher plans role rights can be adjusted. The pages do not describe human approval of individual agent actions.

    Evidence · Evidence
  • Documented with conditions

    Data access & team sharing

    The agent uses only enabled actions. MCP servers receive an auth token, and the documentation advises minimal rights. API actions can also write and delete; the rights depend on the stored access in the target system.

    Evidence · Evidence
04

Memory and conversation continuity

1 of 6 criteria documented

The documentation names no dedicated memory feature. Workflows keep input for the duration of the chat, and additional nodes write it to the contact profile.

No memory feature documented; variables in chat and fields in the contact profile

Sources accessed:

Documentation by criterion

StoragePartly documented

Storage and scope

Workflow variables hold input for the duration of the chat, and further nodes save it to the contact profile. The documentation names no dedicated storage for the AI agent.

SelectionPartly documented

Selection and timing

In workflows you define yourself what gets saved. The documentation does not say whether the AI agent selects anything itself.

Edit & deleteNot publicly established

Inspect, edit and delete

According to the documentation contact fields can be changed by a node. It names no view for agent memories.

Access boundariesPartly documented

Agent and channel boundaries

The agent or Copilot accesses the whole knowledge base or individual folders. The documentation does not describe memory limits between agents or channels.

RetrievalPartly documented

Retrieval

According to the documentation the knowledge base is searched as needed, guidelines always apply. It does not say how a contact's earlier conversations feed in.

New conversationsDocumented

Session reset and compaction

According to the documentation a session ends on forwarding or ending by the agent, after the timeout or when the customer leaves the website. It says nothing about compaction.

05

Cost and effort

5 plans · Prices as of 5 November 2026

Prices and included usage

Pricing checked

Prices exclude VAT. The AI agent is included in no plan but is an add-on for Pro and Enterprise. The trial lasts 14 days.

PlanPriceIncluded
FreeEUR 0 per month

1 seat, 1 channel, 200 conversations; no AI agent.

ProFrom EUR 105 per month with monthly, EUR 87 with annual payment

At least 3 seats, unlimited channels and conversations, 10 WhatsApp numbers, 5 chatbots, Basic API.

EnterpriseOn request

At least 5 seats, 20 WhatsApp numbers, 10 chatbots, Full API, Advanced Routing, SCIM/SSO, account manager.

Connect AI AgentAdd-on: EUR 99 per month including 100 conversations

Billed per conversation. According to the FAQ unused conversations expire only at the end of the contract.

WorkflowsAdd-on: EUR 50 per month for 1,000 workflow runs

Workflows and workflow actions. The documentation refers to the account manager or support for booking.

Price source

  • The AI Copilot costs EUR 19 per month per seat.
  • Third-party price information was not used.

Setup

Test for 14 days with Pro features, then the account moves to Free. The documentation recommends: knowledge base first, then AI agent, then AI Copilot. You set up actions and MCP per agent.

Operation & oversight

Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.

Deployment covered: Hosted operation by the provider

Sources reviewed:

Editorial assessment

Lime Connect documents real tool calls but stays tied to the customer conversation. Approvals before actions, error handling and the model provider remain open. You add the agent add-on and the workflow add-on to the base plan.

Show all 6 points
  • Documented

    Files and working state

    The knowledge base holds up to 3,000 items per organisation. According to the privacy page you set automatic deletion periods for transcripts and messages yourself. It names no default periods.

    Evidence · Evidence
  • Documented

    Sign-ins

    According to the pricing page SSO through OpenID Connect is reserved for Enterprise. MCP connections use an auth token, and OAuth is not supported. API actions allow configurable authentication, whose options the page does not explain.

    Evidence · Evidence · Evidence · Evidence
  • Documented with conditions

    Starting further runs

    The agent answers customer requests. Workflows start on a new conversation, by webhook (beta), after handover from the agent, at a time from a contact field or manually. The pages do not describe schedules for the agent itself.

    Evidence · Evidence
  • Documented with conditions

    Human intervention

    According to the page the agent hands over to the team with full context. According to the page workflows let people step in when needed. The reviewed pages do not describe approval before individual actions.

    Evidence · Evidence · Evidence
  • Documented with conditions

    Detecting errors

    On workflow errors the execution log shows the faulty node. The agent's execution history shows statistics and details per answer, but no error messages. For MCP the documentation recommends the MCP Inspector.

    Evidence · Evidence · Evidence
  • Open in reviewed sources

    Resuming after failures

    Some workflow nodes need paths for skipped input. The documentation does not describe error handling, retries and timeouts for API actions.

    Evidence · Evidence
06

Evidence and open questions

26 sources · 4 open points

Open points

The reviewed sources contain no reliable information on these points. A gap says nothing about the product.

Europe: Availability still unclear

Requirements and limits: not yet confirmed

Sources and evidence

Official website, pricing page, privacy pages and documentation reviewed. The data processing agreement text and sub-processor list are available only on request and were not seen. Example tasks are editorial. Our own hands-on tests are still pending.

Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.

Read profile as Markdown

How we assess the sources

Provider

Lime Connect (Userlike) GmbH in Cologne belongs to the Swedish Lime Technologies and offers a customer communication platform.

Operator
Lime Connect (Userlike) GmbH
Organization
Provider
Provider sourcesSource 1 Source 2 Reviewed
Changes to this profile 1
  • Customer communication platform from Cologne, formerly Userlike, with AI agents that act in connected systems through API actions, MCP and workflows.

These notes describe editorial changes. Source and pricing review dates appear in their respective sections.