Panel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Dixa ApS · dixa.com
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.
Dixa at a glance
- Vendor
- Dixa ApS
- Headquarters
- Incorporated in Denmark source, captured 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Dixa 3/5, the mean of 6 judges. Dixa, a helpdesk and contact centre in one from Dixa ApS in Denmark — the vendor's words: "ticketing is a feature, not the identity" — earns its strongest scores on omnichannel, 7 to 9, for seven channels (phone, email, chat, WhatsApp, Instagram, Facebook, SMS) in one queue with a single timeline, browser-based calling with callback, IVR and recording, context carrying across chat, email and phone. how scores are made
- As of
- Vendor pages captured 29 Sep 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.
The panel's verdict
Dixa, a helpdesk and contact centre in one from Dixa ApS in Denmark — the vendor's words: "ticketing is a feature, not the identity" — earns its strongest scores on omnichannel, 7 to 9, for seven channels (phone, email, chat, WhatsApp, Instagram, Facebook, SMS) in one queue with a single timeline, browser-based calling with callback, IVR and recording, context carrying across chat, email and phone. Knowledge and self-service follow at 7 to 8, one article set feeding help centre, AI agent and agent suggestions. Pricing transparency is the weakest at 1 to 2: no price figure appears on any captured page; the terms bill voice per commenced minute, SMS per segment, with a 5 percent compounding annual indexation and VAT excluded. Scores diverge on ticketing core, 4 to 6 — documented routing, undocumented SLA targets, breach warnings and response-time reporting, weighted 4 by the skeptic persona and 6 by the others — and on integrations, where the integrator persona scored 4 to the rest's 5 and 6 on undocumented API references and no public SSO or SCIM information.
Speaks for it
- Seven channels — phone, email, chat, WhatsApp, Instagram, Facebook, SMS — land in one queue with one timeline, and context carries across chat, email and phone (omnichannel scores 7 to 9)
- Visual no-code routing by skill, language, priority, custom attributes and workload, with intent detection routing to a queue or filtering spam before a human is involved
- One article set feeds the help centre, the AI agent and agent suggestions, with AI translation into any language and stale-content flags
- Order, return and account data is pulled into the customer timeline, with Shopify, Trustpilot and Yotpo named
- A standard data processing agreement is integrated into the terms, a DPO is appointed, and irreversible anonymisation, content obfuscation and deletion of voicemails and call recordings are documented on the GDPR page
Held against it
- No price figure appears on any captured page (pricing transparency scores 1 to 2); the terms bill voice per commenced minute and SMS per segment, apply a 5 percent compounding annual indexation, auto-renew for twelve months with three months' non-renewal notice, and exclude VAT
- We found no public information on SLA targets, breach warnings, escalation paths or first-response and resolution-time reporting
- We found no public information on documented API references, webhooks outside Zapier, SSO or SCIM provisioning, or a sandbox, with API limits appearing only as overage terms
- We found no public information on automatic retention rules per queue, an audit log of agent access or attachment handling
- The terms state the services may be performed on equipment outside the EU under standard contractual clauses, and subprocessor locations are not shown on the captured pages
Best for
- You run phone, email and messaging conversations through one team and want every channel in a single queue and timeline — the bench's strongest range, 7 to 9 on omnichannel
- You are an EU-based buyer seeking a Danish contracting entity with EU customers' databases hosted on Amazon Web Services in Ireland and daily backups in another European location
- Your support volume is ecommerce-shaped and agents need order, return and account data inside the conversation
- You want one knowledge base powering the help centre, the AI agent and agent suggestions
Avoid if
- You must budget an annual invoice from public pages before a sales call — ask the vendor: the public pages we read do not show it
- You run support against contracted SLAs needing breach warnings and first-response and resolution-time reporting — the captured pages show routing and QA scoring instead, and ticketing core scores 4 to 6
- You need documented developer API references, SSO or SCIM provisioning from day one — integrations scores 4 to 6, with API limits appearing only as overage terms
- You process special categories of personal data — the terms prohibit using the service to collect, store, process or transmit it
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 3 of 5 |
| Channels in one queue | 4 of 5 |
| Knowledge base & deflection | 4 of 5 |
| Customer data protection | 3 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 1 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
Routing is the real strength: skills-based, language, priority and workload balancing plus intent detection and custom attributes, all built with a no-code visual rule builder. But the SLA half of the engine is undocumented — no public information on response-time targets, breach warnings, escalation timers, macros, merge and split, or ticket search — and the reporting that is documented is automated QA and performance scoring rather than first-response and resolution times by agent and queue. 4 5 1 3
The Agent Advocate
Routing is the real thing here: skill, language, priority and custom-attribute rules in a no-code builder, intent detection that routes or filters spam before a human sees it, and workload balancing — the vendor itself says ticketing is a feature, not the identity, and the routing evidence backs that up. I found no public information on SLA targets with breach warnings, macros, ticket merge and split, or first-response and resolution-time reporting — the machinery that makes a queue manageable at the hundredth reply. The Auto-QA dashboards scoring every conversation are the part I would least trust to help anyone close a ticket. 4 1 3 1
The Data Protection Officer
Routing is the documented strength: visual no-code rules by skill, language, priority and custom attributes, intent detection that routes to a queue before a human is involved, workload balancing, and every conversation automatically scored for QA and performance tracking. I found no public information on SLA targets, breach warnings, escalation paths, or a search that finds one ticket among ten thousand, which is what the measurement side of this engine needs. 4 5 1 3 1
The Shop Operator
Routing is the strong suit: skills-based and workload-balanced assignment, priority rules for VIPs, intent detection routing to a queue before a human sees it, and custom-attribute routing on order value or loyalty tier. We found no public information on SLA targets with breach warnings, ticket statuses, merge and split, or first-response and resolution-time reporting; Auto-QA scores conversations, which is coaching rather than SLA management. The vendor's own words, "ticketing is a feature, not the identity", match what the pages show. 4 5 1 3
The Integrator
Routing is genuinely documented: visual no-code rules route by skill, language, priority, VIP status, workload and custom attributes, intent detection can route to a queue or filter spam before a human is involved, and auto-QA scores every conversation with performance tracking across teams. We found no public information on SLA policies, breach warnings, escalation, or first-response and resolution-time reporting, so the engine is strong routing without the service-level machinery I would run customer contracts against. 4 5 1 1
The Skeptic
Routing is the documented strength — rules by skill, language, priority, custom attributes and workload, with intent detection routing before a human sees the conversation — but the captured pages state nothing on SLA targets, response-time reporting, ticket statuses or search across tickets, and the vendor's own comparison page says ticketing is a feature, not the identity. I score what is written down: a strong routing engine with the SLA half of this criterion undocumented. 4 5 1 3
Channels in one queue
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
Phone, email, chat, WhatsApp, Instagram, Facebook and SMS all land in one conversation with a single timeline, form submissions route into the same queue, and context carries over from chat, email or phone with a full transcript on handoff. Telephony is browser-based with callback, IVR and recording, and IVR-based call-recording consent is documented; I found no public information on a portal where a requester can see their own ticket status. 5 1 6 3 9
The Agent Advocate
This is the spine of the product: phone with browser-based calling, callback, IVR and recording, plus email, chat, WhatsApp, Instagram, Facebook and SMS, all landing in one timeline with full history, context carrying over from chat, email or the phone — the one screen rather than four tabs that I actually want. I found no public information on a portal where a requester can see their own tickets, or on WhatsApp consent handling, though IVR-based call-recording consent is documented. That leaves it just short of full marks but comfortably the strongest part of the evidence. 5 1 6 9 3
The Data Protection Officer
Phone, email, chat, WhatsApp, Instagram, Facebook and SMS are documented landing as one conversation with one timeline and full history, agents answering from one screen with context carrying over from chat, email or phone. The only gap I see is that consent handling for messengers is not stated, though call-recording consent routing with an IVR split between recorded and unrecorded queues is documented. 1 5 5 6 9
The Shop Operator
This is my real test and it passes: phone, email, chat, WhatsApp, Instagram, Facebook and SMS all land in one place with a unified timeline, calling is native browser-based with IVR, callback and recording rather than a bolt-on, and order data, returns and account details are pulled into the customer's timeline so the agent never opens a second login. We found no public information on a requester-side portal where customers see their own tickets, and consent handling is documented for call recording rather than for messengers specifically — that is what holds it short of the top. 5 1 5 6
The Integrator
Phone, email, chat, WhatsApp, Instagram, Facebook and SMS are documented landing in one place with full history, browser-based calling with callback, IVR and recording is native rather than bolted on, and context carries across chat, email and phone with the agent answering from one screen. We found no public information on consent handling for the messengers or a portal where a requester sees their own tickets, so I stop short of the top level. 5 1 5 6
The Skeptic
Seven named channels — phone, email, chat, WhatsApp, Instagram, Facebook, SMS — with form submissions routed into the same queue, every interaction in one timeline, and context carrying across chat, email and phone; that is one queue and one history, stated plainly rather than just logo-counted. The gaps: WhatsApp consent handling is not stated (only call-recording consent via IVR is documented), call logging per se is not stated, and a portal where a requester sees their own tickets is not documented beyond the branded help centre. 5 1 5 6
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
A searchable, branded help centre on a custom domain, with articles suggested to customers before they submit and surfaced to agents mid-conversation, AI translation into any language, stale content flagged for review, and agents authoring articles straight from conversations — one article source powers the help centre, the AI agent and agent suggestions. The gap for my queue is measurement: the reduction of inbound volume by up to 30 percent is a claim, and I found no public information on reporting that shows which articles actually deflect. 8 7 8 1
The Agent Advocate
Suggestions to the customer before they submit and articles surfacing automatically while the agent answers, AI translation into any language, flags for outdated content, and agents writing articles straight from conversations — one article set feeding the help centre, the AI agent and agent suggestions. Search analytics show what customers search for and where they get stuck, which is close to deflection reporting; the stated reduction of inbound volume by up to 30% is a claim, not a measured number I could act on. 8 7 8
The Data Protection Officer
A searchable, brandable public help centre with its own domain, article suggestions to customers before they submit and to agents while they answer, AI translation into any language, stale-content flagging, and one article source feeding the help centre, the AI agent and agent suggestions. Deflection is stated as an "up to 30%" marketing claim rather than reporting that shows which articles deflect, which is what would separate this from the highest level. 8 7 8 1
The Shop Operator
Deflection is treated as a number, which is what I want before the December peak: articles are suggested before a customer submits, the same articles feed agent suggestions and the AI agent, articles translate into any language with AI, and outdated content is flagged for review. Search analytics showing where customers get stuck plus a stated reduction of inbound volume by up to 30% approaches deflection reporting, though we found no public information on per-article deflection measurement or versioned content with approval. 8 7 1
The Integrator
The help centre is documented as searchable, branded and on a custom domain, with article suggestions to customers before they submit and to agents while answering, AI translation into any language, stale-content flags, agent authoring from conversations, and analytics on what customers search for and where they get stuck — one content source feeds the help centre, the AI agent and agent suggestions. Versioning with approval and per-article deflection reporting against ticket volume are not documented on the captured pages, and the 30 percent volume-reduction figure reads as a marketing claim rather than a report my team could act on. 8 7 8
The Skeptic
Suggestions before the customer submits, answers surfacing while the agent types, AI translation into any language, stale-content flags, and one article set feeding the help centre, the AI agent and agent suggestions — that is most of the top tier's feature list, and agents authoring articles from conversations is a nice touch. Deflection is asserted as "Reduce inbound volume by up to 30%" rather than evidenced as per-article reporting, and draft/publish workflow and categories are not documented. 8 7 8
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
A data processing agreement is required and ready to sign on request, end-user data is deleted on the customer's written request, an irreversible anonymisation feature covers a contact's details, email and chat content can be obfuscated with voicemails and call recordings deleted, and vendor employee access is need-to-know. I found no public information on automatic retention or deletion rules per queue, an audit log of agent access or changes, or attachment handling — and the terms prohibit using the service to process special categories of personal data. 9 13 2 14
The Agent Advocate
A standard data processing agreement applies and is ready to sign on request, access and erasure support is documented, a contact can be irreversibly anonymised, and email and chat content can be obfuscated with voicemails and call recordings deleted — real redaction, not just a policy line. I found no public information on automatic retention or deletion rules per queue, attachment handling, or an audit log of agent access, so it holds up well short of audit grade. 2 9 13 14
The Data Protection Officer
The GDPR compliance page documents mechanisms I can show an auditor: irreversible anonymisation of a contact's details in place of deletion, obfuscation of email and chat content, deletion of voicemails and call recordings, express consent collection, and access requests delivered in electronic format, with a DPO appointed and deletion executed on the customer's written request. What I found no public information on is retention that executes automatically per queue or data category, attachment handling, and an audit log of which agent read or changed which ticket — though vendor-side access is at least answered as invite-only and need-to-know. 9 13 14 2
The Shop Operator
The GDPR page documents real machinery: a standard DPA applies and is ready to sign, a contact's details can be irreversibly anonymised, email and chat content can be obfuscated, voicemails and call recordings deleted, and access requests are supported — redaction of ticket content is more than most pages show. We found no public information on automatic retention rules per queue, an audit log of agent access, or attachment handling, and permission control is evidenced for knowledge rather than for agent roles on tickets. 2 9 13
The Integrator
A data processing agreement applies as an integrated part of the terms and is ready to sign on request, a DPO is appointed, erasure is executed by irreversible anonymisation of a contact, email and chat content can be obfuscated with voicemails and call recordings deleted, and support for access requests is documented alongside need-to-know employee access. We found no public information on automatic retention rules per queue or category, attachment handling, an audit log of agent access, or agent role and queue-level visibility on tickets — the permissions we saw govern the knowledge base. 9 13 2 14
The Skeptic
The data processing agreement is integrated into the terms and ready to sign, a GDPR page documents irreversible anonymisation of a contact, obfuscation of email and chat content, deletion of voicemails and call recordings, and access/erasure handling, and a third-party provider list is published. We found no public information on agent roles or queue-level visibility, an audit log of agent access, automatic retention rules, or attachment handling — those keep it off the top tier. 9 13 14 2
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
Zapier runs bidirectionally with conversation triggers, an integration directory spans CRM, ecommerce and a dozen other categories, order data and account details are pulled into the customer timeline, and any messaging platform can connect through the API — with the terms noting API calls are subject to quantitative limits charged as overage. I found no public information on documented REST API references, SSO or SCIM provisioning, or a sandbox. 11 10 5 5 2
The Agent Advocate
Customer context inside the ticket is proven — order data, returns and account details pulled into the customer timeline — with Shopify, Trustpilot and Yotpo named, plus a bidirectional Zapier connection that triggers on new conversations. We found no public information on a documented REST API reference, SSO or SCIM provisioning, or a sandbox, and API limits appear only as overage clauses in the terms of service. 5 5 11 1 2 10
The Data Protection Officer
An integrations directory spanning twelve categories, a bidirectional Zapier connection that triggers workflows from new conversations, order and account data pulled into the customer timeline inside the ticket, and an API for connecting messaging platforms. The API's own documentation is not shown on the captured pages, rate limits appear only as contract language about overage charging, and I found no public information on single sign-on or SCIM provisioning. 10 11 5 2 14
The Shop Operator
Order data, returns and account details pulled into the timeline — with Shopify orders handled directly — is exactly the shop context my agents need, and Zapier runs bidirectionally off new conversations. The directory names categories from CRM to ecommerce, and Trustpilot and Yotpo reviews are answered inside the product. We found no public information on documented REST API reference pages, SSO or SCIM provisioning, or a developer sandbox; API limits appear only as contractual overage terms. 5 11 10 1
The Integrator
Zapier is documented properly — bidirectional, triggering on new conversations — the directory lists a dozen categories including CRM and ecommerce, and order, return and account data is pulled into the customer timeline; the terms even bill API calls beyond quantitative limits as overage. But we found no public information on developer API documentation, webhooks outside Zapier, SSO or SCIM provisioning, a sandbox, or published rate-limit figures — the security page instead describes an email-token login — so I would be wiring this through a connector and a conversation, not a documented interface. 11 10 5 2 5
The Skeptic
Twelve integration categories plus an all-integrations directory, Zapier both directions with a trigger on new conversations, ecommerce order data pulled into the customer timeline, and an API for connecting messaging platforms whose calls are metered and charged as overage — real substance, though the categories page names categories rather than vendors. We found no public information on API documentation proper, a named CRM integration, SSO or SCIM provisioning, or a sandbox. 10 11 5 2
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
Dixa ApS in Denmark is the contracting entity, EU customers' databases sit in the EU datacentre on Amazon Web Services in Ireland with daily backups in another European location, a data processing agreement applies, and a third-party provider list is referenced. The terms still permit services to run on equipment outside the EU under standard contractual clauses, the delivery model is software-as-a-service with no public information on a self-hosted option, and subprocessor locations are not shown. 13 14 6 2 2
The Agent Advocate
The contracting entity is Dixa ApS in Denmark, EU customers' databases sit in an EU datacentre on named Amazon infrastructure in Ireland with daily backup elsewhere in Europe, a data processing agreement is part of the terms, and a third-party service provider list is published. The terms also state services may be performed outside the EU under standard contractual clauses, the captured pages do not show subprocessor locations, and the delivery model is described as Software-as-a-Service with no public information on a self-hosted option — solid European footing, a step short of end to end. 2 13 14 6 2
The Data Protection Officer
The contracting entity is Dixa ApS in Denmark, EU customers' databases are stated to be hosted in the EU on Amazon Web Services in Ireland with daily backups elsewhere in Europe, and the terms name possible non-EU processing with standard contractual clauses as the mechanism, alongside a standard DPA integrated into the agreement and a published link to the third-party provider list. This falls short of the top only in that the provider list's locations are not shown in the captures, certifications are deferred to Amazon's, and delivery is described as Software-as-a-Service with no self-hosted or private-cloud option documented. 2 13 14 2 6
The Shop Operator
The archive's home is documented concretely: Dixa ApS in Denmark is the contracting entity, EU customers' data sits on Amazon Web Services in Ireland with daily backups in another European location, and a standard DPA applies. Non-EU processing is addressed with standard contractual clauses as the legal basis and a third-party provider list is referenced — but the providers' locations are not shown, and we found no public information on a self-hosted option. 2 2 13 14 6
The Integrator
The contracting entity is Dixa ApS in Denmark, EU customers' databases are hosted in an EU datacenter on Amazon Web Services in Ireland with daily backups in another European location, and the data processing agreement is part of the terms; a third-party provider list is referenced and the possibility of non-EU processing is disclosed under standard contractual clauses. The provider list's locations are not shown on the captured pages and delivery is Software-as-a-Service only, so I stop one step short of a fully evidenced chain with a self-hosted escape hatch. 13 14 2 2
The Skeptic
The contracting entity is Dixa ApS in Denmark, EU customers' databases are hosted in an EU datacenter on Amazon's servers in Ireland with daily backups in another European location, non-EU processing is named with standard contractual clauses as its basis, and vendor-side access is restricted to invited employees and a few developers on a need-to-know basis. The provider list's locations are not shown in the captures, the terms also permit US hosting outside the EU-customer default, and we found no public information on a self-hosted or private-cloud option. 2 13 14 2 6
Pricing transparency
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 figures appear on any page we read — a pricing page is linked but the captured pages carry no amounts, so I cannot compute an annual invoice for my agent count. The terms are rich on billing mechanics — a 5 percent compounding annual indexation, payment in advance by card, a minimum commitment that cannot be reduced, voice charged per commenced minute, SMS per segment, VAT excluded — but there is no rate to set against a headcount. 6 2 2
The Agent Advocate
The pricing page is a link with no numbers on it and every path leads to a demo call, so I cannot compute any invoice for my agent count from public pages. The terms do publish the billing mechanics: voice charged per commenced minute with conference calls billed per participating call, SMS per segment, overage invoiced monthly, a 5% indexation rate applied annually on a compound basis, fees exclusive of taxes and paid in advance — the shape of the bill is public, the amounts are not. 6 3 2 2
The Data Protection Officer
The captured pricing page states no prices at all, so a support lead cannot compute an annual invoice for their agent count from public pages; the terms make clear that figures live in negotiated Order Forms. The terms do document the invoice's shape — voice per commenced minute, SMS per segment, monthly overage invoicing, a 5% compound annual indexation, fees excluding taxes, a minimum commitment — but we found no public per-agent or tier figures. 6 2 2 3
The Shop Operator
I cannot compute an invoice from these pages: no per-agent or tier price appears anywhere we read, the pricing link carries no figures, and the motion is a demo call. The terms do publish billing mechanics — voice per commenced minute, SMS per segment, monthly overage invoicing, taxes excluded, a compounding 5% annual indexation — but mechanics without magnitudes leave the annual invoice unknowable. 6 2 2 3
The Integrator
The captured pages point to a pricing page but state no prices on it, and we found no per-agent or per-tier figures anywhere else; the terms are rich on mechanics — payment in advance, voice per commenced minute, SMS per segment, overage invoiced monthly, a 5% compound annual indexation, VAT excluded — without figures a buyer could apply to their agent count. A support lead cannot compute the real annual invoice from these pages. 6 2 2
The Skeptic
A pricing page is linked, but the captured pages give no price figure at all — no tier, no per-agent amount, not even a from price — so a support lead can compute nothing from public evidence. What the terms do state is the machinery: voice charged per commenced minute, SMS per segment, VAT excluded, a 5% compounding annual indexation, payment in advance by card, twelve-month auto-renewal with three months' non-renewal notice, overage invoiced monthly, and no refunds. 6 2 2
European sovereignty — proven facts
2 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 DK | 2/2 pts | 12 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options |
Cloud service only
unverified
Why unverified?The Terms describe the delivery model as Software-as-a-Service but never explicitly state that no self-hosted or on-premises option exists. |
0/1 pts | 2 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 Dixa
Is Dixa European?
Not determined: the vendor’s pages as captured do not say where Dixa is based. Its vendor, Dixa ApS, is incorporated in Denmark, per the vendor’s page captured 16 Nov 2026.
Where does Dixa store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Dixa have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Dixa?
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: Dixa alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 29 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Hosting location. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Hosting options. The Terms describe the delivery model as Software-as-a-Service but never explicitly state that no self-hosted or on-premises option exists.
- 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.
- 132 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
- 16 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
- 15 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
- 13 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
- 8 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
- 7 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
- 4 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
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (14)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page dixa.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 29 Sep 2026 Details →
- 2 Terms of service — found from the homepage www.dixa.com Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
- 3 Ticketing, queues & SLA — found from sitemap www.dixa.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 26 Oct 2026 Details →
- 4 Ticketing, queues & SLA — found from sitemap www.dixa.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 5 Channels in one queue — found from sitemap www.dixa.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 26 Oct 2026 Details →
- 6 Channels in one queue — found from sitemap www.dixa.com Checked 16 Nov 2026 +3 earlier captures: 2 Nov 2026, 26 Oct 2026, 1 Oct 2026 Details →
- 7 Knowledge base & deflection — found from sitemap www.dixa.com Checked 16 Nov 2026 Details →
- 8 Knowledge base & deflection — found from sitemap www.dixa.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 9 Customer data protection — found from sitemap www.dixa.com Checked 16 Nov 2026 Details →
- 10 Integrations & API — found from sitemap www.dixa.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 11 Integrations & API — found from sitemap www.dixa.com Checked 16 Nov 2026 Details →
- 12 Legal notice — found from the homepage www.dixa.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 13 Privacy policy — found from the homepage www.dixa.com Checked 16 Nov 2026 Details →
- 14 Security / trust page — found from the homepage www.dixa.com Checked 16 Nov 2026 Details →