OTRS
EU-Made Report an errorPanel 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
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
Read this page as one judge. Each weighs the same scores by what they care about.
No written verdict for this product
The panel scored OTRS, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 2 of 5 |
| Channels in one queue | 1.5 of 5 |
| Knowledge base & deflection | 1 of 5 |
| Customer data protection | 2 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 2.5 of 5 |
Ticketing, queues & SLA
Show reasoningHide reasoning
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.
The Support Lead
A real ticket engine is documented: every ticket gets a unique ticket number, changes are reliably stored in the ticket history, tickets can be classified and prioritized, and queues, permissions and an agent dashboard appear in the managed setup, with automation and reporting named as headline features. I found no public information on SLA targets, breach warnings, escalation or search across tickets — the timers my team lives by — so I can't take it past the middle. 4 1 4 9
The Agent Advocate
Every ticket gets a unique ticket number, changes are reliably stored in the ticket history, and the pages list classification, prioritisation, queues and a generic business-process automation claim. I found no public information on SLA targets, escalation, macros, merge and split, or search across a large ticket base, so I cannot go higher than just past basic ticket tracking. 4 4 1 9
The Data Protection Officer
Tickets carry unique ticket numbers, can be classified and prioritised, live in queues with their own permissions, and every change is reliably stored in the ticket history — a change log I want kept. Business process automation and reporting are named on the homepage. We found no public information on SLA targets, response-time reporting, escalation or search across the archive, so the evidence reaches routing and tracking, not managed workloads. 4 1 4 9
The Shop Operator
Every ticket carries a unique ticket number, tickets can be classified and prioritized, and every change lands in the ticket history, with content access controlled through list and permission management. Business process automation, workflows and reporting are named as features, and queues appear in the managed setup. The captured pages do not show SLA targets, response-time reporting or search across tickets, so I cannot place this higher than solid mid-level. 4 4 1 9
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
The Skeptic
Tickets carry a unique ID, can be classified and prioritized, and every change is stored in the ticket history; business process automation and workflows are stated at marketing-page level, and queues, permissions and an agent dashboard appear in the managed setup list. I read for where the SLA policies begin and found none: no SLA targets, escalation rules or response-time reporting on any captured page, and reporting is a single word on the homepage. 4 1 4 9
Channels in one queue
n/r
Show reasoningHide reasoning
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.
The Support Lead not rated — no public information
We found no public information on which customer channels — email, chat, phone, portal or messengers — land in one queue with one history. The pages we read describe tickets, integrations and hosting, but say nothing about inbound channels for requesters. 1 4 7 9
The Agent Advocate
The captured pages document an email server as part of the managed setup and a customer portal for customers' requests and incidents, which is email plus a portal. Beyond that I found no public information on live chat, telephony or messengers landing in one queue with one history. 9 1
The Data Protection Officer
The on-premises and managed documentation names an email server configuration and an OTRS customer portal for customers' requests and incidents — email plus one further channel. We found no public information on live chat, telephony, messengers or social channels arriving in one shared inbox with one history. 1 9
The Shop Operator
The channel evidence I found is an email server configuration plus Active Directory/LDAP and a customer backend in the managed setup, and a customer portal reference for requesters' requests and incidents. We found no public information on live chat, telephony, WhatsApp or other messengers, or social channels landing in one queue, so as far as the captured pages go, the messenger traffic my shop runs never joins the ticket queue. 9
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
The Skeptic
Counting the channels that actually write into the queue: the managed setup configures an email server, and that is the one channel the captured pages document. The integration directory lists DevOps, monitoring and asset tools rather than chat, telephony or messenger connectors, so we found no public information on anything beyond email landing in one history. 7 8 9
Knowledge base & deflection
Show reasoningHide reasoning
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.
The Support Lead
Knowledge management appears only as a term in the use-case list on the homepage. We found no public information on articles, a help centre, publishing workflow, article suggestions or deflection reporting, so this barely registers. 1
The Agent Advocate
Knowledge management appears as a term in the solutions and use-case lists, and nothing more. I found no public information on a public help centre, article workflow, suggestions to agents or customers before submission, or deflection reporting. 1
The Data Protection Officer
Knowledge management appears once as a use-case label on the homepage, and the FAQs and online documentation mentioned are the vendor's own support channels, with FAQ viewing tied to an OTRS ID registration. We found no public information on a product help centre with published articles, a draft or review workflow, article suggestions, or deflection reporting. 2 1 9
The Shop Operator
Knowledge management appears in the use-case list, and that is the whole of the knowledge evidence. We found no public information on a help centre, article workflow, article suggestions to agents or customers, or any deflection reporting, so I cannot credit deflection the way I measure it. 1
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
The Skeptic
Knowledge management appears as a word in the use-case list and content can be made accessible or excluded through list and permission management — an internal content store at most. We found no public information on a searchable public help centre, article workflow, suggestions to customers or agents, or deflection reporting; the FAQs mentioned belong to the vendor's own download and support portal. 1 4 9
Customer data protection
Show reasoningHide reasoning
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.
The Support Lead
The privacy pages name a data protection officer, list subject rights from correction through erasure and portability, state technical and organisational measures, and set concrete retention periods for the data the vendor collects; the product pages document list and permission management over who can see content. We found no public information on a data processing agreement, on retention or deletion of ticket archives specifically, or on audit logs and redaction. 6 2 4 6
The Agent Advocate
There is a published privacy statement with a named data protection officer, stated subject rights including erasure and portability, and concrete deletion timelines, plus in-product permission management that can include or exclude users from content. The data processing agreement question is open on these pages, and I found no public information on product-level retention rules per queue, redaction of ticket content, or an audit log of agent access. 4 6 6
The Data Protection Officer
A privacy policy in German and English names an external data protection officer, grants correction, deletion, restriction, objection and portability rights and states technical and organisational measures, while the product side shows permission management, queue-level permissions and a ticket history storing every change. The retention periods actually published — ten years of email archiving, five years for business contacts, three for trial registrations — concern the vendor's own website and applicant data, not a customer's ticket archive. We found no public information on a data processing agreement, automatic retention or deletion of tickets, redaction of ticket content, an audit of which agent read what, or whether the vendor's support staff can open a customer ticket. 6 2 4 6 9 2
The Shop Operator
There is a privacy policy with technical and organisational measures, a named data protection officer, and documented rights to correction, deletion, restriction, objection and portability, while inside the product list and permission management controls who can access content and ticket changes are stored in history. We found no public information on a data processing agreement, on deletion of a requester's ticket data, or on retention rules per queue, which caps this below the audit-ready level. 6 4 3
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
The Skeptic
The privacy policy, data-protection officer and subject-rights text govern the vendor's own website and marketing data, and the retention periods given — six months for applicant data, ten years of email archiving for tax law — likewise concern the vendor, not a customer's ticket archive. Product-side there are queues and permission management; we found no public information on a data processing agreement, documented ticket deletion, retention rules per queue, or an audit log of agent access. 6 2 4 6 9
Integrations & API
Show reasoningHide reasoning
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.
The Support Lead
Roughly twenty named connectors across monitoring, asset and inventory, DevOps, HR and customer synchronisation — HubSpot, Active Directory, Azure, GitLab and Icinga among them — plus ready-to-use connectors, a REST API described as extending anything, and SSO with an LDAP and customer backend configured in the managed setup. We found no public information on webhooks, SCIM provisioning, rate limits, a sandbox or an app marketplace, which holds it below the top band. 7 7 8 9
The Agent Advocate
Two dozen named integrations across monitoring, DevOps, asset management and CRM (HubSpot, Asana, GitLab, Checkmk, Active Directory), ready-to-use connectors, a documented REST API, and SSO integration in the managed setup. I found no public information on webhooks calling other systems, SCIM provisioning, documented rate limits or a sandbox, so it stops at a solid middle rating. 7 8 7 9
The Data Protection Officer
More than twenty named integrations are documented across fourteen categories, from identity (Active Directory, Azure) and CRM (HubSpot) to DevOps (GitHub, GitLab) and monitoring (Icinga, Checkmk, Grafana), alongside a REST API, ready-to-use connectors and SSO configuration in the managed onboarding. We found no public information on an app marketplace, documented rate limits, a sandbox or SCIM provisioning, so the API's depth rests on the availability claim alone. 7 7 8 9
The Shop Operator
More than twenty named integrations are documented across categories — HubSpot for customer sync and ticket mirroring, GitLab, Asana, Azure DevOps, monitoring tools like Icinga and Checkmk, asset tools, plus Active Directory, Azure and SSO integration as agent and customer backends — with ready-to-use connectors and a REST API to extend anything. For a shop operator I have to note we found no shop or order system among the named integrations, and the pages give no app marketplace, rate limits or sandbox. 7 8 7 9
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
The Skeptic
A long named catalogue — HubSpot, Asana, GitLab, GitHub, Azure DevOps, monitoring and asset systems, Active Directory and Azure backends — across fourteen categories, plus a REST API named on the marketing page and SSO integration in the managed setup. But the pages show pairing blurbs, not a maintained marketplace, and we found no public information on documented rate limits, a sandbox, SCIM provisioning or webhooks. 7 7 8 9
European sovereignty
panel opinion
Show reasoningHide reasoning
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.
The Support Lead
The contracting entity is EasyVista-OTRS GmbH, registered in Oberursel with a Frankfurt commercial register entry; the managed cloud stores data on servers in Germany by default, and an on-premises option gives complete control over system and server. The privacy policy itself states processors could also be used outside the European Union, and we found no public information on a published data processing agreement or on the named hosting provider, so the chain is only partly established. 3 6 9 2
The Agent Advocate
A German contracting entity registered at the Frankfurt court, managed cloud data stored by default in Germany with optional USA or Canada regions on request, and a self-hostable on-premise option that keeps the archive on the customer's own servers. The third-party hosting provider is not named, the privacy policy allows processors outside the EU, and I found no published data processing agreement or product subprocessor list with locations. 3 9 6
The Data Protection Officer
The contracting entity is a German GmbH registered in Frankfurt with a German VAT number, the managed offering stores data in Germany by default with the USA or Canada on request, an on-premises option gives complete control over system and server, and ISO 27001 is claimed for the managed infrastructure. Non-EU processors are at least named in the privacy policy with standard contractual clauses as the safeguard. The hosting runs on unnamed third-party servers, and we found no public information on a published data processing agreement, a subprocessor list with locations for the service itself, or which vendor staff can reach a managed instance. 3 6 9 2
The Shop Operator
The contracting entity is a German GmbH registered in Oberursel with a Frankfurt commercial register entry, managed cloud data is stored in Germany by default, and the on-premise option keeps the archive on our own servers, which is the strongest control I can ask for. Against that, the data-centre provider behind the managed offering is unnamed, we found no public information on a data processing agreement, and the privacy policy allows processors outside the EU in contract performance. 3 9 6 2
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
The Skeptic
The contracting entity is German — EasyVista-OTRS GmbH in Oberursel, registered in Frankfurt — managed instances store data in Germany by default, and an on-premise option gives complete control over system and server. The servers belong to an unnamed third-party provider, the privacy policy reserves the use of processors outside the European Union, and we found no public information on a data processing agreement or a published list of subprocessors for the product itself. 3 6 9
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
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.
The Support Lead
No price figure appears anywhere on the pages we read; the only public offer is a free trial set up on request, alongside a How to Buy link. We found no public per-agent or tier pricing, so I cannot compute an annual invoice for my twelve agents from these pages. 1 9
The Agent Advocate
I found no public prices on any page captured here; the only commercial signals are a free trial instance set up on request and a How to Buy section. A support lead cannot compute the annual invoice for their agent count from these pages, so every purchase is a conversation. 9 1
The Data Protection Officer
No price figure appears on any captured page — no per-agent rate, no tier, no 'from' price — and even the free trial is something the vendor sets up after you "let us know". A "How to Buy" navigation item points into what is evidently a sales conversation. A support lead cannot compute any part of the annual invoice from these pages. 1 9
The Shop Operator
The captured pages give no price figure for any tier or edition; purchasing runs through a How to Buy route and the trial is arranged on request, quoted as 'Let us know, and we'll set up a trial instance for you.' A support lead cannot compute the annual invoice for their agent count from what is published here. 1 9
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
The Skeptic
We found no price figure on any captured page — not a per-agent price, a tier or an add-on — and the only pricing-adjacent items are a "How to Buy" link and a trial the vendor sets up after you "let us know". A support lead cannot compute any part of the annual invoice from these pages. 1 9
European sovereignty — proven facts
3 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in DE
unverified
Why unverified?No excerpt states a parent company's seat, so this German-registered entity is treated as the parent, though its name suggests affiliation with the EasyVista group. |
2/2 pts | 3 Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 31 Aug 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity. No excerpt states a parent company's seat, so this German-registered entity is treated as the parent, though its name suggests affiliation with the EasyVista group.
- Weak sourcing — Hosting location. 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.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 107 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 38 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 16 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 9 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 9 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. Know more? Tell us
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage otrs.com Checked 16 Nov 2026 +3 earlier captures: 15 Sep 2026, 11 Sep 2026, 31 Aug 2026 Details →
- 2 Privacy policy otrs.com Checked 16 Nov 2026 +3 earlier captures: 26 Oct 2026, 15 Sep 2026, 31 Aug 2026 Details →
- 3 Imprint otrs.com Checked 16 Nov 2026 +1 earlier capture: 30 Sep 2026 Details →
- 4 Ticketing, queues & SLA — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 5 Ticketing, queues & SLA — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 6 Customer data protection — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 7 Integrations & API — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 8 Integrations & API — found from sitemap otrs.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 9 Self-hosting / on-premises installation docs — found from the homepage otrs.com Checked 16 Nov 2026 Details →