Freshdesk vs Zammad

Freshdesk

The tier pages are the clearest evidence: multiple SLA policies and intelligent routing begin at Pro, while skill-based routing, the sandbox and audit logs are Enterprise-only, and we found no public information on what an SLA policy actually enforces — timers, breach warnings, business-hours coverage. The ticket lifecycle itself is well documented (closed status, automatic archiving after 120 inactive days, permanent irreversible deletion, automation rules), but we found no public information on escalation chains, macros and triggers, or first-response and resolution reporting by agent and queue.

Zammad

States, assignment, escalations, SLAs, macros, templates and automation rules are all named, and I can read exactly which tier SLAs start at — Professional v2. But nothing evidences business-hours-aware SLA policies, merge/split, first-response reporting by agent and queue, or full-text search across ticket bodies — the bullets are marketing nouns, so I stop just past the anchor-5 line.

Freshdesk

Beyond email, the customer portal and per-contact ticket history are real — customers log in and see their own tickets, archived ones included — but every further channel arrives through glue: Facebook Messenger runs through the bot platform's own webhook data centres, WhatsApp only by wiring a separate Freshchat account into that bot product, and phone is a separate product whose consent-based call recording the privacy notice describes. We found no public information showing chat, messengers and calls landing in one queue with one shared history beside email.

Zammad

Seven channels are named per tier — Email, Web Form, SMS, Chat, Telegram, Facebook, WhatsApp — plus 'Telephony integration', and the 'unified structured ticket view with history' claims one history. My follow-ups go unanswered: no evidence of call logging behind the telephony bullet, no consent handling stated for WhatsApp, and no requester portal where a customer sees their own tickets — the help centre is a knowledge base, not a ticket portal.

Freshdesk

Deflection is documented and measured: intents and their variants map to answers or flows, yes/no helpfulness feedback is collected after every answer, each intent tracks how often it was sent and how helpful, unmapped or low-coverage questions are tagged for training, and the bot hands over to a Freshdesk agent when it cannot answer. The knowledge base itself appears as a tier feature with "multilingual helpdesk" at Pro, but we found no public information on article workflow, versioning, review dates, or agents inserting articles into replies; the "Up to 80% resolution rates" figure sits on the product page with no indication of how it is measured.

Zammad

A help centre and knowledge base exist, multilingual from the Plus tier. Deflection is asserted — 'without opening a ticket' — but never instrumented: no draft/publish workflow, no article-insert into a reply, no suggestions before submission, and no reporting on which articles deflect. That's a basic article list with a language setting, a step above rubric level 3 and clearly short of rubric level 5.

Freshdesk

Two things execute rather than promise: deleting an archived ticket is documented as permanent and irreversible, and a sub-processor list is published with access limited to "only as reasonably necessary", with roles and permissions named from the Growth tier. Against that, audit logs sit behind the Enterprise tier, we found no public information on a signable data processing agreement, per-queue retention rules, or an audit trail of who opened which ticket, and the privacy notice itself describes sharing hashed visitor identifiers with Facebook and LinkedIn for custom-audience advertising.

Zammad

The GDPR rights list and auto-deletion in cover Zammad's own website inquiries, not the customer's ticket archive — that policy was last changed in 2020. Product-side I have 'Permissions' and individual roles at Professional, 2FA and an ISO27001 data centre, but no published DPA, no stated retention period for tickets, no audit log of who opened which ticket, and nothing on attachment handling or redaction.

Freshdesk

The documented API here is the bot builder calling outward — GET, PUT, POST and DELETE with headers and authorisation, test runs, a 10-second timeout, and multipart form data for file uploads — alongside a marketplace platform and metered "pre-built connectors" at €80/5000 tasks. We found no public information on a documented REST API over the helpdesk itself with keys, named CRM or shop integrations, webhooks for core ticket events, or documented rate limits, and the sign-in services described are Google, Facebook Connect and LinkedIn for the vendor's websites rather than enterprise single sign-on for agents.

Zammad

'Open APIs and ready-to-use integrations' plus exactly two named non-channel integrations — GitHub/GitLab and Grafana/Elasticsearch. That's a handful of natives and an API asserted in marketing language: no webhooks, no documented rate limits, no SSO, and no CRM or shop system named anywhere on the evidence.

Freshdesk

The contracting parent is a Delaware company relying on the EU-US, UK and Swiss Data Privacy Frameworks, and processing is stated for the United States, the United Kingdom and the EEA "and in other countries where third parties that we may use are based"; where the hosted archive resides is not confirmed on the captured pages, which only point to a Data Hosting page. A sub-processor list is published, Freshworks entities exist in Germany, the Netherlands and France, and the bot webhooks offer separate US, Europe, India and Australia data centres — but we found no public information showing EU hosting as the standard for a customer's ticket archive.

Zammad

The contracting entity is nailed down — Zammad GmbH, Marienstraße 18 Berlin, HRB 163946 B — with 'Made & hosted in Germany' and an ISO27001-certified German data centre, plus a genuine self-hosted option. But the data-centre provider is unnamed, the only published subprocessors are the website's Matomo and Moosend Ltd rather than the product chain's, and the metered AI feature never states who processes it or where — so rubric level 8's named-provider and full-subprocessor-list bar isn't met.

Freshdesk

All three tiers carry public euro prices with the billing period stated — Growth €17, Pro €52 and Enterprise €84 per agent per month, billed annually — and the metered pieces are unusually explicit: day passes at €2, €7 and €12 per pass, additional AI Agent sessions at €45/100 sessions beyond the 500 included in every tier, plus priced connector tasks and MCP actions. A support lead still cannot compute the real annual invoice, because telephony and live chat sit in separate Freshworks products with no prices on these pages, and VAT treatment and minimum term are unstated.

Zammad

Three tiers priced per agent with agent limits, VAT treatment, storage caps and even the AI meter at €0.03 per call are all public — unusually honest on the AI. But there's no billing period or annual option, no minimum term, no light-agent pricing, and the usage-metered channels (SMS from Starter upward, telephony) carry no price at all, so I can't compute the invoice for a chat-plus-SMS team.