Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

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

by Zammad GmbH · zammad.com

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

Link to this page

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

Zammad at a glance

Vendor
Zammad GmbH
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Starting price
“Starter v2 7€ per agent / month” (vendor’s words) source, captured 16 Nov 2026
Panel verdict
The AI panel rates Zammad 3/5, the mean of 6 judges. Zammad is an open-source helpdesk from Zammad GmbH, Berlin, offered hosted or self-hosted under GPL v3. how scores are made
As of
Vendor pages captured 1 Oct 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Zammad alternatives, European ones first →

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

The Data Protection Officer

Weighted verdict

Sees a ticket archive for what it is: years of personal data customers typed themselves, including the things they should not have. Wants retention that executes, redaction, an audit of who read what, and an answer on whether vendor support can open a ticket.

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

Scored by The Data Protection Officer

Panel median The Data Protection Officer 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 Data Protection Officer
Ticketing, queues & SLA 3.5 of 5 3.5 of 5
Channels in one queue 3.5 of 5 3 of 5
Knowledge base & deflection 3 of 5 3 of 5
Customer data protection 2 of 5 2 of 5
Integrations & API 3 of 5 3 of 5
European sovereignty 2 of 5 3 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 Data Protection Officer

Tickets carry states, assignment and escalation, and the SLA machinery is real: response, update and solution deadlines scoped to freely combined ticket groups, multiple business-hour calendars, and escalation notifications when a deadline is reached. Macros, text modules, templates, triggers, bulk actions, ticket history and full-text search are all documented. We found no public information on merge and split, skills- or load-based ticket assignment, or reporting broken down by agent and queue. 3 6 7 10

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 Data Protection Officer

Email, web form, SMS, chat, Telegram, Facebook and WhatsApp all land as tickets — WhatsApp generates a ticket per incoming message and is answered from the same interface — and the vendor describes one structured ticket view holding all communication, the customer profile and history. Telephony appears as a named integration, but we found no public information on call logging, and we found no public information on a requester-facing portal where a customer can see their own tickets. 2 3 8 9

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 Data Protection Officer

A help centre is positioned explicitly so customers can solve issues without opening a ticket, and the knowledge base is documented as multilingual and searchable, with categories, category-based editing rights, scheduled publishing and wiki-style links from tickets to answers. We found no public information on article suggestions to agents in replies or to customers before submitting, on versioning or review dates, or on reporting that measures deflection. 3 6 10

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 Data Protection Officer

The privacy policy names a data protection officer, enumerates the full set of GDPR rights, commits that data is never sold, and documents automatic deletion of inquiry and contact-form data plus statutory retention for payment data, with German ISO 27001-certified data centres, two-factor authentication, device management and role-based permissions behind it. But what is documented is the website's data lifecycle, not the ticket archive's: we found no public information on a data processing agreement for the service, retention rules per queue, redaction of ticket content, an audit log of agent access, or whether vendor support can open a hosted customer's tickets. 2 3 5 10 11 11

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 Data Protection Officer

The REST/JSON API is documented as API-first — anything the interface can do the API can do — with three authentication methods, scope-restricted tokens, pagination, official PHP and Ruby clients, and webhooks since version 3.6 carrying custom JSON payloads verified by HMAC signature. Named integrations cover GitHub/GitLab and reporting via Elasticsearch and Grafana; we found no public information on an app marketplace, SSO or SCIM provisioning, rate limits, or a sandbox. 1 2 12 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 Data Protection Officer

Zammad GmbH is the contracting entity with a Berlin address and commercial register entry, the hosted plans run on the vendor's own servers in German ISO 27001-certified data centres, and the full GPL v3 codebase is downloadable and self-hostable — an option that lets a buyer keep the archive entirely on their own infrastructure. The subprocessor names the privacy policy publishes (Matomo, Moosend, Vimeo LLC of New York) concern the vendor's website rather than the service; we found no public information on a published data processing agreement, the data-centre provider's name, or vendor support access to hosted instances. 2 4 6 11 14

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 Data Protection Officer

All three tiers are priced publicly per agent per month — Starter v2 at 7€, Professional v2 at 16€, Plus v2 at 25€ — with agent caps (5, 35, unlimited), channel lists, attachment and disk limits, support hours, prices explicitly exclusive of statutory VAT, and optional AI features metered at €0.03 per AI call. A 30-day free trial and a plan finder are offered; we found no public information on telephony or messenger costs or on minimum contract terms. 1 2 6

Report an error

European sovereignty — proven facts

2 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?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Open source Open source (copyleft) 1/1 pts 14 Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Zammad

Is Zammad European?

Yes. whats-best.ai classifies Zammad as EU-Made. Its vendor, Zammad GmbH, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does Zammad store data?

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

Does Zammad have a free plan?

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

What are the best alternatives to Zammad?

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 Userlike (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: Zammad 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 homepage zammad.com Checked 16 Nov 2026 Details →
  2. 2 Pricing zammad.com Checked 16 Nov 2026 Details →
  3. 3 Product overview zammad.com Checked 16 Nov 2026 Details →
  4. 4 Imprint zammad.com Checked 16 Nov 2026 Details →
  5. 5 Privacy policy zammad.com Checked 16 Nov 2026 Details →
  6. 6 Security / trust page zammad.com Checked 16 Nov 2026 Details →
  7. 7 Ticketing, queues & SLA — found from sitemap zammad.com Checked 16 Nov 2026 Details →
  8. 8 Channels in one queue — found from sitemap zammad.com Checked 16 Nov 2026 Details →
  9. 9 Channels in one queue — found from sitemap zammad.com Checked 16 Nov 2026 Details →
  10. 10 Knowledge base & deflection — found from sitemap zammad.com Checked 16 Nov 2026 Details →
  11. 11 Customer data protection — found from sitemap zammad.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  12. 12 Integrations & API — found from sitemap zammad.com Checked 16 Nov 2026 Details →
  13. 13 Integrations & API — found from sitemap zammad.com Checked 16 Nov 2026 Details →
  14. 14 Open-source licence page — found from the homepage zammad.com Checked 16 Nov 2026 Details →
  15. 15 Structured-data backfill: markup only, no text or screenshot zammad.com Checked 8 Nov 2026 Details →