OTRS vs Znuny

OTRS

Three homepage captures and the legal pages don't evidence a single ticketing capability — no routing, no SLA timers, no escalation chains, no search, not even a status model. All I have is the 'Customer Service & Helpdesk' category label and a 'service management suite' descriptor, which gets it off the absolute floor but tells me nothing I could put in front of my team on a Monday.

Znuny

Queues are permission-based grouping objects with ticket ownership, priority changes, and close and pending screens, and inbound mail dispatches automatically to a queue or by recipient line, with moving and splitting between teams. But the captured documentation shows nothing on SLA timers, breach warnings, escalation chains, macros, or search — I found no public information on any of those, and for a team on a contractual SLA that is the whole ballgame.

OTRS

Nothing in the evidence evidences any channel at all — not email handling, not a portal, not a single messenger — let alone channels landing in one queue with one history. rubric level 0 says email only; the evidence gives me less than that to work with, so this is the floor.

Znuny

What is documented to land in one queue is email — any number of mailboxes across IMAP, POP3 and Microsoft Graph, with OAuth2 — plus a phone screen where an agent records a call into the ticket system. We found no public information on live chat, a customer portal, messengers, social channels, or telephony with call logging, so the multi-channel pitch rests on manual phone entry.

OTRS

The only knowledge-base-adjacent fact anywhere is that OTRS's own website has FAQs — that's their marketing site, not a product help centre, article workflow, or deflection reporting. There is no evidence the product reduces ticket volume at all.

Znuny

We found no public information on a knowledge base, public help centre, article workflow, article suggestions, or deflection reporting anywhere in the captured pages. The homepage's listing of forum and professional services points to people-based support, and nothing evidences self-service content reducing ticket volume.

OTRS

Credit where due: a published privacy statement, GDPR page and Trust Center exist, a named external DPO is on record, and retention periods are actually stated (10 years general, 6 months application data) — but every one of those governs OTRS's own website and CRM, not the helpdesk product. Nothing evidences agent roles, queue-level visibility, per-queue retention rules, a ticket audit log, redaction, or an executable deletion of a requester's data inside the product, which caps this at the DPA-on-request-and-coarse-practices level.

Znuny

Access control is the evidenced strength: seven basic queue permissions plus configurable extended ones, so who sees and works which queue is genuinely granular. We found no public information on a published or requestable DPA, a stated retention period, an executable deletion path for a requester's data, an audit log, or attachment handling.

OTRS

No API, no webhooks, no SSO, no named CRM or shop integration — nothing. The named Google, HubSpot and 6sense entries in are the vendor's own website marketing stack, not product integrations, and I won't count them as such.

Znuny

The only external-system connectivity shown is mail collection, including Microsoft Graph alongside IMAP and POP3. We found no public information on an API, webhooks, named CRM or shop integrations, SSO, SCIM, rate limits, or a sandbox — a support team would be copying customer context in by hand.

OTRS

The contracting entity is genuinely German — OTRS GmbH, Amtsgericht Frankfurt HRB 143059, Oberursel address, German VAT — which rules out the bottom anchors. But hosting and data residency for a customer's ticket archive are stated nowhere, the product's own subprocessor list is absent, and the vendor's own chain runs US processors (Google Tag Manager, LinkedIn, Vimeo) with third-country transfers declared possible — where my archive lives is the first question I ask, and this sheet can't answer it.

Znuny

The German contracting entity is fully evidenced — Berlin address, Charlottenburg commercial register number, VAT ID — and the software is downloadable to run wherever we choose, so archive placement is in our own hands. We found no public information on hosting, ownership, subprocessors, or certification behind the professional services, which keeps it from going higher.

OTRS

Three separate captures of the homepage produced not one price, tier, add-on or billing term. A support lead can't compute any invoice from this, so it's the floor.

Znuny

The licence price is public and unambiguous — the homepage states the software as "Free as free can be" with the latest release downloadable — so the software invoice is computable for any agent count with no tiers, bundles or add-on gates. What carries no public pricing is the professional services layer a team like mine would actually engage, and that is where computing the real annual cost stops.