Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Zendesk, Inc. · www.zendesk.de

Compare with Freshdesk → Compare with Intercom → Report an error on this page Is this your product? →

Link to this page

Zendesk: AI-assisted analysis on whats-best.ai Zendesk: 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.

Zendesk at a glance

Vendor
Zendesk, Inc.
Headquarters
Not stated on the vendor’s pages as of 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 19 Oct 2026
Panel verdict
The AI panel rates Zendesk 3.5/5, the mean of 6 judges. Zendesk scores highest on knowledge and self-service, which runs 8 to 9: judges credit a knowledge builder that turns interactions into article drafts, AI topic identification from ticket trends, approval workflows with review intervals, and localisation in over 40 languages. how scores are made
As of
Vendor pages captured 19 Oct 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Zendesk alternatives, European ones first →

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

The Support Lead

Weighted verdict

Runs a team of twelve against an SLA the sales team promised. Wants routing that reflects skill, timers that warn before they breach, and reporting she can take to a quarterly review. Reads "AI-powered" as a claim to be checked against the queue on a Monday morning.

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

Scored by The Support Lead

Panel median The Support Lead 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 Support Lead
Ticketing, queues & SLA 3.5 of 5 3.5 of 5
Channels in one queue 3.5 of 5 3.5 of 5
Knowledge base & deflection 4.5 of 5 4.5 of 5
Customer data protection 4 of 5 4 of 5
Integrations & API 3.5 of 5 3.5 of 5
European sovereignty 2 of 5 2 of 5
Pricing transparency 3.5 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 Support Lead

Routing is the strong suit: tickets from email, chat and messaging are assigned automatically, skills- and availability-based routing starts from the Professional plan, SLA-based timing from Growth, and macros, triggers, views and prebuilt dashboards are documented. What I can't find on the captured pages is the part my SLA lives on: breach warnings, escalation on missed targets, merge and split, and first-response and resolution reporting broken down by agent and queue. 2 6 7 6 9

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 Support Lead

Email, messaging, phone and social channels land in one central place with a unified agent workspace, and the voice pages show real queue handling — IVR, grouping, prioritisation, overflow, after-hours routing, queue-size limits and callback — plus WhatsApp Business Messaging and a customer portal with knowledge articles and community discussions. I found no public information on the messenger's consent handling or on whether a requester can see their own tickets in that portal, which is what separates a genuinely single history from channel logos. 2 6 8 9 6 8 10

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 Support Lead

Knowledge is a managed asset: help centres localised in over forty languages with approval workflows, scheduled publishing, depublishing and review intervals, article performance tracked so weak content is reworked or archived, and deflection reported as numbers such as the ratio of tickets to contacts and independently solved issues. AI topic identification mines ticket trends for new article recommendations and drafts, and generative and semantic search answer before a ticket is filed; on versioning of article content I found no public information. 7 10 11 10 11

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 Support Lead

The heavy items are documented: configurable data retention policies, data masking, PII redaction including automatic redaction of credit card numbers, access logs, audit logs on Enterprise plans, role-based access control, private attachments, documented support for access and erasure requests, and a published subprocessor list with names and locations. My caveat for a twelve-seat team is cost, since much of this sits in an add-on or behind Enterprise plans; on retention executed and evidenced per category, and on the vendor's own support access to customer instances, I found no public information. 3 5 3 5

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 Support Lead

More than 1,700 plug-and-play integrations in the marketplace, a documented REST API v2 with the v1 reference retired, SSO via SAML and OIDC, a sandbox environment on the top plan, and customer context from connected databases linked to ticket fields. I found no public information on SCIM provisioning, documented rate limits, or which of those marketplace integrations the vendor itself maintains — good enough to build on, not enough to plan a provisioning workflow from public pages alone. 2 7 8 12 5 9

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 Support Lead

The European elements are real — a selectable EWR data location, a Zendesk GmbH registered in Berlin on the legal notice, and a published subprocessor list with locations — but the chain doesn't close: copyright and vendor identity sit with Zendesk, Inc. in the United States, hosting runs on AWS, the default region for new accounts is unstated, and no data processing agreement is evidenced on the captured pages. As a buyer weighing this, that is one foot in Europe with the rest of the chain to verify contract by contract. 3 4 5 3 5

Report an error

Pricing transparency

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 Support Lead

A support lead can price most of the invoice from public pages: Support Team at 19 €, Suite Team at 55 € and Suite Professional at 115 € per agent and month with annual billing stated, add-ons priced the same way (Contact Center 82 €, Copilot 50 €, Workforce Engagement 50 €), and feature lists per tier. The top tier is a sales conversation, and I found no public information on VAT treatment, minimum term, or light-agent and contact limits, so the annual total for twelve agents is close to computable but not complete. 2 2 6

Report an error

European sovereignty — proven facts

1 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 Not determined unverified
Why unverified?

The page lists regions as equal choices and does not state which region is the default for new accounts, so the EWR option may require selection and a suitable plan.

— uncited Report an error
Hosting options EU region selectable unverified
Why unverified?

Der EWR-Standort ist nur eine von mehreren wählbaren Regionen; die Seite verweist auf eine Regional Data Hosting Policy, wonach Verfügbarkeit von Produkt und Plan abhängen kann, und nennt keinen Standardstandort.

1/1 pts 3 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Zendesk

Is Zendesk European?

No. whats-best.ai classifies Zendesk as Rest of world.

Where does Zendesk store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does Zendesk have a free plan?

Yes. Zendesk has a free plan, per the vendor’s page captured 19 Oct 2026.

What are the best alternatives to Zendesk?

As of 18 Nov 2026, the panel rates LiveAgent (3.5/5), Intercom (3.5/5) and Deskpro (3/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: Zendesk 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 (13)

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

  1. 1 Vendor homepage www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  2. 2 Pricing www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  3. 3 Privacy www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  4. 4 Legal notice www.zendesk.de Checked 16 Nov 2026 Details →
  5. 5 Security / trust page www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  6. 6 Ticketing, queues & SLA — found from sitemap www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  7. 7 Ticketing, queues & SLA — found from sitemap www.zendesk.de Checked 16 Nov 2026 Details →
  8. 8 Channels in one queue — found from sitemap www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  9. 9 Channels in one queue — found from sitemap www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  10. 10 Knowledge base & deflection — found from sitemap www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  11. 11 Knowledge base & deflection — found from sitemap www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  12. 12 Integrations & API — found from sitemap www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  13. 13 Integrations & API — found from sitemap www.zendesk.de Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →