Freshdesk vs Zammad

Freshdesk

Intelligent routing and multiple SLA policies arrive at Pro, skill-based routing and audit logs at Enterprise, and the ticket-archiving lifecycle is documented down to its effect on reports, search and customer replies. I found no public information on escalation chains, macros, merge and split, or first-response and resolution-time reporting by agent, so I stop short of the higher band.

Zammad

States, assignment, escalations, macros, automation rules and SLAs are all named, which is the substance of rubric level 5 — but nothing evidences search across ticket bodies, priorities, business-hours SLA policies, merge/split, or what the 'Reporting' actually measures. In a ten-thousand-ticket queue I need to know an agent can find the ticket, and the evidence is silent on that.

Freshdesk

Email AI agents, a customer portal where requesters see their own tickets, and WhatsApp and Facebook Messenger deployment through the Freshchat and Freddy products are all evidenced, with consent-based call recording stated for the separate Freshcaller product. What the captured pages do not show is these channels meeting in one queue with one history: messenger conversations reach agents as a bot handover that creates a ticket, and no telephony call logging into the helpdesk is evidenced.

Zammad

Email, web form, chat, Telegram, Facebook, WhatsApp and telephony are all named, and 'all communication... in one structured ticket view' supports one history — but messenger consent handling is never stated, and there is no evidence of a portal where a requester sees their own tickets, only a help centre. That keeps it under the anchor-8 bar.

Freshdesk

A knowledge base and customer portal ship from the Growth plan, and the Freddy bot answers customer questions with intent statistics showing how often each answer was sent and how helpful it was, plus a training view flagging unmapped and unhelpful questions — deflection treated as measurable. I found no public information on editorial workflow, versioning, review dates, or article suggestions shown to agents while they answer.

Zammad

A public help centre with an explicit deflection claim and a multilingual knowledge base (Plus tier) clears rubric level 5. Nothing evidences editorial workflow, versioning, inserting articles into replies, suggestions to agents or customers, review dates, or deflection reporting — so I cannot credit the 8-anchor features beyond multilinguality.

Freshdesk

Roles and permissions ship from Growth, audit logs sit at Enterprise, a sub-processor list is published, and deleting an archived ticket is documented as permanent and irreversible. We found no public information on a signable data processing agreement, a stated retention period, requester-level erasure or access requests, or attachment handling, and the privacy notice describes sharing hashed email addresses and phone numbers with Facebook and LinkedIn for custom-audience advertising.

Zammad

The privacy policy lists full GDPR rights including deletion and granular roles are a feature, but that policy governs Zammad's own website — the evidence evidences no tenant DPA, no stated retention period for ticket archives, no audit log of ticket access, and no attachment handling. Roles plus documented rights sit just above the anchor-3 floor; nothing here executes.

Freshdesk

An application marketplace for first- and third-party apps, metered pre-built connectors, MCP actions priced per thousand, and a documented bot-side API library with custom headers, test runs, file attachments and debug logs are all evidenced, and a sandbox ships at Enterprise. But what is documented is the product calling out — I found no public information on a documented REST API for building against the helpdesk itself, rate limits, webhooks for ticket events, or SCIM provisioning, and no CRM, shop or identity system is named.

Zammad

'Open APIs and ready-to-use integrations' is a homepage bullet with no docs, and the named integrations are GitHub/GitLab and Grafana/Elasticsearch — developer tools, not one CRM, shop or identity system. My whole checklist — documented rate limits, webhooks that retry, SCIM, a sandbox, SSO — appears nowhere, which is the read-mostly rubric level 3 plus a sync claim I can't verify.

Freshdesk

The parent is Freshworks Inc. of Delaware, processing is described across the United States, the United Kingdom, the EEA and countries where third parties are based, and transfers rest on the Data Privacy Framework; German, Dutch and French entities are also named as controllers. Data residency is not confirmed on the vendor's captured pages, though a sub-processor list is published and a Data Hosting page is referenced.

Zammad

Zammad GmbH in Berlin is the contracting entity, hosting is 'Made & hosted in Germany' in an ISO27001-certified German data centre, and a self-hosted option exists — rubric level 5 met, with self-hosting pulling above it. But the data-centre provider is unnamed, the pipeline itself marks residency and subprocessor exposure unknown, and the only listed subprocessors (Matomo, Moosend) are website tools, not the product chain.

Freshdesk

All three tiers are priced per agent with the billing period stated — €17, €52 and €84 per agent per month, billed annually — alongside day passes at €2, €7 and €12 and metered prices for extra AI sessions, connector tasks and MCP actions, with plan lists showing where SLA policies and the sandbox begin. We found no public information on VAT treatment, minimum term, or the cost of the separate chat and telephony products, so the full annual invoice is still not computable from public pages.

Zammad

Three tiers with per-agent prices, explicit channel lists, agent caps, storage limits, VAT treatment and even a metered AI price of €0.03/call are public — most of an annual invoice is computable. But telephony is a channel on the product page that appears in no tier's channel list and carries no number, and no minimum term is stated.