Zammad
EU-Made Report an errorPanel 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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Zammad is an open-source helpdesk from Zammad GmbH, Berlin, offered hosted or self-hosted under GPL v3. Its strongest column is ticketing core, a flat 7 — response, update and solution SLAs scoped to freely combinable ticket groups, per-customer business-hour calendars and escalation notifications are documented. Pricing transparency follows at 6 to 7, with Starter v2 at 7€, Professional v2 at 16€ and Plus v2 at 25€ per agent / month, prices exclusive of statutory VAT and optional AI features metered at €0.03 per AI call. The weakest column is customer data protection at 3 to 4: the GDPR privacy policy names a data protection officer and states data is never sold, but it documents the vendor's website, and the judges found no public information on a data processing agreement, ticket-archive retention rules or an audit log of agent access. Sovereignty genuinely splits the bench, 4 to 6 — the German contracting entity, German ISO27001-certified data centres and full self-hosting argue for; the absence of public information on a data processing agreement and hosted-service subprocessors argues against.
Speaks for it
- Documented SLA machinery with response, update and solution deadlines scoped to freely combinable ticket groups, per-customer business-hour calendars and escalation notifications
- Channels from email to WhatsApp generate tickets in one structured view, with WhatsApp answered from the same interface and the chat widget shown only when an agent has capacity
- API-first REST API with three authentication methods, scope-restricted tokens, pagination, official PHP and Ruby clients and HMAC-signed webhooks with custom payloads
- Hosted tiers priced publicly per agent / month — Starter v2 at 7€ for up to 5 agents, Professional v2 at 16€ for up to 35, Plus v2 at 25€ with unlimited agents — plus a 30-day free trial
- Full GPL v3 codebase downloadable and self-hostable, allowing the ticket archive to sit on the buyer's own infrastructure
Held against it
- No public information on a data processing agreement, retention or deletion rules for the ticket archive, or an audit log of agent access
- No public information on merge and split, skills- or load-based ticket assignment, or reporting broken down by agent and queue
- No public information on documented rate limits, a sandbox, SSO or SCIM provisioning, or an app marketplace
- Multilingual knowledge base and GitHub/GitLab integration sit on the top plan, and article authoring is admin-only unless permissions are granted
- The published subprocessors (Matomo, Moosend, Vimeo LLC of New York) concern the vendor's website rather than the hosted helpdesk, and the data-centre provider is not named
Best for
- You need a documented SLA engine with business-hour calendars per customer and escalation at the deadline
- You want the option to self-host the full GPL v3 codebase and keep the ticket archive on your own infrastructure
- You build integrations yourself against a documented REST API with official PHP or Ruby clients
- Your team runs at most 5 agents and needs email, web form and SMS ticketing at 7€ per agent / month
Avoid if
- You need chat, Telegram, Facebook or WhatsApp channels on the entry tier — chat and Telegram first appear on Professional v2, Facebook and WhatsApp on Plus v2
- Your agents, not administrators, should author help-centre content — authoring is admin-only unless an administrator grants the rights
- You need reporting broken down by agent and queue — the documented options are standard reporting plus Elasticsearch/Grafana on the top plan
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 3.5 of 5 |
| Channels in one queue | 3.5 of 5 |
| Knowledge base & deflection | 3 of 5 |
| Customer data protection | 2 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3.5 of 5 |
Ticketing, queues & SLA
Show reasoningHide reasoning
How this is scored
The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.
0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.
3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.
5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.
8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.
10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.
The Support Lead
The SLA machinery is what I'd want on my wall: response, update and solution deadlines, business-hour calendars you can keep per customer, escalation notifications when the time is reached, and SLAs scoped to freely combined ticket groups — plus macros, triggers and overviews. I found no public information on warnings before a breach, merge and split, skills- or load-based assignment, or reporting broken down by agent and queue, so it stops short of the top of the scale. 3 6 7 2
The Agent Advocate
Response, solution and issue-based SLAs tied to business-hour calendars — with multiple calendars for customers on different hours, escalation at breach and notifications only inside working hours — is an engine that survives contact with a Monday morning. Macros, text modules, triggers, core workflows and one structured ticket view with full-text search are documented; we found no public information on merge and split, skills- or load-based assignment, or response and resolution reporting broken down by agent and queue. 3 6 7 10
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
The Shop Operator
The SLA engine is genuinely documented: response, update and solution SLAs scoped to freely combinable ticket groups, business-hour calendars per customer with multiple calendars, and escalation notifications when the deadline hits, plus triggers, macros, templates, bulk actions and full-text search. We found no public information on merge and split, skills- or load-based assignment, or first-response reporting broken down by agent and queue — standard reporting is as granular as the pages get. 3 7 6 2
The Integrator
Business-hour calendars drive the escalation maths, response and solution SLAs scope to freely combinable ticket groups, and a ticket that reaches its SLA time escalates and notifies the agents who opted in — a genuine engine, with macros, triggers, text modules and full-text search all documented. Standard reporting plus deeper Elasticsearch reporting via Grafana is asserted, but we found no public information on per-agent or per-queue breakdowns, merge and split, or skills- or load-based assignment. 2 3 6 7 10
The Skeptic
The SLA machinery is well documented: response, update and solution deadlines, business-hour calendars with multiple calendars per customer, escalation notifications, and SLAs scoped to freely combinable ticket groups, alongside macros, triggers, automation rules and full-text search. SLAs first appear in the Professional feature list rather than the entry tier, and we found no public information on merge and split, skills- or load-based assignment, or reporting broken down by agent and queue. 2 3 7
Channels in one queue
Show reasoningHide reasoning
How this is scored
Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.
0 — No customer channel of its own; the product only works on tickets entered by hand or by another system.
3 — Email turned into tickets, with a web form or one further channel.
5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.
10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.
The Support Lead
Email, 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 chat widget only appears when an agent has capacity, which I respect. Telephony is named as an integration without documented call logging, and I found no public information on a customer portal or on consent handling for the messengers. 2 3 8 9
The Agent Advocate
Email, web form, SMS, chat, Telegram, Facebook and WhatsApp are listed per plan, and the WhatsApp integration is documented to open a ticket per message and be answered from the same interface — that is the one-screen promise I judge channels by. We found no public information on a customer portal where requesters see their own tickets, on call logging behind the stated telephony integration, or on WhatsApp consent handling beyond a pointer to prerequisites and limitations. 2 3 8 9
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
The Shop Operator
WhatsApp does land in the queue: every message on the WhatsApp Business account automatically generates a ticket managed from the Zammad interface, and the chat widget only displays when an agent is online with remaining capacity. Email, web form, SMS, Telegram, Facebook and a listed telephony integration complete the picture, all feeding one structured ticket view with the customer's history. We found no public information on a customer portal where requesters see their own tickets, on call logging for telephony, or on WhatsApp consent handling. 9 8 2 3
The Integrator
Email, web form, SMS, chat and Telegram land as tickets in one structured view with the customer's history, and on the top plan Facebook and WhatsApp join them — WhatsApp with a setup guide that states prerequisites and limitations, and a chat widget that only displays when an agent has capacity. Telephony appears as a named integration with no call logging documented, we found no public information on a customer portal where requesters see their own tickets, and the channel list narrows on the lower tiers. 2 3 8 9
The Skeptic
WhatsApp explicitly generates tickets answered from the same interface, and email, web form, SMS, chat and Telegram are listed — though Facebook and WhatsApp arrive only on the top plan. Telephony appears as a named integration with no call-logging detail on the captured pages, and we found no public information on messenger consent handling or a portal where requesters see their own tickets. 2 3 8 9
Knowledge base & deflection
Show reasoningHide reasoning
How this is scored
Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.
0 — No knowledge base or self-service of any kind; the product is a ticket inbox only.
3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.
5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning that flag stale content, and reporting on which articles deflect.
10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.
The Support Lead
A multilingual help centre with search, category-based edit rights and scheduled publishing is documented, and the vendor states customers solve common issues without opening a ticket — deflection as an intention, not yet a number. I found no public information on article suggestions before a customer submits or while an agent answers, stale-content flags, or reporting on which articles deflect. 3 10 2
The Agent Advocate
A customer-facing help centre and a multilingual knowledge base with full-text search, categories, scheduled publishing and category-based editing rights are documented, and the vendor states customers solve common issues without opening a ticket — deflection as intent, though not yet as a measured number. We found no public information on article suggestions to the agent while answering or to the customer before submitting, or on reporting about which articles deflect. 2 3 6 10
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
The Shop Operator
There is a genuine help centre where customers solve issues without opening a ticket, with multilingual articles, categories, full-text search, scheduled publishing and category-based editing rights granted by admins. We found no public information on article suggestions to customers before they submit or to agents while answering, on versioning or review dates, or on reporting of which articles actually deflect — so I cannot predict whether the December ticket count would fall. 10 3 2
The Integrator
A searchable help centre with categories, rich-text articles with attachments and embedded images, scheduled publishing, multilingual content and wiki-style linking from tickets to answers is documented, with multilingual knowledge base gated to the higher plan. We found no public information on article suggestions to customers before they submit or to agents while answering, on review dates or versioning, or on reporting that says which articles deflect — and only admins write articles unless permission is explicitly granted, so the article workflow is thin for agents. 2 3 6 10
The Skeptic
A searchable knowledge base with categories, scheduled publishing, wiki-style linking and multilingual articles — though multilinguality is on the top plan while the mid plan is monolingual, and authoring is gated to admins by default. We found no public information on article suggestions before submission or while an agent answers, on draft and publish states, or on reporting of which articles deflect, even though the help centre is said to let customers solve issues without opening a ticket. 3 6 10
Customer data protection
Show reasoningHide reasoning
How this is scored
A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.
0 — The vendor's own terms state that ticket content is used for purposes beyond providing the service, or that a data processing agreement is not offered.
3 — A privacy policy and a data processing agreement (DPA) offered, with agent roles that limit what an agent can do.
5 — A DPA published or signable online, agent roles and group- or queue-level visibility, and deletion of tickets or of a requester's data documented in the help centre.
8 — Automatic retention or deletion rules per queue or data category, attachment handling stated, an audit log of agent access or changes, documented support for access and erasure requests, and redaction of ticket content.
10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.
The Support Lead
There is a published privacy policy naming a data protection officer and the full set of GDPR rights, agent permissions with role-based limits, and two-factor authentication with device management. I found no public information on a data processing agreement, on retention or deletion rules for tickets, or on an audit log of agent access — and the deletion statements on the captured pages concern the vendor's own website inquiries rather than the helpdesk product. 5 11 11 2 3
The Agent Advocate
The privacy policy names a data protection officer, lists the subject rights from information through deletion to portability, states that data will in no case be sold, and documents automatic deletion of contact-form data, while an ISO27001-certified data centre, 2FA, device management and individual roles sit on the trust and pricing pages. We found no public information on a data processing agreement, per-queue retention or deletion rules, an audit log of agent access, or redaction of ticket content. 2 5 6 11 11
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
The Shop Operator
A GDPR privacy policy listing all subject rights, a named data protection officer, a statement that data is never sold, two-factor authentication, device management and an ISO27001-certified data centre give a solid policy floor, with agent permissions and category-level rights limiting what agents can touch. We found no public information on a data processing agreement, on retention or deletion rules for the ticket archive itself, or on an audit log — the deletion statements captured concern the vendor's own contact forms, not customer tickets. 5 11 2 10
The Integrator
The published privacy policy is squarely GDPR-framed: a named data protection officer in Berlin, the full rights catalogue including deletion and portability, an explicit no-sale statement, and 2FA, device management and an ISO27001-certified German data centre on the plan pages. That documentation, though, covers the vendor's own website; we found no public information on a data processing agreement, on retention or deletion rules for the ticket archive itself, or on an audit log of agent access. 2 5 6 11 11
The Skeptic
A German GDPR privacy policy names a data protection officer, lists the full set of subject rights, and the product documents role-based permissions down to knowledge-base authoring. We found no public information on a data processing agreement, per-queue retention, audit logs, redaction or attachment handling; the documented automatic deletion covers inquiries sent to the vendor's own website rather than ticket data inside a customer's instance. 5 10 11
Integrations & API
Show reasoningHide reasoning
How this is scored
The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.
0 — A closed tool with no API and no integrations; context is copied in by hand.
3 — A handful of named integrations or a connector service such as Zapier, or an API with basic documentation.
5 — Named integrations for common CRM, shop or collaboration tools, a documented REST API, and webhooks or triggers that call other systems.
8 — An app marketplace with maintained bidirectional integrations, customer context from other systems shown inside the ticket, SSO and SCIM provisioning, documented rate limits and a sandbox.
10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.
The Support Lead
"API first" is stated to mean anything doable in the interface is doable through the REST API, with three authentication methods, restricted-scope tokens, official PHP and Ruby clients, and webhooks with HMAC signatures carrying full ticket context — plus named GitHub/GitLab integration. I found no public information on an app marketplace, SSO or SCIM provisioning, documented rate limits or a sandbox, which holds it below the top of the scale. 12 13 2 1
The Agent Advocate
The API is documented as API-first — anything the interface can do can be done via REST — with three authentication methods, restrictable API tokens, official PHP and Ruby clients, and webhooks since version 3.6 that POST ticket, article, user and organization payloads with optional HMAC signing; GitHub/GitLab and Elasticsearch/Grafana are named integrations. We found no public information on an app marketplace, SSO or SCIM provisioning, documented rate limits, or a sandbox. 1 2 12 13
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
The Shop Operator
API-first is claimed and documented: anything doable through the interface can be done via the REST/JSON API, with three authentication methods, official PHP and Ruby clients, scope-restricted tokens and pagination, while webhooks carry HMAC signatures with customisable JSON payloads since version 6.0 and named use cases for Teams, Slack, RocketChat and CRM. We found no public information on an app marketplace, SSO or SCIM provisioning, documented rate limits, or order context from a shop system shown inside the ticket — which is the second-login problem I care about most. 12 13 2
The Integrator
This is what I build against, and the foundation is unusually well documented: an API-first claim that anything the interface does the REST API does, three authentication methods including OAuth2, scope-restricted API tokens, pagination on all resources, official PHP and Ruby clients, and webhooks with HMAC signatures, custom payloads and a documented payload of tickets, articles, users, roles, organizations and groups; GitHub/GitLab integration and Slack, Teams and RocketChat use cases appear by name. We found no public information on documented rate limits, a sandbox, SSO or SCIM provisioning, or an app marketplace — the public GPL v3 source and self-hosting option soften that, but I want rate limits in writing before wiring a CRM to this. 1 2 12 13 14
The Skeptic
An API-first REST/JSON API with three authentication methods, restrictable tokens, official PHP and Ruby clients and pagination, plus webhooks with HMAC signatures, custom payloads and stated use cases including Teams, Slack and CRM. GitHub/GitLab integration and Grafana reporting sit on the top plan, and we found no public information on an app marketplace, SSO or SCIM provisioning, documented rate limits or a sandbox. 2 12 13
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.
The Support Lead
The contracting entity is Zammad GmbH in Berlin, the hosted service is stated to run in ISO 27001-certified German data centres, and the entire codebase is open source under GPL v3 with a self-hosting route if I need the archive on my own infrastructure. The chain stops there: I found no public information on a data processing agreement or a subprocessor list with locations for the hosted service, and no data-centre provider is named. 4 6 2 14
The Agent Advocate
Zammad GmbH is registered in Berlin, the hosted service is stated to run on servers in German, ISO27001-certified data centres, and the GPL-v3 codebase is fully self-hostable, so a buyer who wants the archive on their own infrastructure has a real option. We found no public information on a data processing agreement or on the subprocessor chain for the hosted archive; the privacy policy names only website tools such as Matomo, Moosend and Vimeo. 4 6 11 14
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
The Shop Operator
Zammad GmbH in Berlin with a German commercial register entry is the contracting party, the pricing pages state hosted plans run on servers in German data centres with ISO27001 certification, and GPL v3 code with a real self-hosting route means the archive can sit on my own infrastructure. We found no public information on a data processing agreement or the subprocessor chain for the hosted product. 4 2 6 14
The Integrator
The chain I care about is documented German: Zammad GmbH in Berlin with a commercial register number, hosted plans on servers in German ISO27001-certified data centres, and — rare in this market — a full-feature open-source build under GPL v3 that I can download and run on my own infrastructure, with the code public and no vendor lock-in claimed. We found no public information on a data processing agreement, the data-centre provider is not named, and the subprocessor disclosure covers the marketing website — Matomo, Moosend and Vimeo in New York — rather than the hosted helpdesk service. 2 4 6 11 14
The Skeptic
Zammad GmbH in Berlin is the contracting entity, hosted plans run on servers in German data centres described as ISO27001-certified, and the GPL v3 codebase can be downloaded and self-hosted entirely. We found no public information on a data processing agreement or on which subprocessors touch the hosted ticket archive; the published subprocessors (Matomo, Moosend, Vimeo) concern the vendor's website. 2 4 6 14
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier, per agent or flat.
5 — Per-agent prices public for the main tiers with the billing period stated and the main features per tier listed.
8 — Every tier and add-on priced publicly with per-agent maths, telephony or messenger costs and light-agent or contact limits given, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.
The Support Lead
Three tiers are priced per agent per month — Starter v2 at 7€, Professional v2 at 16€, Plus v2 at 25€ — with agent caps of 5, 35 and unlimited, plus storage, attachment limits, channels and support hours per tier, VAT stated as exclusive, and the optional AI features at €0.03 per AI call. What I cannot compute from the public pages: telephony or messenger costs, an annual invoice figure, or a minimum term. 2 6 1
The Agent Advocate
All three hosted tiers are public — Starter v2 at 7€, Professional v2 at 16€ and Plus v2 at 25€ per agent / month — with agent limits of 5, 35 and unlimited, per-tier channels, storage, attachments and support hours, prices stated as excluding statutory VAT, and the optional AI feature priced at €0.03 per AI call, so the invoice for a given agent count is computable from the pricing pages. We found no public information on minimum contract term or separate telephony costs. 2 6
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
The Shop Operator
All three hosted tiers are public per agent and month — Starter v2 at 7€, Professional v2 at 16€, Plus v2 at 25€ — with agent limits of 5, 35 and unlimited, channels, storage and support hours per tier, prices stated as plus statutory VAT, and the optional AI add-on priced at €0.03 per AI call, so I can compute the annual software invoice for my agent count. We found no public information on minimum contract terms, telephony or messenger costs, or pricing for the self-hosted route. 2 6
The Integrator
Three hosted tiers are priced per agent / month — Starter v2 at 7€ capped at 5 agents, Professional v2 at 16€ with a maximum of 35, Plus v2 at 25€ with unlimited agents — each with its channel list, storage, attachment size and feature set published, VAT stated as exclusive of statutory VAT, the optional AI features metered at €0.03 per AI call, plus a 30-day free trial and a plan finder. We found no public information on minimum terms or separate telephony and messenger channel costs, so the base invoice is computable from public pages while the metered edges are not. 1 2 6
The Skeptic
All three tiers are priced per agent per month with feature and channel matrices, agent caps, storage and attachment limits, VAT stated as excluded, and the AI summariser explicitly metered at €0.03 per AI call rather than included. We found no public information on telephony or messenger costs, a minimum term, or differences between monthly and annual billing. 2 6
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Incorporated in DE | 2/2 pts | 4 Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 1 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location, Hosting options. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 35 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage zammad.com Checked 16 Nov 2026 Details →
- 2 Pricing zammad.com Checked 16 Nov 2026 Details →
- 3 Product overview zammad.com Checked 16 Nov 2026 Details →
- 4 Imprint zammad.com Checked 16 Nov 2026 Details →
- 5 Privacy policy zammad.com Checked 16 Nov 2026 Details →
- 6 Security / trust page zammad.com Checked 16 Nov 2026 Details →
- 7 Ticketing, queues & SLA — found from sitemap zammad.com Checked 16 Nov 2026 Details →
- 8 Channels in one queue — found from sitemap zammad.com Checked 16 Nov 2026 Details →
- 9 Channels in one queue — found from sitemap zammad.com Checked 16 Nov 2026 Details →
- 10 Knowledge base & deflection — found from sitemap zammad.com Checked 16 Nov 2026 Details →
- 11 Customer data protection — found from sitemap zammad.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 12 Integrations & API — found from sitemap zammad.com Checked 16 Nov 2026 Details →
- 13 Integrations & API — found from sitemap zammad.com Checked 16 Nov 2026 Details →
- 14 Open-source licence page — found from the homepage zammad.com Checked 16 Nov 2026 Details →
- 15 Structured-data backfill: markup only, no text or screenshot zammad.com Checked 8 Nov 2026 Details →