Zammad

Zammad is an open-source helpdesk system that collects support requests from email, web chat, social media, and messaging apps into a single shared ticket queue. Agents see every communication with a customer in one view regardless of which channel it came through. New tickets from email land in the same inbox as a message from Telegram or a web chat conversation, with full history attached.

The platform covers the features a small support operation needs. SLA policies set response and resolution time targets with escalation rules that notify team leads when a ticket is approaching breach. The knowledge base lets you publish articles for both customers and internal agents — public articles reduce ticket volume by giving customers self-service options; internal articles standardise how agents handle common questions.

Multi-channel handling is where Zammad earns its place over simpler email-only tools. If your support comes through a mix of email, a contact form, live chat, and social DMs, managing those separately is operationally messy. Zammad centralises them. Customers do not need to know which channel to use, and agents do not need to check multiple inboxes.

The deployment is more involved than a single-container install. Zammad requires Elasticsearch for its search functionality, plus PostgreSQL and Redis. The Elasticsearch dependency in particular is non-negotiable — Zammad uses it for ticket and knowledge base search extensively, and the system is notably worse without it configured properly from the start.

For teams coming from Zendesk or Freshdesk, the agent UI is functional but not as refined. There is more configuration required upfront, and new agents take longer to get up to speed. For teams where budget or data ownership is the priority, that trade-off is usually acceptable.

Zammad: Pros & Cons