Panel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Crisp IM SAS · crisp.chat
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.
Crisp at a glance
- Vendor
- Crisp IM SAS
- Headquarters
- Incorporated in France source, captured 26 Oct 2026
- Data hosting
- In the EU by default source, captured 26 Oct 2026
- Free plan
- Yes, per the vendor’s own page source, captured 26 Oct 2026
- Panel verdict
- The AI panel rates Crisp 3/5, the mean of 6 judges. Crisp, a customer-service and helpdesk platform from Crisp IM SAS of Nantes, scores highest on integrations: a REST API the vendor describes as its backbone — token scopes, published rate limits, webhooks, SDKs for four platforms, an MCP server — fronts a broad marketplace. how scores are made
- As of
- Vendor pages captured 26 Oct 2026 to 1 Nov 2026; evaluated by the panel 28 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Crisp, a customer-service and helpdesk platform from Crisp IM SAS of Nantes, scores highest on integrations: a REST API the vendor describes as its backbone — token scopes, published rate limits, webhooks, SDKs for four platforms, an MCP server — fronts a broad marketplace. Its weakest service scores land on the ticketing core: routing by round robin, origin, intent and custom strategies to agents, team pickup or sub-inboxes is well documented, but the judges found no public information on SLA targets, breach warnings, first-response or resolution reporting, or archive search, and the only service-level agreement named in the terms is reserved for Enterprise Plan customers. Omnichannel, knowledge self-service, customer data protection and sovereignty cluster at 6–7. Where scores differ, it is interpretive: on sovereignty, judges scoring 7 credit the published sub-processor list and relay servers in the US, UK and Singapore keeping connection logs only, while judges at 6 note the captured pages show no locations on that list. Pricing transparency scores 2–3: a free tier and a 14-day all-features trial are public, but no price for any paid tier is.
Speaks for it
- Documented REST API with token scopes, published rate limits, webhooks, an MCP server and SDKs for four platforms, described by the vendor as the backbone of the product
- Email, the website chat widget and messengers from WhatsApp to Telegram land in one shared inbox with the customer's past interactions visible
- The data processing agreement applies from account creation and is signable per workspace, with a French data protection officer and subject requests answered within a one-week target free of charge
- Hosting is stated as EU — messaging data in the Netherlands, plugin data in Germany on DigitalOcean — with standard contractual clauses cited for transfers
- The public help centre is brandable and multilingual, with analytics on visitors per article, reader feedback and the search keywords customers typed
Held against it
- We found no public information on SLA targets, breach warnings, first-response or resolution reporting, or search across conversations, with the only SLA in the terms reserved for Enterprise Plan customers
- Telephony reaches the shared inbox only through partner apps such as Aircall, Ringover and KrispCall, with no public information on call logging
- We found no public information on single sign-on, SCIM provisioning or a developer sandbox
- We found no public information on an audit log of agent access, redaction of conversation content, or attachment handling
- No monetary figure for any paid tier appears among the captured pages, so an annual invoice cannot be computed from them
Best for
- You need one shared inbox for email, your website chat widget and a dozen messengers, with the customer's history beside each conversation
- Your team builds its own tooling and wants a documented REST API with token scopes, published rate limits and webhooks rather than a partner-contact form
- Your compliance review needs in-product GDPR artifacts — a signable DPA from account creation, a named French data protection officer, and published retention periods per data category
- You want the vendor's stated EU hosting — messaging data in the Netherlands, plugin data in Germany — with standard contractual clauses cited for transfers
Avoid if
- You manage your queue against SLA promises — ask the vendor: the public pages we read do not show it
- You need voice in the queue natively — telephony arrives only through third-party apps such as Aircall, Ringover and KrispCall
- You must price the deployment before committing — the captured pages name a free tier, a 14-day all-features trial and a Plus plan but show no price for any paid tier
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 2 of 5 |
| Channels in one queue | 3.5 of 5 |
| Knowledge base & deflection | 3.5 of 5 |
| Customer data protection | 3 of 5 |
| Integrations & API | 3.5 of 5 |
| European sovereignty | 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
Routing is real and well documented: round-robin, origin, intent and custom strategies, assignment to specific agents, team pickup or a private sub-inbox, canned messages, reminders, and clear escalation paths from the AI agent to a human. But everything my team's SLA stands on is undocumented here — we found no public information on priorities, SLA timers or breach warnings, first-response or resolution reporting, merge and split, or search across conversations; the only service level agreement named in the terms is a contractual one reserved for Enterprise Plan customers. A four: stronger than a shared inbox with views, short of a queue I can manage against a promise. 1 5 6 8 2
The Agent Advocate
Routing is the strong suit: rules by round robin, origin or intent, department selection, team pickup and private sub-inboxes, canned messages with dynamic data and collision alerts against duplicate replies. But the hundredth reply is where tools fail, and I found no public information on priorities, statuses, SLA targets, response-time reporting or search across the conversation archive; the only SLA mentioned is a contractual document for Enterprise plan customers. 1 2 5 6 8
The Data Protection Officer
Conversations are routed by rules with round robin, origin, intent and custom strategies to named agents, open team pickup or private sub-inboxes, with assignment, canned messages, reminders, collision alerts and three documented escalation paths out of the AI agent. We found no public information on SLA targets or response-time reporting, ticket priorities, or search across the conversation archive. 5 6 8
The Shop Operator
Routing is real: conversations can be assigned to agents or teams, routed by round robin, origin or intent, with canned messages, private notes and collision alerts, plus a documented hand-over from the AI agent to humans. What I found no public information on is the measurement side — no queue-level SLA policies, no first-response or resolution reporting, no breach warnings and no search across tickets, which is what keeps a ten-thousand-conversation inbox survivable at peak volume. 2 5 6 8
The Integrator
Routing is real and documented: rules using Round Robin, origin and intent assign conversations to specific agents, leave them for team pickup or push them to a private sub-inbox, and the AI agent escalates to humans three documented ways with office-hours awareness. But we found no public information on priorities and statuses, SLA targets or response-time reporting, or search across the conversation archive — the measurable half of the engine is undocumented, so this sits below the mid-level. 5 6 8
The Skeptic
Routing is the real thing here — strategies named Round Robin, Origin, Intent and Custom, destinations of a specific agent, team pickup or a private sub-inbox, plus canned messages, reminders and collision alerts. But the measurement side is where I stop: the captured pages place the SLA document with Enterprise Plan customers only, and I found no public information on per-queue SLA targets, breach warnings, first-response or resolution reporting, search across tickets, or merge and split. Escalation exists, but only as the AI agent handing a conversation to a human. 5 6 8
Channels in one queue
Show reasoningHide reasoning
How this is scored
Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.
0 — No customer channel of its own; the product only works on tickets entered by hand or by another system.
3 — Email turned into tickets, with a web form or one further channel.
5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.
10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.
The Support Lead
Email, the website and app chat widgets, WhatsApp, Messenger, Instagram, Telegram, Line and more land in one shared inbox, with the customer's past interactions visible through the built-in CRM. Telephony arrives through named partner integrations such as Aircall, Ringover and KrispCall, with nothing captured on call logging or messenger consent handling, and we found no public information on a portal where a requester sees their own tickets. Six: one queue for nearly everything, voice bolted on, and self-service visibility for the customer unproven. 1 7 8 13
The Agent Advocate
Chat widget, email via Google and Microsoft inboxes, WhatsApp, Messenger, Instagram and a dozen further messaging channels land in one shared inbox with the customer's past interactions beside the conversation — one screen, not four tabs. Phone arrives through Aircall, Ringover and KrispCall rather than natively, and I found no public information on a customer portal where a requester sees their own tickets, or on WhatsApp consent handling. 1 5 7 8 13
The Data Protection Officer
Email, the website and mobile chat widget, and messengers from WhatsApp and Messenger to Instagram, Telegram and Line all land in one shared inbox, and the built-in CRM shows the customer's past interactions to whoever answers. Telephony arrives through integrations such as Aircall that bring calls into the same inbox, though we found no public information on a customer portal where a requester can see their own tickets, or on messenger consent handling. 1 7 13
The Shop Operator
This is the first thing I check — WhatsApp, the website chat widget, email, Instagram, Messenger and a dozen further channels land in one shared inbox, with the customer's data and past interactions visible whenever you communicate with someone, which is exactly the one-queue parcel desk I need. Phone reaches the inbox through partner apps such as Aircall, Ringover and KrispCall, and I found no public information on a customer portal where requesters see their own tickets, or on WhatsApp consent handling, so I stop short of the top. 1 5 7 8 13
The Integrator
Email, the chat widget and a dozen messengers from WhatsApp to Telegram land in one shared inbox with the customer's past interactions visible through the built-in CRM, and telephony reaches the inbox through Aircall, Ringover and KrispCall. What holds this back: we found no public information on a customer portal where a requester sees their own tickets, on consent handling for the messenger channels, or on call logging detail. 1 7 13 5
The Skeptic
I counted the logos: twelve messaging channels from WhatsApp and Messenger to Telegram, Viber, Discord and Twilio SMS, plus email, a chat widget and social, and the pages claim one unified, collaborative inbox with the customer's data and past interactions on screen. Telephony appears only as third-party apps — Aircall, Ringover, KrispCall — with calls "in your shared inbox", though we found no public information on call logging. We also found no public information on messenger consent handling or a customer portal where a requester sees their own tickets. 1 5 7 8 13
Knowledge base & deflection
Show reasoningHide reasoning
How this is scored
Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.
0 — No knowledge base or self-service of any kind; the product is a ticket inbox only.
3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.
5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning that flag stale content, and reporting on which articles deflect.
10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.
The Support Lead
A public help centre with custom branding, multilingual articles, a chat widget and mobile apps is documented, and the analytics go past vanity numbers: visitors per article, customer feedback for improving articles, and the keywords people type into the search box to guide new content. We found no public information on review dates or versioning that flag stale content, on suggestions offered before a customer submits, or on deflection reported as a number against ticket volume. Seven — knowledge is measured, not yet managed. 1 9 10
The Agent Advocate
A branded multilingual help centre with an internal knowledge base too, and analytics that count visitors per article, collect reader feedback and surface the keywords typed into search so you write the next article from evidence. The AI agent answers from your articles and a copilot assists agents, but I found no public information on draft-and-publish workflow, versioning or review dates, or deflection reported as a number against ticket volume. 1 6 9 10
The Data Protection Officer
A public help centre with custom branding and multilingual articles is documented, alongside an internal knowledge base and analytics reporting average visitors per article, reader feedback and the search keywords customers typed — which turns unanswered searches into a content plan — while the same content feeds the AI agent. We found no public information on versioning or review dates that flag stale articles, or on deflection measured against ticket volume. 1 9 10
The Shop Operator
The help centre is public-facing, brandable and multilingual, with real analytics — average visitors per article, customer feedback, and the keywords people typed into the search engine — which is how I spot the gaps before the tickets pile up. The AI agent is trained on the website, imported PDFs and knowledge base articles and handles conversations autonomously, so deflection is the design; I found no public information on versioning or review dates that flag stale articles, and deflection is not reported against ticket volume. 1 9 10
The Integrator
The knowledge base is a managed surface rather than a brochure: multilingual articles, a customizable help centre, an internal help centre for staff, and analytics covering visitors per article, reader feedback and the keywords people typed into search. Deflection runs through the AI agent trained on the articles, the website and imported PDFs. We found no public information on draft-and-publish workflow, review dates or versioning, or deflection reported as a number a team can act on. 10 9 1
The Skeptic
A searchable, multilingual, brandable help centre with real analytics: average visitors per article, customer feedback per article, and the keywords typed into the search box to guide new content — plus an AI agent trained on the articles. What I could not find: draft and publish workflow, review dates or versioning that flags stale articles, article suggestions inside agent replies, or deflection reported as a number. The analytics show visitors and feedback, not deflection. 1 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
The data processing agreement applies from account creation and can be signed, uploaded — paper signature allowed — and managed per workspace, a French data protection officer is named, subject requests are targeted inside one week free of charge, deletion on request and on termination is documented, and retention periods per data category are published. What I cannot evidence for my compliance review: an audit log of agent access or changes, redaction of ticket content, attachment handling, and retention rules a customer configures per queue. Six — strong on subject rights and the agreement, thin on in-product enforcement. 2 3 9 11 12
The Agent Advocate
This is documented properly: a DPA you download and sign from your account that applies from creation, a named DPO in France, breach notification within 24 hours, written per-category retention periods (system logs one year, contracts ten years, card data fifteen months), deletion on request and a one-week target for data-subject requests free of charge. I found no public information on an audit log of agent access or changes, redaction of ticket content, or attachment handling. 2 3 4 11 12
The Data Protection Officer
The data processing agreement applies from account creation and is signable, cancellable and even printable from inside the product, a French data protection officer is designated, access and erasure requests are answered within one week free of charge, and irreversible deletion plus a published retention schedule per data category are documented. We found no public information on an audit log of who read which conversation, redaction of conversation content, or attachment handling — and vendor access to customer data is stated only as need-to-know with internal security levels, not as consent-gated. 2 3 4 11 12
The Shop Operator
The paperwork is genuinely there: a data processing agreement applies from account creation, can be signed and uploaded from within the workspace per workspace, and there is a French data protection officer, deletion on request and on termination, an electronic copy on demand, and a stated answer target of one week for access requests free of charge. I found no public information on an audit log of agent access, redaction of ticket content, or how attachments are handled. 2 3 11 12
The Integrator
The data processing agreement applies from account creation, is downloadable per workspace with paper signature allowed, and subject-rights handling beats the legal minimum: access requests answered within one week and free of charge, portability stated, irreversible deletion on request and on termination. Retention is disclosed per data category, a subprocessor list is published, customer data is excluded from AI training, and vendor-side access is need-to-know with different security levels. We found no public information on an audit log of agent actions, redaction of ticket content, or configurable retention rules per queue. 3 11 12
The Skeptic
The GDPR machinery is unusually well documented: a data processing agreement that applies from account creation, downloadable and signable per workspace even on paper, a named data protection officer in France, deletion on request, retention stated per data category (system logs one year, card data fifteen months), subject access answered within a one-week target free of charge, and no AI training on customer data. For the in-product side I found no public information on an audit log of agent access to tickets, attachment handling, or redaction of ticket content. Role-based access controls are mentioned, but tied to internal documentation rather than ticket visibility. 2 3 4 11 12
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
The developer story holds up: a REST API described as the backbone of the product with scoped tokens, documented rate limits, webhooks, language libraries, an MCP server and a plugin system with its own marketplace, plus named CRM, shop and collaboration integrations and phone partners. We found no public information on single sign-on or SCIM provisioning or a sandbox environment, and customer context from other systems inside the conversation is evidenced only through sync partners like Hubspot. Seven. 6 13 14
The Agent Advocate
A real developer platform: REST API with token scopes and documented rate limits, a real-time API, webhooks, chat SDKs for web and mobile, a plugin framework with widgets and token scopes, and a marketplace spanning Hubspot, Salesforce, Pipedrive, WordPress, Shopify, Aircall, Stripe and the Zapier/Make/n8n set. I found no public information on SSO or SCIM provisioning or a sandbox, which keeps it short of the top band. 13 14
The Data Protection Officer
The documented REST API is described as the backbone of the product, with token scopes, published rate limits, webhooks, real-time and workflow APIs, an MCP server, chat SDKs for four platforms and a plugin framework with widgets, plus a categorised marketplace spanning CRM, shop, automation and telephony names such as Hubspot, Salesforce, Shopify, Zapier and Aircall. We found no public information on single sign-on and SCIM provisioning or a developer sandbox. 13 14
The Shop Operator
Shop systems are in the catalogue — Shopify, WooCommerce, Magento, Prestashop — alongside CRM names like HubSpot, Salesforce and Zoho, and the REST API is documented as the backbone of the product with rate limits, webhooks, token scopes and SDKs for web, iOS, Android and React Native, giving me documented routes to put order context in front of the agent. I found no public information on single sign-on or SCIM provisioning, or on a sandbox for building against the API. 13 14
The Integrator
The developer documentation is genuinely there, which is what I weigh hardest: the REST API is described as the backbone of the product, with a rate-limits page, scoped authentication tokens, webhook hooks for plugins and websites, a real-time API, SDKs for four platforms, an MCP server, and a plugin framework with marketplace submissions, token scopes and widgets — no partner-contact form standing in front of any of it. The catalogue covers the systems I have to reach: Hubspot, Salesforce, Pipedrive, Shopify, WooCommerce, Slack, Jira and the automation services. We found no public information on SCIM or SSO provisioning, a sandbox to build against, API versioning with a deprecation policy, or whether webhooks retry on failure. 14 13
The Skeptic
A real developer surface: a REST API the vendor calls the backbone of the product, with token scopes, documented rate limits, webhooks, a real-time API, SDKs for web and mobile, an MCP server, and a plugin system with its own marketplace — plus named integrations for Salesforce, HubSpot, Pipedrive, Shopify, Stripe, GitHub, Jira and Slack. We found no public information on SSO or SCIM provisioning, a sandbox, or which integrations the vendor itself maintains and whether they are bidirectional. Customer context in the ticket comes from Crisp's own CRM rather than a documented integration side-panel. 1 13 14
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.
The Support Lead
The company is Crisp IM SAS of Nantes with a French data protection officer and the CNIL as supervisory authority, hosting is documented as EU standard — messaging in the Netherlands, plugin data in Germany, on DigitalOcean — and a subprocessor list is referenced. Non-EU touches are named rather than buried: relay servers in the United States, the United Kingdom and Singapore keep connection logs, and card data sits with Stripe, with Standard Contractual Clauses cited where transfers apply; however, the locations on the subprocessor list are not established on the captured pages. Six — a genuinely European setup I could defend, with the tail of the chain still to verify. 3 4 9 11
The Agent Advocate
Crisp IM SAS is a French company with a Nantes address and SIREN, CNIL is the supervisory authority, and all customer data is stated to sit in the EU — messaging in the Netherlands, plugin data in Germany — on named DigitalOcean infrastructure. A sub-processor list is said to be available for review but locations are not shown in the captures, and US, UK and Singapore relay servers hold connection logs, with US-headquartered providers in the chain under Standard Contractual Clauses cited where transfers apply. 3 11 12
The Data Protection Officer
The contracting entity is a French company with a published SIREN and address in Nantes, CNIL as the supervisory authority, and all data is stated to be held in the EU on DigitalOcean infrastructure in the Netherlands and Germany. Non-EU processing is named — relay servers in the United States, United Kingdom and Singapore keeping connection logs only — with standard contractual clauses for transfers, but the published sub-processor list is not shown with locations in the captured pages, and United States-headquartered providers such as Cloudflare, DigitalOcean and Stripe sit in the chain. 3 11
The Shop Operator
The vendor's own statement puts the archive in Europe: messaging data in the Netherlands and plugin data in Germany on DigitalOcean servers run through an EU subsidiary, with a French company in Nantes under the CNIL and a published data processing agreement. Relay servers in the United States, United Kingdom and Singapore hold only connection logs with standard contractual clauses cited for transfers; the sub-processor list is published, but I found no public information on each listed partner's location, and no certification or self-hosted option is documented. 3 4 9 11
The Integrator
The contracting entity is Crisp IM SAS, a French company with a SIREN and a Nantes address, a designated DPO in France and the CNIL as supervisory authority; all data is stated to sit in the EU — messaging in the Netherlands, plugin data in Germany — on DigitalOcean servers, with a published subprocessor list and Standard Contractual Clauses for transfers. Non-EU processing is named rather than hidden: relay servers in the United States, United Kingdom and Singapore store connection logs only. US-headquartered providers sit in the chain, and we found no public information on a certification or a self-hosted option, which keeps this below the top level. 11 3 2
The Skeptic
A strong chain: a French contracting entity with a SIREN and a Nantes address, EU hosting with a named provider — DigitalOcean, messaging in the Netherlands, plugin data in Germany — a published sub-processor list, a data processing agreement with standard contractual clauses, and a French data protection officer under the CNIL. The edges are named too: relay servers in the US, UK and Singapore holding connection logs, and credit card data at Stripe, with US-headquartered providers in the chain; the page does not state the legal basis for each non-EU transfer. We found no public information on a self-hosted or private-cloud option or a published certification. 3 11 13
Pricing transparency
not rated — the vendor publishes no price
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
The terms document a free tier, a 14-day trial with all features and no card required, monthly plans without commitment that terminate immediately and are non-refundable, annual plans that run to period end, and monthly AI and WhatsApp credits that are lost if unused. But we found no price figures for any paid plan on the captured pages — no per-agent rate, no tier numbers, no VAT treatment — so I cannot compute what twelve agents cost us for a year. Two. 2 13
The Agent Advocate
A free tier and a fourteen-day all-features trial with no card are public, and the terms state monthly plans carry no commitment, the current month is non-refundable, and AI and WhatsApp credits renew monthly and are lost if unused. But I found no figure for any paid plan among the captured pages — the Plus plan is named without a price — so a support lead cannot compute an annual invoice from public information. 1 2 7 13
The Data Protection Officer
A free tier, a Plus plan and a 14-day all-features trial without card are named, and the terms spell out credit renewal, non-refundable current months and termination mechanics — but we found no public price for any paid tier among the captured pages, so a support lead cannot compute the annual invoice for their agent count from them. 1 2 10
The Shop Operator
What is public is the shape of the deal: a free subscription at no charge, a fourteen-day trial of all features with no card required, monthly plans without commitment terminable at any time, and AI and WhatsApp usage metered in monthly credits that are lost at each renewal. I found no public information on a price for the paid plans — no per-agent figure, no plan prices, no VAT treatment — so I cannot compute an annual invoice for my agent count from these pages. 1 2 13
The Integrator
A free subscription and a 14-day all-features trial with no card are public, and the billing mechanics are documented: monthly plans without commitment, annual plans effective at period end, no refunds, and AI and WhatsApp credits renewed monthly with unused credits lost. But we found no public price figures for the paid plans on the captured pages, so I cannot compute an annual invoice for a given agent count. 2 1 13
The Skeptic
This is where a support lead is stuck: the captured pages show a free tier, a fourteen-day all-features trial with no card, and a plan named Crisp Plus, but not one monetary figure for any paid tier, per-agent or otherwise, appears on them. The metering is at least visible — AI and WhatsApp credits renewed monthly and lost if unused, while the AI Helpdesk features are described as included in Crisp Plus — so the buyer can see the shape of the bill but not its size. We found no public information on VAT treatment, minimum term or per-agent maths from which an annual invoice could be computed. 1 2 3
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in FR | 2/2 pts | 3 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?Relay servers in the US, UK and Singapore retain connection logs outside the EU, and the privacy policy itself only commits to storing data in Europe 'where possible'. |
2/4 pts | 11 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?Concluding the DPA involves downloading a PDF, signing it electronically or on paper, and uploading it back from an owner account, but no contact with the vendor is required. |
1/1 pts | 12 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Crisp
Is Crisp European?
Not determined: the vendor’s pages as captured do not say where Crisp is based. Its vendor, Crisp IM SAS, is incorporated in France, per the vendor’s page captured 26 Oct 2026.
Where does Crisp store data?
Crisp stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 26 Oct 2026.
Does Crisp have a free plan?
Yes. Crisp has a free plan, per the vendor’s page captured 26 Oct 2026.
What are the best alternatives to Crisp?
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: Crisp alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 26 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Concluding the DPA involves downloading a PDF, signing it electronically or on paper, and uploading it back from an owner account, but no contact with the vendor is required.
- Weak sourcing — Hosting location. Relay servers in the US, UK and Singapore retain connection logs outside the EU, and the privacy policy itself only commits to storing data in Europe 'where possible'.
- 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.
- 4 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
- 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
- 1 compliance 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
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page crisp.chat Checked 26 Oct 2026 Details →
- 2 Terms of service — found from the homepage crisp.chat Checked 26 Oct 2026 Details →
- 3 Privacy policy — found from the homepage crisp.chat Checked 26 Oct 2026 Details →
- 4 Security / trust page — found from the homepage docs.crisp.chat Checked 26 Oct 2026 Details →
- 5 Ticketing, queues & SLA — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
- 6 Ticketing, queues & SLA — found from sitemap help.crisp.chat Checked 26 Oct 2026 Details →
- 7 Channels in one queue — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
- 8 Channels in one queue — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
- 9 Knowledge base & deflection — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
- 10 Knowledge base & deflection — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
- 11 Customer data protection — found from sitemap help.crisp.chat Checked 26 Oct 2026 Details →
- 12 Customer data protection — found from sitemap help.crisp.chat Checked 26 Oct 2026 Details →
- 13 Integrations & API — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
- 14 Integrations & API — found from sitemap docs.crisp.chat Checked 26 Oct 2026 Details →
- 15 Code repository (open-source licence) — found from the homepage github.com Checked 1 Nov 2026 Details →