Freshdesk vs Zammad

Freshdesk

Routing and SLA are real and visibly tiered — intelligent routing and multiple SLA policies on Pro, skill-based routing and audit logs on Enterprise — and the archive runs itself: closed, inactive tickets become read-only after 120 days, count as closed in reports, and stay out of global search unless an admin opts them in. We found no public information on priorities, escalation chains, macros, merge and split, business-hours SLA policies, or what the audit log actually records.

Zammad

States, assignment, escalations, macros, templates, automation rules, SLAs and reporting are all evidenced, which clears the mid anchor. But nothing on business-hours-aware SLA policies, escalation chains, merge/split, or full-text search across ticket bodies, so it stays below the 8.

Freshdesk

Email threads, a customer portal where requesters can see their own tickets, and WhatsApp and Facebook Messenger deployment are all evidenced, with Messenger conversations handed over to a Freshdesk agent and Freshcaller call recording stated as subject to both parties' consent. The messengers arrive through a separate bot product connected over APIs, and we found no public information showing all channels landing in one queue with one shared history when a customer switches.

Zammad

Email, web form, chat, SMS, Telegram, WhatsApp and Facebook all land in one structured ticket view with shared history, plus telephony integration. Deducted because messenger consent handling is not stated, there is no evidenced customer portal where a requester sees their own tickets, and call logging is a bare phrase.

Freshdesk

Self-service is managed where it is measured: intents with variants, fallbacks, yes/no feedback after each answer, helpfulness statistics, and a training view that tags unmapped and thin questions so coverage gaps get found. The knowledge base itself appears only as a plan feature line, and we found no public information on editorial workflow, versioning, review dates, article suggestions to agents while they answer, or deflection reported as a number against ticket volume.

Zammad

A help centre and a knowledge base exist, multilingual on the Plus tier, with the stated aim of customers solving issues without a ticket. No editorial workflow, no versioning, no suggestions to agent or customer, and no deflection reporting are evidenced, so this sits between the basic article list and the working public help centre.

Freshdesk

The one lifecycle that demonstrably executes is archiving — closed, inactive tickets are archived after 120 days and deleting an archived ticket is permanent and irreversible — alongside roles and permissions on the base plan, audit logs on Enterprise, a published subprocessor list, and the customer named as controller of hosted data. We found no public information on a signable data processing agreement, queue-level visibility, redaction, attachment handling, what happens to the data after archiving, or whether the vendor's own support can open a customer's ticket.

Zammad

GDPR rights including deletion are listed and configurable roles/permissions and 2FA exist — but the deletion clause is the vendor's own website-inquiry auto-delete, not a path for a customer's ticket archive. No published DPA, no stated retention period for ticket data, no audit log of who opened which ticket, no redaction, no attachment-handling policy, and total silence on whether Zammad support can open a hosted instance's tickets.

Freshdesk

The bot platform's API library is documented in working detail — methods, authorisation headers, test runs, a ten-second timeout and multipart file payloads — and pre-built connectors, MCP actions and a marketplace of first- and third-party applications are all named, with a sandbox on the top plan. We found no public information on integrations named for CRM or shop systems, webhooks for core ticket events, single sign-on for agents, SCIM provisioning or documented rate limits.

Zammad

Open APIs and ready-to-use integrations are claimed, with named GitHub/GitLab and Grafana/Elasticsearch integrations. But no CRM, shop or identity integration is named, and there is no evidence of webhooks, SSO, rate limits, bidirectional sync or a sandbox — a read-mostly API with a few connectors.

Freshdesk

The contracting parent is Freshworks Inc. of Delaware and the notice relies on the EU-US Data Privacy Framework while processing personal data in the United States, the UK, the EEA and wherever its third parties are based; the vendor's own captured pages do not confirm where hosted customer data resides, and hashed identifiers are shared with social platforms for advertising. A published subprocessor list, EU group entities and a Europe data centre for the bot webhooks — alongside US, India and Australia — keep this a step above nothing.

Zammad

German contracting entity (Zammad GmbH, Berlin, commercial register Charlottenburg), German ISO27001 data centre, and crucially a self-hosted option that puts the archive on the buyer's own infrastructure. The data-centre provider is unnamed and no subprocessor list exists for the product chain — the only named subprocessors, Matomo and Moosend, serve the vendor's website.

Freshdesk

All three plans carry public per-agent prices with the billing period stated — Growth at €17, Pro at €52 and Enterprise at €84 per agent per month billed annually — plus per-tier day passes and metered prices for AI sessions, connector tasks and MCP actions, and the feature lists show which tier SLA policies and audit logs belong to. Computing the real invoice still trips on unstated VAT treatment and minimum term, and we found no public price for the chat product the WhatsApp deployment depends on.

Zammad

All three tiers carry public per-agent prices with agent limits, channels, storage, support hours, VAT treatment and a metered AI fee of €0.03 per call — nearly computable. Billing period and minimum term are unstated, and telephony appears on the product page but in no tier's channel list, so its price position is a guess.