# Lime Connect

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

Canonical profile: https://ki-agentenkompass.de/en/agents/lime-connect/
Editor: [Michael Meierhoff](https://ki-agentenkompass.de/en/about/)
Sources reviewed: 2026-11-05
Basis: provider documentation. Examples are editorial suggestions, not hands-on product tests.

## Overview

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.

- Provider: Lime Connect (Userlike) GmbH
- Product family: Lime Connect
- Profile type: Customer communication platform with AI agents
- Environment: Website chat, WhatsApp, email, Instagram, Facebook Messenger, SMS and video; Message Center on the web and as a mobile app
- Connections: According to the page among others Lime CRM, Salesforce, HubSpot, Pipedrive, Zendesk, Freshdesk, Shopify, Slack and Jira, plus callback API, API actions and MCP
- 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.
- Pricing model: Pro from EUR 87 with annual, from EUR 105 with monthly payment; AI agent an additional EUR 99 per month with 100 conversations. Prices exclude VAT.

## Key features

### 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: https://connect.lime-technologies.com/en/products/ai-automation/

### 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: https://docs.lime-connect.com/features/connect-ai/actions/api-actions

### 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: https://docs.lime-connect.com/features/connect-ai/mcp

### 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: https://docs.lime-connect.com/features/workflows/general-nodes

### 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: https://docs.lime-connect.com/features/connect-ai/setups

### 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: https://docs.lime-connect.com/features/connect-ai/guidelines

### 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: https://docs.lime-connect.com/features/connect-ai/execution-history

## Example workflows

### 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.

### 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.

## Requirements and limits

### AI agent is an add-on

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

Source: https://connect.lime-technologies.com/en/pricing/

### AI Automation Hub is being discontinued

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

Source: https://docs.lime-connect.com/features/ai-automation-hub

### Few actions recommended

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

Source: https://docs.lime-connect.com/features/connect-ai/actions

### Models and model providers

Not yet confirmed: 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: https://connect.lime-technologies.com/en/products/ai-automation/

### Approval before actions

Not yet confirmed: 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: https://docs.lime-connect.com/features/connect-ai/mcp

### Independent multi-step work

Not yet confirmed: 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: https://docs.lime-connect.com/features/connect-ai/actions/workflow-actions

## 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.

## 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

Not publicly established · Sources accessed on: 2026-11-05

- [Lime Connect: AI automation](https://connect.lime-technologies.com/en/products/ai-automation/)

- [Lime Connect Docs: Connect AI](https://docs.lime-connect.com/features/connect-ai)

- [Lime Connect: AI info](https://connect.lime-technologies.com/en/ai-info/)

## 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: 2026-11-05

### Chat data in Germany

Available

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 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: https://connect.lime-technologies.com/en/products/data-privacy/
Official source: https://connect.lime-technologies.com/en/legal/dpa/
Official source: https://connect.lime-technologies.com/en/products/ai-automation/

### AI models on Azure and AWS Bedrock

With requirements

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 covered: EU

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

Official source: https://connect.lime-technologies.com/en/products/ai-automation/

### Training on customer data

With requirements

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 covered: EU/EEA

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

Official source: https://connect.lime-technologies.com/en/products/data-privacy/

### Data processing agreement and sub-processors

Available

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 covered: EU/EEA

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

Official source: https://connect.lime-technologies.com/en/products/data-privacy/
Official source: https://connect.lime-technologies.com/en/legal/dpa/
Official source: https://connect.lime-technologies.com/en/legal/privacy-policy/

### Third countries and "GDPR compliant"

Availability still unclear

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 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: https://connect.lime-technologies.com/en/legal/privacy-policy/
Official source: https://connect.lime-technologies.com/en/ai-info/

## 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: 2026-11-05

### Account used

Documented with conditions: 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: https://docs.lime-connect.com/features/single-sign-on-(sso)
Evidence: https://connect.lime-technologies.com/en/pricing/

### Admin approval

Documented: 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: https://docs.lime-connect.com/setup/team/team-setup
Evidence: https://docs.lime-connect.com/features/connect-ai/mcp

### Data access & team sharing

Documented with conditions: 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: https://docs.lime-connect.com/features/connect-ai/actions/api-actions
Evidence: https://docs.lime-connect.com/features/connect-ai/mcp

## Prices and included usage

Pricing checked: 2026-11-05

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.

### Free

EUR 0 per month

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

Price source: https://connect.lime-technologies.com/en/pricing/

### Pro

From 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.

Price source: https://connect.lime-technologies.com/en/pricing/

### Enterprise

On request

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

Price source: https://connect.lime-technologies.com/en/pricing/

### Connect AI Agent

Add-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.

Price source: https://connect.lime-technologies.com/en/pricing/

### Workflows

Add-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: https://connect.lime-technologies.com/en/pricing/

The AI Copilot costs EUR 19 per month per seat.

Third-party price information was not used.

Pricing details: https://connect.lime-technologies.com/en/pricing/

## 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: 2026-11-05

### Files and working state

Documented: 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: https://docs.lime-connect.com/features/connect-ai/knowledge-base
Evidence: https://connect.lime-technologies.com/en/products/data-privacy/

### Sign-ins

Documented: 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: https://docs.lime-connect.com/features/single-sign-on-(sso)
Evidence: https://connect.lime-technologies.com/en/pricing/
Evidence: https://docs.lime-connect.com/features/connect-ai/mcp
Evidence: https://docs.lime-connect.com/features/connect-ai/actions/api-actions

### Starting further runs

Documented with conditions: 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: https://docs.lime-connect.com/features/workflows/general-nodes
Evidence: https://docs.lime-connect.com/features/connect-ai/setups

### Human intervention

Documented with conditions: 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: https://connect.lime-technologies.com/en/products/ai-automation/
Evidence: https://connect.lime-technologies.com/en/products/workflows/
Evidence: https://docs.lime-connect.com/features/connect-ai/mcp

### Detecting errors

Documented with conditions: 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: https://docs.lime-connect.com/features/workflows/general-nodes
Evidence: https://docs.lime-connect.com/features/connect-ai/execution-history
Evidence: https://docs.lime-connect.com/features/connect-ai/mcp

### Resuming after failures

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

Evidence: https://docs.lime-connect.com/features/workflows
Evidence: https://docs.lime-connect.com/features/connect-ai/actions/api-actions

### 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.

## Memory and conversation continuity

Scope: No memory feature documented; variables in chat and fields in the contact profile
Sources accessed: 2026-11-05

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.

### Storage and scope

Partly documented: 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.

- [Lime Connect Guide: Workflows](https://docs.lime-connect.com/features/workflows)

### Selection and timing

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

- [Lime Connect Guide: Workflows](https://docs.lime-connect.com/features/workflows)

### Inspect, edit and delete

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

- [Lime Connect Guide: Actions nodes](https://docs.lime-connect.com/features/workflows/actions-nodes)

### Agent and channel boundaries

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

- [Lime Connect Guide: Knowledge base](https://docs.lime-connect.com/features/connect-ai/knowledge-base)

### Retrieval

Partly documented: 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.

- [Lime Connect Guide: Guidelines](https://docs.lime-connect.com/features/connect-ai/guidelines)

### Session reset and compaction

Documented: 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.

- [Lime Connect Guide: Execution history](https://docs.lime-connect.com/features/connect-ai/execution-history)

## Context

A paid plan with add-on and a maintained knowledge base. The agent works within customer conversations. The reviewed pages do not name the model provider, and the sub-processors are in the data processing agreement, which you have to request. "GDPR compliant" is a provider claim.

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.

## Open points

Europe, availability still unclear:
- Third countries and "GDPR compliant"

Requirements and limits, not yet confirmed:
- Models and model providers
- Approval before actions
- Independent multi-step work

## Sources

- https://connect.lime-technologies.com/

- https://connect.lime-technologies.com/en/products/ai-automation/

- https://connect.lime-technologies.com/en/products/workflows/

- https://connect.lime-technologies.com/en/pricing/

- https://connect.lime-technologies.com/en/products/data-privacy/

- https://connect.lime-technologies.com/en/ai-info/

- https://connect.lime-technologies.com/en/legal/dpa/

- https://connect.lime-technologies.com/en/integrations/

- https://connect.lime-technologies.com/en/legal/privacy-policy/

- https://connect.lime-technologies.com/en/about-us/

- https://docs.lime-connect.com/features/connect-ai

- https://docs.lime-connect.com/features/connect-ai/actions

- https://docs.lime-connect.com/features/connect-ai/mcp

- https://docs.lime-connect.com/features/connect-ai/setups

- https://docs.lime-connect.com/features/connect-ai/execution-history

- https://docs.lime-connect.com/features/connect-ai/guidelines

- https://docs.lime-connect.com/features/connect-ai/knowledge-base

- https://docs.lime-connect.com/features/connect-ai/actions/api-actions

- https://docs.lime-connect.com/features/connect-ai/actions/workflow-actions

- https://docs.lime-connect.com/features/ai-automation-hub

- https://docs.lime-connect.com/features/workflows

- https://docs.lime-connect.com/features/workflows/actions-nodes

- https://docs.lime-connect.com/features/workflows/general-nodes

- https://docs.lime-connect.com/features/single-sign-on-(sso)

- https://docs.lime-connect.com/setup/team/team-setup

- https://docs.lime-connect.com/userlike-is-now-lime-connect

## 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
- Website: https://connect.lime-technologies.com
- Reviewed: 2026-11-05

- Provider source: https://connect.lime-technologies.com/en/legal/privacy-policy/

- Provider source: https://docs.lime-connect.com/userlike-is-now-lime-connect

[Sources and method](https://ki-agentenkompass.de/en/sources/)
