Freshdesk vs Zammad

Freshdesk

The plans name intelligent routing, multiple SLA policies and skill-based routing, and the support docs show a genuine lifecycle — closed tickets archive automatically after 120 inactive days, automation rules stop on archived tickets, and unresolved-ticket reporting is documented. But we found no public information on SLA breach warnings, priority handling, macros, or merge and split, and nothing showing whether search reaches ticket bodies, which is what finding one parcel query among ten thousand depends on.

Zammad

States, assignment, escalations, SLAs, macros, automation rules and reporting are all named, which is a genuine engine above the routing-and-status floor. But the evidence is silent on search entirely — I need to find one parcel ticket in ten thousand — and business-hours SLA policies, escalation chains, merge/split and per-agent response reporting are nowhere evidenced.

Freshdesk

Email and the customer portal clearly land in one ticketing product with a shared inbox, and the portal lets a requester see their own archived tickets. WhatsApp only reaches an agent through a chain — a Freddy Self-service bot deployed on a Freshchat widget, handed over to Freshdesk via APIs — and Facebook Messenger runs through the same bot platform, so we found no public information showing these channels land in one queue with one shared history. Telephony appears only as a sibling product in the privacy notice, with no evidence of calls logging into the Freshdesk queue.

Zammad

Chat, Telegram, Facebook and WhatsApp land as channels alongside email and web form, with a unified ticket view claimed — WhatsApp and the shop form in one queue is evidenced, not marketing. Docked below 8 because telephony is only a bare 'integration' with no call logging, messenger consent handling is unstated, and no requester-facing portal with own tickets appears anywhere.

Freshdesk

The deflection machinery is documented and it is what I judge on: the bot answers customers before any ticket exists, tracks how often each intent was sent and whether it helped, flags unmapped and unhelpful questions for training, and creates a ticket only on handover, with the product pages claiming resolution rates up to 80%. We found no public information on the knowledge base as a managed asset — editorial workflow, versioning, review dates, or reporting tying specific articles to deflected volume; it appears only as a named plan feature.

Zammad

A help centre explicitly positioned at 'without opening a ticket' plus a multilingual KB in the Plus tier shows deflection intent, above a bare article list. But no editorial workflow, no article suggestions to agent or customer, no review dates, and no deflection reporting — I couldn't tell you whether December's ticket count fell.

Freshdesk

The engine can actually execute deletion — deleting an archived ticket is documented as permanent and irreversible — and the plans name roles and permissions plus audit logs. The privacy notice publishes a subprocessor list with confidentiality obligations, but we found no public information on a signable DPA, on a stated retention period for ticket data (the 120-day archive rule is workflow, not retention), or on documented support for access and erasure requests.

Zammad

Individual roles and permissions, 2FA and an ISO27001 data centre give real access control, but no published DPA, no ticket retention period, no audit log and no product-level deletion path are evidenced — the GDPR-rights facts describe Zammad's own website inquiries, not the customer archive. Deletion is left entirely to the customer to arrange.

Freshdesk

There is a real integration surface: pre-built connectors for data sync priced per five thousand tasks, MCP actions priced per thousand, a marketplace of first- and third-party apps, and a documented API library inside the bot builder covering GET, PUT, POST and DELETE, authorisation headers, test runs and file payloads. But for a shop like mine the order context is the point, and we found no public information naming any CRM or shop integration, showing order data inside the ticket, or covering product single sign-on, webhooks or documented rate limits.

Zammad

'Open APIs and ready-to-use integrations' plus GitHub/GitLab and Grafana/Elasticsearch is a handful of named hooks, but nothing a shop runs on. No CRM, shop or order-management connector, no webhooks, no SSO, and nothing evidenced that puts the customer's order in front of the agent without a second login — my core requirement.

Freshdesk

This is an American vendor — Freshworks Inc. of Delaware — processing personal data in the United States, the United Kingdom and the EEA and relying on the EU-U.S. Data Privacy Framework, though EU contracting entities in Germany, the Netherlands and France exist depending on the customer. A subprocessor list is published and the bot platform exposes a Europe data-centre endpoint, but data residency for the ticket archive itself is not confirmed on the vendor's own captured pages, and for a European buyer that unknown is the whole question.

Zammad

German GmbH with a commercial register number, made and hosted in Germany, ISO27001-certified data centre, and open source with a self-host option — I can keep the archive on my own infrastructure. It stops short of the higher anchor because the data-centre provider is unnamed and no subprocessor list for the hosted product is published (the named Matomo/Moosend are the vendor's website tools).

Freshdesk

The per-agent maths is public and unusually granular: "€17 /agent/month, billed annually" at Growth, €52 at Pro, €84 at Enterprise, with day passes at €2, €7 and €12 per pass and metered add-ons priced by the unit — €45/100 sessions, €80/5000 tasks, €13/1000 actions. What I cannot compute from these pages is my real invoice: the WhatsApp route runs through Freshchat and calls through Freshcaller, and we found no public prices for either, nor VAT treatment or minimum terms.

Zammad

Per-agent prices for all three tiers with agent caps, storage limits, VAT treatment and even usage-metered AI at €0.03 per call are public, and WhatsApp clearly starts at Plus — I can nearly compute my invoice. Docked for no stated minimum term and for telephony, which is advertised as a channel but appears in no plan's channel list and carries no price.