OTRS vs Znuny

OTRS

Not one fact about routing, queues, SLA timers, escalation or search appears in any capture; a 'Customer Service & Helpdesk' category label and a homepage are all I have, and a label is not an engine. Absence this total sits at the bottom of the scale, with a single point only for the category claim.

Znuny

Queues are documented as permission objects with grouping by department, service, product or country, moving and splitting for inter-team hand-off, and personal My Queues views with drill-down filtering; ownership, priority, and pending and close permissions imply a working status model. We found no public information on SLA timers, breach warnings, escalation chains, reporting on first-response and resolution time, or full-text search across ticket bodies.

OTRS

No chat, portal, phone, or messenger integration is evidenced anywhere in the evidence, so there is nothing to credit beyond the helpdesk category's implied email handling — which is the anchor-zero position. The marketing site's own channels (forums, video, X buttons) are about OTRS, not the product's queue.

Znuny

Mail collection is documented in depth — any number of accounts over IMAP, POP3 and Microsoft Graph with OAuth2, folder selection and per-account fetch — and a phone-screen permission lets agents record calls as tickets, so this is email plus agent-logged calls. We found no public information on live chat, a customer portal, messengers or telephony integration landing in one queue.

OTRS

The only knowledge-adjacent fact is that OTRS's own website shows FAQs to registered visitors — a vendor article list, not a product help centre, editorial workflow, or deflection reporting. Nothing here evidences the product organising or reducing ticket volume.

Znuny

We found no public information on a knowledge base, help centre, article workflow, article suggestions or deflection reporting in any captured page; the product is presented as corporate-level ticket management and the queue documentation covers queues alone.

OTRS

The vendor polices its own house well — named external DPO (IITR), published privacy statement, Trust Center, and concrete retention per data category (6-month application data, 3-year trial, 10-year email archive) — but says not one word about the product: no queue-level retention rules that execute, no redaction, no audit of who opened which ticket, no DPA, no answer on vendor support access, and a blanket 'usually 10 years' is a hoard, not a policy. That is a compliance posture, not capability, and it sits between rubric level 0 and 3.

Znuny

The permission model is the one documented strength: seven queue-level permissions from read-only to full access, with optional extended permissions behind system configuration, giving real control over which agents see which queue. Beyond that we found no public information on retention periods, executable deletion of a requester's data, an audit log of who opened which ticket, attachment handling, redaction, or a published data-processing agreement.

OTRS

No API, webhook, SSO, rate limit, or named integration appears in any captured page; context would have to be copied in by hand, which is precisely the zero anchor. Across three homepage captures not a single system-to-system fact surfaced.

Znuny

We found no public information on a documented API, named CRM, shop or identity integrations, webhooks, SSO or SCIM provisioning in the captured pages; the connectivity evidence covers mail protocols only, which is inbound mail rather than system-to-system context.

OTRS

The contracting entity is firmly German — OTRS GmbH, Oberursel, HRB 143059 at Amtsgericht Frankfurt, DE VAT — and the privacy policy does name subprocessors and discloses third-country transfers with SCCs for the US video-conferencing processor. But that subprocessor list is the marketing website's trackers (Google, LinkedIn, Vimeo, 6sense), the hosting location of a customer's ticket archive is nowhere stated, and whether OTRS support can open a customer instance goes unanswered — better than the pipeline's zero, short of anchor five.

Znuny

The contracting entity is firmly European — Znuny GmbH of Berlin with a Charlottenburg commercial register entry and German VAT ID — and the software ships as a download, so a buyer can run the archive on their own infrastructure. We found no public information on hosting arrangements, subprocessors, ownership or certification, which leaves the processing chain unevidenced.

OTRS

No price, tier, add-on, billing period or agent-count fact appears in any capture; a support lead could not compute even a rough invoice from this evidence, which is the bottom anchor.

Znuny

The software is free and downloadable — "Free as free can be" — so the annual licence invoice is zero for any agent count with the feature set as shipped, and no tiering is implied. The one unpriced element is Znuny Professional Services, for which no public prices are given.