OTOBO

OTOBO is the open source successor to OTRS Community Edition, created after OTRS discontinued its free tier and moved to a commercial-only model. Maintained by Rother OSS, OTOBO picks up where OTRS CE left off and provides a migration path for the many organisations that had built their service desk operations on OTRS before the licence change.

The platform handles email-based ticketing at its core. Inbound emails to configured mailboxes are automatically converted into tickets, assigned to queues, and routed to agents based on rules you define. Agents reply from the interface and their responses go out as formatted email. The entire conversation thread is captured in the ticket history, with timestamps, agent names, and state changes creating an audit trail.

ITIL alignment is built into the architecture. OTOBO supports the standard ITIL service management processes — incident management, problem management, change management, and service request fulfillment — as distinct ticket types with their own workflows, approvals, and reporting. For IT teams that need to demonstrate ITIL compliance or are working toward certifications, this structure matters.

SLA definitions, escalation rules, and automatic notifications handle the operational side of a service desk. You define response and resolution time targets per priority, and OTOBO tracks breach status, sends warnings before deadlines, and escalates to supervisors when SLAs are at risk.

The practical challenge is setup complexity. OTOBO is a Perl application with a lot of configuration surface. Docker deployment manages the Perl dependencies cleanly, but getting queues, routing rules, SLA configurations, and notification templates correctly configured for your specific workflow takes time. For organisations with straightforward requirements, the simpler setup of Zammad or Freescout is worth evaluating. OTOBO earns its complexity when ITIL processes and OTRS migration are the driving requirements.