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

Crisp: AI-assisted analysis on whats-best.ai Crisp: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

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

Crisp alternatives, European ones first →

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

The Integrator

Weighted verdict

Has to wire the helpdesk into a CRM, a shop and an identity provider that all predate it. Wants a documented API with rate limits, webhooks that retry, SCIM, and a sandbox. Reads a partner-contact form on an integrations page as a missing API.

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

Scored by The Integrator

Panel median The Integrator This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Integrator
Ticketing, queues & SLA 2 of 5 2 of 5
Channels in one queue 3.5 of 5 3.5 of 5
Knowledge base & deflection 3.5 of 5 3.5 of 5
Customer data protection 3 of 5 3.5 of 5
Integrations & API 3.5 of 5 3.5 of 5
European sovereignty 3 of 5 3.5 of 5

Ticketing, queues & SLA

How this is scored

The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.

0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.

3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.

5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.

8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.

10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.

Report an error

The 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

Report an error

Channels in one queue

How this is scored

Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.

0 — No customer channel of its own; the product only works on tickets entered by hand or by another system.

3 — Email turned into tickets, with a web form or one further channel.

5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.

8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.

10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.

Report an error

The 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

Report an error

Knowledge base & deflection

How this is scored

Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.

0 — No knowledge base or self-service of any kind; the product is a ticket inbox only.

3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.

5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.

8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning that flag stale content, and reporting on which articles deflect.

10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.

Report an error

The 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

Report an error

Customer data protection

How this is scored

A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.

0 — The vendor's own terms state that ticket content is used for purposes beyond providing the service, or that a data processing agreement is not offered.

3 — A privacy policy and a data processing agreement (DPA) offered, with agent roles that limit what an agent can do.

5 — A DPA published or signable online, agent roles and group- or queue-level visibility, and deletion of tickets or of a requester's data documented in the help centre.

8 — Automatic retention or deletion rules per queue or data category, attachment handling stated, an audit log of agent access or changes, documented support for access and erasure requests, and redaction of ticket content.

10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.

Report an error

The 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

Report an error

Integrations & API

How this is scored

The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.

0 — A closed tool with no API and no integrations; context is copied in by hand.

3 — A handful of named integrations or a connector service such as Zapier, or an API with basic documentation.

5 — Named integrations for common CRM, shop or collaboration tools, a documented REST API, and webhooks or triggers that call other systems.

8 — An app marketplace with maintained bidirectional integrations, customer context from other systems shown inside the ticket, SSO and SCIM provisioning, documented rate limits and a sandbox.

10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.

Report an error

The 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

Report an error

European sovereignty

How this is scored

Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.

0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.

3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.

5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.

Report an error

The 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

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price or one priced tier, per agent or flat.

5 — Per-agent prices public for the main tiers with the billing period stated and the main features per tier listed.

8 — Every tier and add-on priced publicly with per-agent maths, telephony or messenger costs and light-agent or contact limits given, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.

10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.

Report an error

The 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

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location 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

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (15)

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

  1. 1 Vendor page crisp.chat Checked 26 Oct 2026 Details →
  2. 2 Terms of service — found from the homepage crisp.chat Checked 26 Oct 2026 Details →
  3. 3 Privacy policy — found from the homepage crisp.chat Checked 26 Oct 2026 Details →
  4. 4 Security / trust page — found from the homepage docs.crisp.chat Checked 26 Oct 2026 Details →
  5. 5 Ticketing, queues & SLA — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
  6. 6 Ticketing, queues & SLA — found from sitemap help.crisp.chat Checked 26 Oct 2026 Details →
  7. 7 Channels in one queue — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
  8. 8 Channels in one queue — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
  9. 9 Knowledge base & deflection — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
  10. 10 Knowledge base & deflection — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
  11. 11 Customer data protection — found from sitemap help.crisp.chat Checked 26 Oct 2026 Details →
  12. 12 Customer data protection — found from sitemap help.crisp.chat Checked 26 Oct 2026 Details →
  13. 13 Integrations & API — found from sitemap crisp.chat Checked 26 Oct 2026 Details →
  14. 14 Integrations & API — found from sitemap docs.crisp.chat Checked 26 Oct 2026 Details →
  15. 15 Code repository (open-source licence) — found from the homepage github.com Checked 1 Nov 2026 Details →