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 panel's verdict

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. The remaining criteria — ticketing, omnichannel, customer data protection, integrations, pricing transparency — each span a single point between 6 and 8; no flagged split was flagged, and rationales repeatedly report finding no public information on SLA breach warnings and escalation, merge and split, SCIM provisioning and rate limits. Pricing is partly computable — 19 €, 55 € and 115 € per service agent per month billed annually, add-ons at 82 € and 50 € — but Suite Enterprise is contact-sales and VAT, minimum term and light-agent limits are not public. Sovereignty is weakest at 4 to 5: the EEA is one of four selectable regions, a Zendesk GmbH is registered in Berlin with a published subprocessor list, yet the vendor is Zendesk, Inc. of San Francisco, no default region is stated, and no contracting entity or data processing agreement appears on the captured pages.

Report an error

Speaks for it

  • Knowledge and self-service scored 8 to 9 on a managed content lifecycle — approval workflows, scheduled publishing, depublishing and review intervals in over 40 languages
  • Omnichannel routing assigns email, chat and messaging tickets in every plan, with WhatsApp Business Messaging named and voice handling IVR, queue limits and callback
  • A marketplace of more than 1,700 plug-and-play integrations sits beside a documented REST API v2 and app framework
  • Per-agent prices are public with the billing period stated — Support Team 19 €, Suite Team 55 €, Suite Professional 115 €, plus add-ons at 82 € and 50 € per agent per month
  • Privacy tooling is documented for access, erasure, portability and objection requests, with automatic credit-card redaction and a published subprocessor list with names and locations

Report an error

Held against it

  • Sovereignty scored 4 to 5, with the EEA only one of four selectable regions, no default region stated, and no contracting entity or data processing agreement on the captured pages
  • No public information was found on SLA breach warnings and escalation, ticket merge and split, or first-response and resolution reporting by agent and queue
  • Configurable retention policies, data masking, PII redaction and access logs sit in the paid add-on for extended data protection and security, with audit logs limited to Enterprise plans
  • No public information was found on SCIM provisioning or documented rate limits
  • Suite Enterprise is contact-sales only, and VAT treatment, minimum term, light-agent and contact limits are not public

Report an error

Best for

  • You need a multilingual help centre run as a managed asset — the top scores of the bench, 8 to 9, sit on knowledge and self-service
  • Your team unifies email, messaging, phone and social channels in one workspace and WhatsApp Business Messaging matters
  • You build on a large integration marketplace and a documented REST API v2, and can settle rate limits with the vendor before wiring systems
  • You can price most of the invoice from public per-agent figures and accept a contact-sales top tier

Report an error

Avoid if

  • You must close a European legal chain before purchase — ask the vendor: the public pages we read do not show it
  • Your SLA regime depends on documented breach warnings and escalation — ask the vendor: the public pages we read do not show it
  • You need the exact annual invoice up front — Suite Enterprise is contact-sales and VAT treatment, minimum term and light-agent limits are not public
  • You expect data masking, retention policies and access logs in the base plan — they sit in a paid add-on, with audit logs limited to Enterprise plans

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Ticketing, queues & SLA 3.5 of 5
Channels in one queue 3.5 of 5
Knowledge base & deflection 4.5 of 5
Customer data protection 4 of 5
Integrations & API 3.5 of 5
European sovereignty 2 of 5
Pricing transparency 3.5 of 5

Ticketing, queues & SLA

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

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

The Agent Advocate

The ticketing pages document the working machinery I judge by: automations and triggers, macros and views in the agent manual, skill- and urgency-based routing from the Professional plan, SLA-based timing from the Growth plan, and customer context on every ticket. I found no public information on business-hours SLA policies with breach warnings, merge and split, or first-response and resolution reporting broken down by agent and queue, so I hold it just under the full working tier. 2 6 7

Report an error

The Data Protection Officer

The pages document tickets auto-assigned by omnichannel, skills and intent routing, SLA-based timing from the Growth plan, urgency and skills prioritisation from Professional, plus automations, triggers, macros, views and preconfigured analytics dashboards. I found no public information on business-hours SLA policies with breach warnings, ticket merge and split, or first-response and resolution reporting broken down by agent and queue, so this is strong routing rather than managed workload. 2 6 7 6

Report an error

The Shop Operator

Routing is what I buy for: omnichannel routing sits in every plan, tickets are distributed by urgency and skills from the Professional plan, and SLA-based timing arrives from the Growth plan, with views, macros, automations and triggers documented in the agent manual and real-time dashboards stated. I found no public information on business-hours SLA policies per queue with breach warnings and escalation, on merging and splitting tickets, or on first-response and resolution reporting broken down by agent and queue. 6 6 2 7

Report an error

The Integrator

The engine is documented: omnichannel routing auto-assigns tickets from email, chat and messaging in every plan, SLA-based timing arrives with the Growth plan, urgency-and-skills prioritisation with Professional, and the agent guide covers views, macros and triggers on top of preconfigured dashboards, while the voice pages add business-hours routing, overflow handling and callback queues. I found no public information on SLA breach warnings and escalation, ticket merge and split, or first-response and resolution reporting broken down by agent and queue, so I stop just short of the strongest rating. 2 6 7 8

Report an error

The Skeptic

Routing is documented at the level I look for — omnichannel assignment included in all plans, skills-based and intent-based routing, automations and triggers, macros and views in the agent guide — but the pages gate the timing pieces: SLA-based timing starts from the Growth plan and urgency-and-skills prioritisation from Professional. Preconfigured analytics dashboards are named, yet I found no public information on business-hours SLA policies per queue with breach warnings and escalation, on merge and split, or on first-response and resolution reporting by agent and queue. 2 6 7 6 9

Report an error

Channels in one queue

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

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

The Agent Advocate

Email, messaging, phone and social channels are documented as landing in one central place, with omnichannel routing assigning email, chat and messaging tickets in every plan and a unified agent workspace named — one screen, not four tabs. WhatsApp Business Messaging, IVR with queue management and callback, and a customer portal with community discussions are all documented; the captured pages do not show the consent handling around the messenger, which is the one piece of the bundle I could not verify. 6 9 8 11

Report an error

The Data Protection Officer

Email, messaging, phone and social channels are stated to come together in one ticketing system with a unified agent workspace, WhatsApp Business Messaging is named, and voice arrives with IVR, queue limits, overflow handling and callback. We found no public information on consent handling for the messenger channels or on call logging, and the customer portal is listed without a statement that a requester can see their own tickets there. 6 8 9 8 10

Report an error

The Shop Operator

Email, messaging, phone and social channels are documented as landing at one central place in the ticketing with a unified agent workspace, and WhatsApp Business Messaging is named as a channel — the WhatsApp-in-one-queue test I run. Telephony comes with IVR, grouping, prioritisation, overflow, after-hours routing and callback, and a self-service portal with community discussions exists; I found no public information on messenger consent handling or call logging, which keeps it short of channel-as-detail. 6 6 9 8 11

Report an error

The Integrator

Email, messaging, phone and social channels are documented as arriving in one ticketing system with a unified agent workspace, WhatsApp Business Messaging is named, the voice pages cover IVR, queue limits and callback, and a customer-facing portal with knowledge articles and community discussions exists. I found no public information on consent handling for messengers or on a requester viewing their own tickets in the portal, which keeps this one notch below the best case. 6 9 8 11

Report an error

The Skeptic

The ticketing page states email, messaging, phone and social channels are unified in one central place, and omnichannel routing that assigns tickets from email, chat and messaging is stated as included in all plans; WhatsApp Business Messaging, a customer self-service portal with community discussions, and telephony with IVR, queue limits, callback and business-hours settings are all documented. What I could not find is the messenger's consent handling or any statement that a customer can move between channels mid-issue without repeating themselves. 6 8 9 6 8 10 11

Report an error

Knowledge base & deflection

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

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

The Agent Advocate

This is knowledge run as an asset, not a folder of articles: AI turns support interactions into structured drafts to close content gaps, ticket trends recommend new help-centre articles, review intervals and approval workflows keep content current, article performance is tracked, and self-service shows up as ticket-to-contact ratio and independently solved issues, localised across forty-plus languages. I stop short of the top only because article version history itself is not spelled out on the captured pages. 10 11 11

Report an error

The Data Protection Officer

Knowledge is documented as a managed asset: AI topic identification mines ticket trends to recommend new articles, a knowledge builder turns support interactions into article drafts, article performance and a ticket-to-contact ratio with independently solved issues are reported, and content runs through approval workflows with review intervals and depublishing in 40-plus languages. The one gap I can see is an explicit statement of article suggestions pushed to the agent while they answer, which keeps it just short of the top level. 10 11 10 11

Report an error

The Shop Operator

The help centre is run as an asset: branded help centres localised in over 40 languages, approval workflows with scheduled publishing, depublishing and review intervals, article performance tracked so weak content gets reworked or archived, and ticket trends mined to recommend new articles — gaps filled from the tickets themselves. The self-service metrics include the ticket-to-contact ratio and independently solved issues, deflection figures I could actually check against December's ticket count. 11 11 10 10

Report an error

The Integrator

Knowledge is documented as a managed asset rather than a folder of articles: a knowledge builder turns support interactions into article drafts to close content gaps, topic identification mines ticket trends to recommend new articles, metric groups cover ticket-to-contact ratio, independently solved issues and case volume per topic, and the content lifecycle has approval workflows, scheduled publishing, depublishing and review intervals with localisation in over 40 languages. Only explicit content versioning went unstated on the pages I read. 10 10 11

Report an error

The Skeptic

Knowledge is documented as a managed asset, not just an FAQ: AI-supported topic identification reads ticket trends and recommends new help-centre articles, article performance is measured with ticket-to-contact ratios and independently solved issues against case volume by top-performing topics, and approval workflows, scheduled publishing, depublishing and review intervals exist with localisation in over 40 languages. The caveat this buyer cares about: Copilot is a separately priced add-on at 50 € per agent per month billed annually, so the agent-side AI assistance is metered rather than included. 10 11 2 10 11

Report an error

Customer data protection

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

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

The Agent Advocate

Processor role, privacy tools supporting access and erasure requests, a service data deletion policy, automatic credit-card redaction, audit logs on Enterprise plans, attachments behind login, and a published subprocessor list with names and locations are all documented — a real answer to a data-protection audit. Retention rules, data masking and access logs sit in an add-on rather than the base product, and I found no public information on the data processing agreement itself. 3 3 5

Report an error

The Data Protection Officer

The pages document configurable retention policies, data masking, PII redaction including automatic redaction of credit-card numbers in tickets, access logs, audit logs at Enterprise plans, private attachments behind login, role-based access control, and privacy tools covering access, correction, portability, deletion and objection requests, with Zendesk stated as processor and a subprocessor list published with names and locations. The retention, masking and access-log items sit behind the paid add-on for extended data protection and security, and I found no public information on a data processing agreement published or signable online or on whether the vendor's own support can read customer tickets, so it stops short of audit-grade. 3 5 3 5

Report an error

The Shop Operator

Zendesk is documented as processor with the subscriber as controller, and the evidence covers configurable data retention policies, data masking, PII redaction, access logs, Enterprise-plan audit logs, tooling for access and erasure requests, attachments gated behind login, and a published subprocessor list with names and locations. The retention, masking and redaction tooling comes as a paid add-on with custom roles only from the top plans, and I found no public information on a data processing agreement in the captured pages. 3 3 5 5

Report an error

The Integrator

The security pages document role-based access control with custom roles, audit logs on Enterprise plans, manual and automatic credit-card redaction, private attachments, privacy tools covering access, erasure, portability and objection requests, and a published subprocessor list with names and locations. The sharper controls — custom retention policies, data masking, PII redaction and access logs — sit behind the Advanced Data Protection and Security add-on, and I found no public information on how the vendor's own support staff access customer instances. 3 3 5

Report an error

The Skeptic

The deep protections exist but they are sold, not standard: configurable data retention policies, data masking, PII redaction and access logs come in the Advanced Data Privacy and Security add-on, and audit logs are limited to the Enterprise and Enterprise Plus plans. Automatic credit-card redaction, private attachments requiring login, documented support for access and erasure requests, and a published subprocessor list with names and locations are also evidenced; I found no public information on a signable data processing agreement on the captured pages. 3 5 3 5

Report an error

Integrations & API

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

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

The Agent Advocate

A marketplace with more than 1,700 plug-and-play apps, published REST API v2 and app-framework references with the old v1 docs marked deprecated, Sunshine database results linkable to ticket fields, and enterprise SSO via SAML and OIDC give a builder genuine material. I found no public information on SCIM provisioning, documented rate limits or an API sandbox, which is what keeps this off the top step. 2 7 9

Report an error

The Data Protection Officer

A marketplace with more than 1,700 apps, a documented REST API v2 with an app framework reference, a sandbox environment, SAML and OIDC single sign-on, and the Sunshine platform querying connected databases and writing results into ticket fields are all on the pages. We found no public information on SCIM provisioning, documented rate limits, or vendor-maintained bidirectional integrations, which is what the top level asks for. 2 5 7 9 13

Report an error

The Shop Operator

A marketplace with more than 1,700 apps, a documented REST API v2 whose v1 reference is marked deprecated, an app framework, and Sunshine databases that query connected data and link results straight to ticket fields — that is the order-in-front-of-the-agent piece I need. Single sign-on via SAML and OIDC and an Enterprise sandbox environment are stated; I found no public information on SCIM provisioning or documented rate limits. 9 7 13 5 2

Report an error

The Integrator

This is the criterion I read first: a marketplace with more than 1,700 plug-and-play integrations, a published REST API v2 reference alongside an app framework reference, deprecated v1 documentation showing versions are managed, a sandbox environment from the Enterprise plan, SSO via SAML and OIDC, and marketplace apps that query external databases and link results into ticket fields. Nowhere on the captured pages did I find a documented rate limit, webhook behaviour with retries, or SCIM provisioning — exactly the three things I need before wiring this into a CRM, a shop and an identity provider that all predate it. 2 7 5 9 13

Report an error

The Skeptic

This is a serious integration story: a marketplace with more than 1,700 apps, documented REST API v2 and app framework references with the deprecated v1 listed beside them, a sandbox environment from Suite Enterprise, SSO via SAML and OIDC, and the Sunshine platform querying connected databases and linking results to ticket fields. The two things I looked for and found no public information on are SCIM provisioning and documented rate limits. 2 7 9 13 5 9

Report an error

European sovereignty panel opinion

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

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

The Agent Advocate

The captured pages prove a selectable European Economic Area hosting region, name a German subsidiary in the legal notice, name AWS as the hosting provider, and point to a published subprocessor list with names and locations — more than a single European element. They state neither a default region for new accounts, nor the contracting entity, nor a data processing agreement, and the EWR option itself depends on product and plan, so I score this above the single-element level but below the established European tier. 3 4 3 5

Report an error

The Data Protection Officer

What the pages prove is an EWR data location selectable among the US, Australia and Japan with no default region stated, hosting on AWS, a German Zendesk GmbH registered in Berlin while the legal entity and copyright are Zendesk, Inc. of San Francisco, and a published subprocessor list with names and locations. The data processing agreement and any transfer assessment are unknown here, and I found no public information on which entity contracts with European customers or on the legal basis for non-EU processing, so I credit the EU option and the published chain but not the rest. 3 4 5 3 5

Report an error

The Shop Operator

European elements are proven: the European Economic Area is one of four selectable data locations on AWS, a Zendesk GmbH is registered at Amtsgericht Charlottenburg in Berlin, and a subprocessor list with names and locations is published. The chain around them stays open — the copyright names Zendesk, Inc. of San Francisco, the legal notice names the local subsidiary without stating who contracts, no default region is stated, and I found no public information on a data processing agreement. 3 4 5 6

Report an error

The Integrator

The chain is partly documented: hosting runs on AWS with a selectable European Economic Area region under a Regional Data Hosting Policy, a German subsidiary is registered in Berlin, a subprocessor list with names and locations is published, and Zendesk's processor role is stated. The vendor provenance places Zendesk, Inc. in San Francisco, the default region for new accounts is not stated, and I found no public information on the contracting entity or a data processing agreement, so a European archive looks possible here but not assured. 4 5 3 5

Report an error

The Skeptic

The EWR is one of four selectable regions among US, AU and JP, no default region is stated, and the page itself points to a hosting policy under which availability depends on product and plan; Zendesk GmbH is registered in Berlin, but the pages do not state which entity a buyer contracts with or the parent's seat, and the copyright reads Zendesk, Inc. A subprocessor list with names and locations is published, yet I found no public information on a data processing agreement or on the legal basis for non-EU processing. 4 5 3 5

Report an error

Pricing transparency

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

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

The Agent Advocate

The pricing page publishes per-agent monthly figures of 19 €, 55 € and 115 € billed annually, plus add-ons priced at 82 € and 50 € per agent per month with annual billing stated and per-plan feature lists published. The enterprise tier is contact-sales only, and I found no public information on VAT treatment, minimum term, telephony usage costs or light-agent pricing, so the true annual invoice is only partly computable from public pages. 2 2 6

Report an error

The Data Protection Officer

Per-agent prices are public with the billing period stated — 19 €, 55 € and 115 € per agent per month billed annually for the main tiers, plus add-ons at 82 € and 50 € — and feature lists per tier are given, while the top suite is contact-sales only. We found no public information on VAT treatment, minimum term, light-agent or contact limits, or metered telephony usage, so a support lead still cannot compute the full annual invoice from public pages alone. 2 2 6

Report an error

The Shop Operator

Per-agent prices are public with the annual billing period stated — 19 € for Support Team, 55 € for Suite Team and 115 € for Suite Professional per service agent per month — and the main add-ons carry numbers too, Contact Center at 82 € and Copilot at 50 € per service agent per month, with features listed per tier and a 14-day trial without credit card. Suite Enterprise is contact-sales only, and I found no public information on VAT treatment, minimum term, or light-agent and contact pricing. 2 2 6

Report an error

The Integrator

Per-agent prices are public for the main tiers with the billing period stated — Support Team at 19 €, Suite Team at 55 €, Suite Professional at 115 € per service agent per month, billed annually — and the add-ons carry numbers too: Contact Center at 82 €, Copilot at 50 €, Workforce Engagement at 50 € per agent per month, while only the top suite tier is a sales conversation and a startup programme offers six months free for up to 50 agents. I found no public information on minimum term, VAT treatment, or light-agent and contact limits, so I cannot compute the exact annual invoice from public pages alone. 2 2 6

Report an error

The Skeptic

The per-agent ladder is public with the billing period stated — 19 €, 55 € and 115 € per agent per month billed annually — feature lists per tier are given, and the add-ons carry numbers: Contact Center 82 €, Copilot 50 € and Workforce Engagement 50 € each per agent per month billed annually. I still cannot compute a complete invoice: Suite Enterprise is contact-sales, and the captured pages give no light-agent or contact limits, no VAT treatment, no minimum term, and no metered costs for telephony or WhatsApp usage. 2 1 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 →