Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by OTRS AG · otrs.com

Compare with Zammad → Compare with Znuny → Report an error on this page Is this your product? →

Link to this page

OTRS: AI-assisted analysis on whats-best.ai OTRS: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

OTRS at a glance

Vendor
OTRS AG
Headquarters
Incorporated in Germany source, captured 16 Nov 2026
Data hosting
In the EU by default source, captured 16 Nov 2026
Free plan
Not stated on the vendor’s pages as of 16 Nov 2026
Panel verdict
The AI panel rates OTRS 2/5, the mean of 6 judges. how scores are made
As of
Vendor pages captured 31 Aug 2026 to 16 Nov 2026; evaluated by the panel 17 Nov 2026. all sources

OTRS alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Integrator

Weighted verdict

Has to wire the helpdesk into a CRM, a shop and an identity provider that all predate it. Wants a documented API with rate limits, webhooks that retry, SCIM, and a sandbox. Reads a partner-contact form on an integrations page as a missing API.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Integrator

Panel median The Integrator This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Integrator
Ticketing, queues & SLA 2 of 5 2 of 5
Channels in one queue 1.5 of 5 1.5 of 5
Knowledge base & deflection 1 of 5 1 of 5
Customer data protection 2 of 5 1.5 of 5
Integrations & API 3 of 5 3 of 5
European sovereignty 2.5 of 5 2.5 of 5

Ticketing, queues & SLA

How this is scored

The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.

0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.

3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.

5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.

8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.

10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.

Report an error

The Integrator

Every ticket gets a unique number, classification and priority, changes are reliably stored in a ticket history, and queues, permissions, an agent dashboard, automation and workflows are all named on the product pages. What I could not find anywhere I read is an SLA target, response-time reporting, rule-based routing to teams and agents, or documented search across tickets — for a suite marketed as ITIL-aligned I expected the SLA machinery to be visible, and on these pages it is not. 4 1 4 9

Report an error

Channels in one queue

How this is scored

Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.

0 — No customer channel of its own; the product only works on tickets entered by hand or by another system.

3 — Email turned into tickets, with a web form or one further channel.

5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.

8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.

10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.

Report an error

The Integrator

The captured pages show an email server as a configured channel and an OTRS customer portal for end customers' requests and incidents, which is email plus one further channel. I found no public information on live chat, telephony, messengers or social channels landing in the same queue, so the evidence reaches exactly two channels and stops. 1 9

Report an error

Knowledge base & deflection

How this is scored

Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.

0 — No knowledge base or self-service of any kind; the product is a ticket inbox only.

3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.

5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.

8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning that flag stale content, and reporting on which articles deflect.

10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.

Report an error

The Integrator

Knowledge management appears in the solutions and use-case lists and FAQs are mentioned, but nothing I read documents articles, draft and publish states, suggestions to agents or customers, multilingual content or deflection reporting. I cannot wire deflection expectations from a keyword in a tag cloud. 2 1

Report an error

Customer data protection

How this is scored

A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.

0 — The vendor's own terms state that ticket content is used for purposes beyond providing the service, or that a data processing agreement is not offered.

3 — A privacy policy and a data processing agreement (DPA) offered, with agent roles that limit what an agent can do.

5 — A DPA published or signable online, agent roles and group- or queue-level visibility, and deletion of tickets or of a requester's data documented in the help centre.

8 — Automatic retention or deletion rules per queue or data category, attachment handling stated, an audit log of agent access or changes, documented support for access and erasure requests, and redaction of ticket content.

10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.

Report an error

The Integrator

Agent-facing limits are documented — queues and permissions, list and permission management over ticket content, and a reliable ticket history — alongside a published GDPR/Trust Center page and ISO 27001-managed infrastructure. I found no public information on a data processing agreement, product-level retention or deletion of ticket and requester data, attachment handling, redaction, or an audit log of agent access, so the product-side evidence sits at roles and permissions. 3 2 4 9

Report an error

Integrations & API

How this is scored

The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.

0 — A closed tool with no API and no integrations; context is copied in by hand.

3 — A handful of named integrations or a connector service such as Zapier, or an API with basic documentation.

5 — Named integrations for common CRM, shop or collaboration tools, a documented REST API, and webhooks or triggers that call other systems.

8 — An app marketplace with maintained bidirectional integrations, customer context from other systems shown inside the ticket, SSO and SCIM provisioning, documented rate limits and a sandbox.

10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.

Report an error

The Integrator

This is the strong suit for my stack: twenty-plus named integrations with sync language — HubSpot for customer synchronization, GitLab for ticket mirroring, GitHub for defect sync — plus Active Directory and Azure as external agent and customer backends, SSO integration in the managed configuration, ready-to-use connectors and a REST API named on both language versions of the integrations page. But the REST API is a marketing sentence, not a specification: I found no public information on rate limits, webhooks, SCIM provisioning, a sandbox or developer documentation of any depth, and no named shop or order-system integration despite a procurement-and-ERP category. 7 7 8 9

Report an error

European sovereignty

How this is scored

Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.

0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.

3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.

5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.

Report an error

The Integrator

The legal notice names EasyVista-OTRS GmbH of Oberursel, registered at the Frankfurt court, managed instances default to German hosting with USA or Canada only on request, on-premise gives complete control over system and server, and the website's own analytics run on a self-hosted Matomo. The chain underneath is thin: managed data sits on unnamed third-party provider servers, the privacy policy allows processors outside the EU for contract performance, and I found no published data processing agreement or product subprocessor list with locations. 3 2 6 9

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price or one priced tier, per agent or flat.

5 — Per-agent prices public for the main tiers with the billing period stated and the main features per tier listed.

8 — Every tier and add-on priced publicly with per-agent maths, telephony or messenger costs and light-agent or contact limits given, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.

10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.

Report an error

The Integrator

I found no public prices on any page I read; the trial is contact-gated — "Want to try OTRS for free? Let us know, and we'll set up a trial instance for you" — and the homepage's How to Buy section carried no figures in the captured pages. No support lead can compute an annual invoice for an agent count from what is published here. 1 9

Report an error

European sovereignty — proven facts

3 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location EU by default unverified
Why unverified?

This applies only to the Managed cloud offering, and the privacy policy additionally allows processors outside the EU; on-premises data remains on the customer's own servers.

2/4 pts 9 Report an error
Hosting options Self-hostable 1/1 pts 9 Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about OTRS

Is OTRS European?

Yes. whats-best.ai classifies OTRS as EU-Made. Its vendor, OTRS AG, is incorporated in Germany, per the vendor’s page captured 16 Nov 2026.

Where does OTRS store data?

OTRS stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026.

Does OTRS have a free plan?

Not stated on the vendor’s pages as of 16 Nov 2026.

What are the best alternatives to OTRS?

As of 18 Nov 2026, the panel rates Zendesk (3.5/5), LiveAgent (3.5/5) and Intercom (3.5/5) highest among the other 35 Customer Service & Helpdesk products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Zammad (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: OTRS alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (9)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage otrs.com Checked 16 Nov 2026 +3 earlier captures: 15 Sep 2026, 11 Sep 2026, 31 Aug 2026 Details →
  2. 2 Privacy policy otrs.com Checked 16 Nov 2026 +3 earlier captures: 26 Oct 2026, 15 Sep 2026, 31 Aug 2026 Details →
  3. 3 Imprint otrs.com Checked 16 Nov 2026 +1 earlier capture: 30 Sep 2026 Details →
  4. 4 Ticketing, queues & SLA — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  5. 5 Ticketing, queues & SLA — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  6. 6 Customer data protection — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  7. 7 Integrations & API — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  8. 8 Integrations & API — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
  9. 9 Self-hosting / on-premises installation docs — found from the homepage otrs.com Checked 16 Nov 2026 Details →