Zammad

Martin Edenhofer launched Zammad in 2016 to rethink customer service tooling after fifteen years building the OTRS ticketing system. Where legacy helpdesks forced agents through rigid database forms and static ticket pages, Zammad was engineered around real-time browser multitasking and omnichannel routing. That architecture gives support departments a single-page workspace where email, chat, and phone queues update live without manual page reloads.

Why Zammad instead of Zendesk

Zendesk organizes support operations around paginated ticket views and independent browser windows, whereas Zammad keeps the entire agent workflow inside a tabbed single-page application. Support agents can switch between multiple open customer conversations, user profiles, and organization records simultaneously without losing in-progress drafts. Built-in WebSocket connections deliver instant collision warnings when a colleague opens or types in a ticket, stopping duplicate agent responses before they reach the customer. Omnichannel feeds consolidate inbound emails, website chat, and computer telephony integration into an uninterrupted chronological timeline.

The operational trade-off centers on ecosystem breadth versus local workflow ownership. Zendesk offers a commercial catalog of more than a thousand third-party marketplace add-ons, ready-made CRM plugins, and managed cloud maintenance. Zammad requires internal teams to deploy and manage a multi-container stack with Elasticsearch and background workers. In exchange, operations leads gain complete control over data retention, custom database object attributes, and granular role-based routing rules without facing tier-gated feature limits or recurring per-seat subscription invoices.

What it does well

• Real-time agent collision detection alerts staff the moment a teammate views or edits a ticket, preventing overlapping replies across shared mailboxes.
• Internal multitasking interface lets agents retain active ticket tabs, unsaved notes, and customer records across shifts without losing workspace context.
• Native computer telephony integration connects SIP and VoIP telephone systems, automatically matching incoming caller IDs to existing customer accounts.
• Granular organization management and email domain mapping allow agencies to segregate multi-client ticket queues within a unified administrative console.