Freshdesk vs Zammad

Freshdesk

Intelligent routing, multiple SLA policies and custom dashboards arrive on Pro, with skill-based routing and audit logs held back for Enterprise, and the archiving lifecycle is properly documented — closed tickets auto-archive after 120 inactive days and still count as closed in reporting. We found no public information on SLA timers with breach warnings, escalation chains, or first-response and resolution time reported by agent and queue, which is exactly the reporting I take to a quarterly review.

Zammad

The bones are evidenced — "States · Assignment · Escalations", SLAs, macros, automation rules, overviews and reporting — and escalations plus SLAs are what I need against a promised SLA. But nothing shows breach warnings, business-hours-aware SLA policies, per-agent resolution reporting, merge/split or even that search exists; and SLAs only enter at Professional v2, so Starter buyers track work they can't measure.

Freshdesk

Email agents, a customer portal, Facebook Messenger and WhatsApp bots are all evidenced, and phone exists as the Freshcaller product with call-recording consent stated. But the WhatsApp deployment runs through a Freshchat integration and bot-to-agent handover happens over APIs, and we found no public information showing these channels land in one queue with one shared history a customer can move between mid-issue.

Zammad

Email, web form, chat, Telegram, WhatsApp and Facebook are all placed as priced channels and the unified ticket view with customer profile suggests one history per customer. Missing: no evidence of call logging for the claimed telephony integration, no messenger consent handling, no requester-visible portal — and chat and WhatsApp are tier-gated, so "one queue" depends on which invoice you sign.

Freshdesk

Freddy answers track intent statistics with helpful/not-helpful feedback and training tags that flag unmapped and unhelpful questions — a genuine gap-finding loop rather than a link library. We found no public information on editorial workflow, versioning, review dates or deflection reported as a number, and the claimed "up to 80% resolution rates" is a figure I would want checked against my own queue.

Zammad

A help centre and knowledge base exist with the deflection promise spelled out ("without opening a ticket") and multilingual articles from Plus upward. No editorial workflow, draft/publish, article insert into replies, review dates or deflection reporting appears anywhere in the evidence — knowledge is a shelf, not a managed asset.

Freshdesk

The sub-processor list is published, Freshworks states it is generally the processor rather than controller of hosted data, and audit logs come with the Enterprise plan. We found no public information on a published signable data processing agreement, a stated retention period, or documented support for access and erasure requests; the only deletion path evidenced is the permanent, irreversible deletion of archived tickets.

Zammad

Configurable roles and permissions, transport encryption, 2FA, device management, an ISO27001 German data centre, and a self-hosted route that removes vendor access altogether are all evidenced. But there is no published DPA, no stated retention period for tenant ticket data, and no evidenced in-product erasure execution — the GDPR rights list and auto-delete text in the privacy policy govern Zammad's own website inquiries, not my instance.

Freshdesk

The API library supports GET, PUT, POST, DELETE and JS functions with test runs, custom authorisation headers and reusable configurations, connectors are sold as metered add-ons at €80/5000 tasks, and there is a marketplace plus a sandbox on Enterprise. We found no public information on named CRM or shop integrations, documented rate limits, or SCIM provisioning, and the only webhooks evidenced are messenger event subscriptions.

Zammad

"Open APIs and ready-to-use integrations" plus named GitHub/GitLab and Grafana/Elasticsearch connections are the entire evidence base. No CRM or shop system is named, and webhooks, SSO, rate limits, SCIM and any sandbox are silent — an API I can't confirm past the marketing claim is an API I can't plan a build on.

Freshdesk

The contracting parent is a Delaware company and processing is named in the United States, the UK and the EEA, with the EU-U.S. Data Privacy Framework offered as the safeguard. EU entities such as Freshworks GmbH and Freshworks Technologies B.V. exist and the sub-processor list is published, but the captured pages do not confirm where the hosted ticket archive itself is stored.

Zammad

The contracting entity is a German GmbH with a Charlottenburg commercial register number, hosting is German on an ISO27001-certified data centre, and self-hosting exists for keeping the archive on our own infrastructure. But the data-centre provider is unnamed, there is no subprocessor list for the product itself (Matomo and Moosend cover only their website), and the pipeline marks residency and subprocessor exposure as unconfirmed — so I can't give the transparency an anchor-8 buyer would audit.

Freshdesk

All three tiers are public per-agent with the billing period stated — €17, €52 and €84 /agent/month billed annually — alongside day passes and metered add-ons such as €45/100 AI Agent sessions and €13/1000 MCP actions, so most of my annual agent invoice is computable from the pricing page. VAT treatment and minimum term are not stated, however, and we found no public information on telephony pricing.

Zammad

I can compute the tiered invoice from public pages alone: per-agent prices, agent caps, channel placement per tier (WhatsApp in Plus, SLAs in Professional), VAT explicitly excluded, and even the AI meter at €0.03 per call. What keeps it off rubric level 8: telephony is claimed on the product page yet appears in no priced tier, and billing commitment and minimum term are unstated.