Customer Service & Helpdesk
eDesk
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by eDesk (formerly xSellco) · edesk.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.
eDesk at a glance
- Vendor
- eDesk (formerly xSellco)
- Headquarters
- Not stated on the vendor’s pages as of 20 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 20 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 20 Oct 2026
- Panel verdict
- The AI panel rates eDesk 3/5, the mean of 6 judges. eDesk is an ecommerce helpdesk from xSellco Limited, an Irish entity registered in Dublin 4. how scores are made
- As of
- Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
eDesk is an ecommerce helpdesk from xSellco Limited, an Irish entity registered in Dublin 4. Its strongest criteria are customer data protection and omnichannel, both clustering at 6-7; the weakest are pricing transparency and sovereignty. The strengths are concrete: a GDPR Article 17 erasure path replaces ticket subjects and bodies with «REDACTED», including archived copies, and one workspace takes email, webstore, marketplace, live chat and WhatsApp as tickets with Shopify order history in view. Ticketing core sits at a flat 6 on real SLA timers, including a business-hours Company timer and a marketplace timer with Amazon's 24-hour default; knowledge and self-service trails at 5-6. On pricing, only Essential carries a public figure — €39 per agent/ month with a stated 20% annual saving — while Growth, Professional and Custom carry no public price in the captured pages. The flagged splits flagged nothing; the lone 4 on pricing transparency credited the listed store and marketplace allowance per tier, and the two 5s on sovereignty weighed named transfer safeguards against independent sourcing that returned unknown and WhatsApp running through Meta.
Speaks for it
- GDPR Article 17 erasure is documented to field level, replacing ticket subjects and bodies with «REDACTED», including archived copies, and deleting attachments and AI summaries
- Email, webstore, marketplace, live chat and WhatsApp land as tickets in one workspace, with Shopify order history and previous conversations in the same view
- SLA timers include a Company timer that counts business hours only and a marketplace timer with a 24-hour Amazon default, with the mailbox ordered by least time left
- A published data processing addendum applies automatically, with delete-or-return on termination and 30 days' notice before any new third-party processor
- Returns, cancellations and order adjustments are processed inside the helpdesk through the Shopify integration, with a documented API naming calls like Create Message and Upload Tracking Information
Held against it
- Only Essential carries a public price — €39 per agent/ month — while Growth, Professional and Custom carry no public price in the captured pages
- Retention is stated only as "as long as necessary", with retention periods and service-provider details available only on request by email
- We found no public information on escalation chains, ticket merge and split, or first-response and resolution reporting by agent and queue
- The captured pages give different figures for the plan that unlocks the API — an advanced RESTful API listed under Professional, and an API article naming the Enterprise plan
- WhatsApp traffic runs through Meta as platform partner since the end of June 2025, with no safeguard specific to that leg shown on the captured pages
Best for
- You run a Shopify store and want order history, shipping status, returns and cancellations handled inside the same ticket queue
- You must answer marketplace messages within fixed windows such as Amazon's 24-hour expectation, from one mailbox
- You need a GDPR Article 17 erasure process documented to field level that you can hand to a data protection officer
- You want to evaluate the full product before committing, via a 14-day free trial that includes every feature
Avoid if
- You must cost the full contract before signing — only the Essential price is public, and tickets already counted toward the monthly bill continue to count even after a customer's data is erased
- Your procurement requires a published subprocessor list or a named data-centre provider — the captured pages show service-provider and retention details available only on request by email
- You need first-response and resolution reporting by agent and queue — the captured pages show only a 'Detailed Reporting Extracts' line on the Professional plan
- You depend on telephony support with call logging — the feature list names a 'Talk' feature without describing what it does
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 3 of 5 |
| Channels in one queue | 3.5 of 5 |
| Knowledge base & deflection | 2.5 of 5 |
| Customer data protection | 3.5 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 1.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 — A shared mailbox with labels; no ownership, no status model, no history beyond the thread.
3 — Tickets with assignment and open/closed status, but routing is manual, there are no SLA timers and search covers subject lines only.
5 — Queues with rules-based routing, priorities, a working status model, SLA timers with breach warnings, and full-text search across ticket bodies.
8 — Business-hours-aware SLA policies per queue or customer, escalation chains, macros and triggers, merge and split, 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
The SLA machinery is real and better than a countdown clock: a company timer that counts business hours only and pauses outside them, a marketplace timer that ignores office hours and takes Amazon's 24-hour default, a Time Left column that orders the mailbox by least time remaining, and an Overdue-plus-minutes readout once a target slips. Routing is thinner — "intelligent ticket routing" sits on the marketing page and chat agents claim unassigned conversations by hand — and I found no public information on escalation chains, merge and split, or first-response and resolution reporting by agent and queue beyond a "Detailed Reporting Extracts" line on the top plan, nor on what search covers. 1 3 4 5 12
The Agent Advocate
The SLA machinery is genuinely good: a business-hours timer that pauses outside office hours, per-marketplace timers with a 24-hour Amazon default, an Overdue counter, and a mailbox that puts least-time-left at the top. Beyond snippets and a marketing claim of intelligent routing I found no public information on full-text search across ticket bodies, merge and split, escalation chains, or first-response and resolution reporting by agent and queue. 3 4 1 5 12
The Data Protection Officer
SLA handling is genuine: a business-hours-aware Company SLA timer that pauses outside office hours, per-marketplace timers with a 24-hour Amazon-style default, overdue readouts, and a mailbox ordered by least time left. Beyond the timers the record thins — we found no public information on escalation chains, ticket merge or split, or first-response and resolution reporting by agent and queue, and search is mentioned only in passing. 1 4 12
The Shop Operator
The engine is genuinely there: SLA timers that count down during business hours and can be set per marketplace, an Overdue display with time past target, and a mailbox that lists the ticket with least time left first — exactly how a parcel-tracking queue should be driven. Statuses, claiming, snippets and rule-based automations are evidenced too. We found no public information on escalation chains, merge and split, first-response and resolution reporting by agent and queue, or full-text search across ticket bodies. 1 3 4 5 12
The Integrator
The SLA machinery is real: a business-hours-aware Company SLA timer that pauses outside office hours, per-marketplace timers with overridable targets, overdue warnings that count up past the target, and a mailbox ordered by time remaining, plus AI ticket grouping and snippets. We found no public information on escalation chains, merge and split, or reporting on first-response and resolution time by agent and queue. 4 1 12 5
The Skeptic
Two SLA timers are genuinely documented — a Company timer that counts down only during your business hours and a per-marketplace timer that runs around the clock with Amazon's 24-hour default — with an Overdue-plus-minutes readout, To Do and Resolved states, and a mailbox sorted by least time left. That is a real engine, but we found no public information on escalation chains, merge and split, or first-response and resolution-time reporting by agent and queue; "intelligent ticket routing" is a homepage phrase with no settings page behind it in the captured pages. 1 3 4 5
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 — Email only.
3 — Email plus one more channel, but the second lives in its own inbox: no shared history, and a customer who switches channel starts again.
5 — Email, a web form or portal and live chat all landing as tickets in one queue, with the customer's history visible whichever channel they used.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp, Signal or similar) with its consent handling stated, and a customer portal where a requester can see their own tickets.
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
Email, webstore and marketplace messages, social messaging, live chat and WhatsApp all land as tickets in one centralized workspace, with Shopify order history and previous conversations shown against every ticket — my agents would work one queue with one customer view. WhatsApp is properly documented: two-way messaging, customer opt-in and approved templates before any proactive outreach, and the platform partner named (360 Dialog to the end of June 2025, Meta since). The pages name a "Talk" feature without saying what it does, and I found no public information on telephony with call logging or a portal where a requester can see their own tickets. 1 3 5 6 8 12
The Agent Advocate
Email, web forms, live chat and WhatsApp all end up as tickets in one mailbox, WhatsApp's consent rules are spelled out down to approved templates and opt-in, and the Shopify view puts order history and past conversations on one screen. I found no public information on telephony beyond a feature name, and none on a portal where a requester can see their own tickets. 5 6 12 8 1
The Data Protection Officer
Email, webstores, marketplaces, live chat and WhatsApp all become tickets in one workspace, with order history and previous conversations shown in a single view; WhatsApp consent handling is properly documented, from customer opt-in to template approval. We found no public information on a customer portal where a requester sees their own tickets, and the only telephony evidence is a lone word, Talk, on a features list. 1 5 6 12
The Shop Operator
WhatsApp and the shop genuinely land in one queue: a WhatsApp message creates a ticket with its opt-in and template consent handling stated, a finished live chat closes into a ticket, and every ticket carries the Shopify order history and shipping status in one view. A feature named Talk appears in the feature list, but we found no public information on call logging behind it. We also found no public information on a customer portal where a requester can see their own tickets. 1 5 6 12
The Integrator
Email, webstore, live chat, marketplaces and social messaging land as tickets in one workspace with the customer's Shopify order history and previous conversations in one view, and WhatsApp consent handling is spelled out — opt-in required, template approval, no free text when initiating. We found no public information on telephony with call logging beyond a feature name, or on a customer portal where a requester can see their own tickets. 1 5 6 12
The Skeptic
Chat closes into a To Do or Resolved ticket in the same Mailbox, WhatsApp arrives as a ticket, and the WhatsApp consent handling is actually spelled out — opt-in required, template approval, proactive messages restricted to approved templates, Meta named as the platform partner since June 2025. A feature called Talk sits in the navigation, but we found no public information on call logging behind it, and the customer-facing knowledge base offers a submit-a-ticket form with no public information on a requester viewing their own tickets. Shopify order history and previous conversations do appear in one view inside the ticket. 1 5 6 8 12
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; answers live in agents' heads and old tickets.
3 — A basic article list, public or internal, with no editorial workflow, no versioning and no link between articles and tickets.
5 — A searchable public help centre with categories, draft and publish states, and agents able to insert an article into a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates 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
There is a genuine public help centre — libraries on a public URL or custom domain, categories and nested sub-categories, CSS restyling, password protection — plus AI-assisted search that scans for relevance beyond exact keywords, and agents can embed any article into a reply with a single keystroke. The "reduce customer queries by up to 30%" figure is a marketing claim; I found no public information on draft-and-publish workflow, versioning, review dates, multilingual articles, or deflection reporting I could take to a quarterly review. 7 8
The Agent Advocate
A searchable public help centre with categories, a custom domain and AI relevance search is real, and the single-keystroke shortcut for embedding an article into a reply is the kind of macro I actually want. I found no public information on article workflow, review dates, multilingual articles or reporting on which articles deflect — the 30% reduction claim is marketing, not a number a team can act on. 7 8
The Data Protection Officer
A searchable public help centre with categories and nested sub-categories, AI-assisted search, custom domains, a submit-a-ticket form, and agents able to embed any article into a reply with a single keystroke. We found no public information on draft and publish editorial states, multilingual articles, review dates for stale content, or reporting on which articles deflect — the reduction of queries by up to 30% appears as a marketing claim rather than a number the team can act on. 7 8
The Shop Operator
There is a real public help centre with categories and sub-categories, agents can embed any article into a reply with a single keystroke, and search scans for relevance beyond exact keywords. The "reduce customer queries by up to 30%" figure is a marketing claim, and we found no public information on draft-and-publish workflow, review dates, multilingual articles, or reporting on which articles deflect. Until deflection is a number the team can act on, this stays mid-scale for me. 7 8
The Integrator
A public help centre with categories, sub-categories, a custom domain and AI relevance search exists, agents can embed any article into a reply with a single keystroke, and the pages claim self-service cuts customer queries by up to 30%. We found no public information on draft and publish states, versioning, review dates for stale content, multilingual articles, or reporting on which articles deflect. 7 8
The Skeptic
The knowledge base is a real public help centre — categories with nested sub-categories, AI-assisted search beyond exact keywords, custom domains, and a $ shortcut that embeds any article into an agent reply — and the chat widget puts a bot before the human. We found no public information on draft and publish editorial states, multilingual articles, review dates that flag stale content, or reporting on which articles deflect; the claim of reducing customer queries "by up to 30%" is a promise with no number behind it a team could act on. 5 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, and what the vendor does with attachments — judged on what executes rather than what is promised.
0 — No retention policy stated, no deletion path, agents all see everything, and no DPA is published.
3 — A DPA on request and coarse roles; deletion is described as something the customer arranges, and there is no stated retention period.
5 — A signable DPA published, configurable agent roles and queue-level visibility, a stated retention period, and deletion of a requester's data that can actually be executed.
8 — Automatic retention rules per queue or data category, attachment handling stated, an audit log of who opened which ticket, documented support for access and erasure requests, and pseudonymisation or 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 erasure path is documented at a level I could hand straight to a DPO: a GDPR Article 17 request anonymises rather than deletes tickets, replaces subject and body with «REDACTED» including archived copies, deletes attachments, AI summaries and translations, masks order addresses, and pulls the tickets out of search — permanent, run in the background within minutes, gated to an admin login. Around it sit a processing addendum that applies automatically, controller and processor roles, delete-or-return on termination, once-a-year audit rights and 30 days' notice of subprocessor changes. I found no public information on an audit log of who opened which ticket or automatic retention rules — retention is "as long as necessary", with details only on request by email. 2 9 10
The Agent Advocate
The erasure execution is documented better than most: subjects and bodies replaced with «REDACTED» including archived copies, attachments and AI summaries deleted, order addresses masked, tickets removed from search results. Retention is only "as long as necessary" with details on request, subprocessor details come only by email rather than a published list, and I found no public information on an audit log of who opened which ticket. 9 10 2 12
The Data Protection Officer
Erasure is documented field by field — ticket subjects and bodies replaced with «REDACTED» including archived copies, order notes and free-text return reasons redacted, addresses masked, attachments and translation files deleted, tickets excluded from search — with duplicate-request protection, irreversibility and delete-or-return on termination stated, plus a DPA that applies automatically. The weak legs are retention, stated only as "as long as necessary" with details available on request, and oversight: we found no public information on an audit log of who opened which ticket, a published subprocessor list, or whether the vendor's own support can open a customer ticket. 2 9 10 12
The Shop Operator
Erasure actually executes and is documented in detail: ticket subject and body replaced with «REDACTED» including archived copies, addresses masked, attachments deleted, running in minutes behind an Admin login — more than a promise. A data processing addendum is published and applies automatically, with controller/processor roles and audit rights. The only stated retention rule is "as long as necessary" with details on request, we found no published list of service providers, configurable roles arrive only from the Professional plan upward, and we found no public information on an audit log of who opened which ticket. 2 9 10 12
The Integrator
Article 17 erasure is executable and documented to field level — subjects and bodies replaced with «REDACTED», addresses masked, attachments, translations and AI summaries deleted — and the DPA is published, applies automatically, with audit rights limited to once per twelve months. Retention is stated only as being as long as necessary with periods available on request, and we found no public information on per-queue retention rules or an audit log of who opened which ticket. 9 2 10 12
The Skeptic
The GDPR erasure path is documented to a level I rarely see and it runs: subject and body replaced with «REDACTED» including archived copies, addresses masked, order notes and return reasons redacted, attachments and AI artifacts deleted, and the customer's tickets dropped from search — plus a published DPA deemed to apply and custom roles and permissions. Retention, though, is stated only as "as long as necessary" with periods available by email on request, the service-provider list is likewise request-only, and we found no public information on an audit log of who opened which ticket. 2 9 10 12
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 — No API and no named integrations; context is copied in by hand.
3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.
5 — Named integrations for common CRM and shop systems, a documented REST API with keys, webhooks for the core ticket events, and SSO.
8 — Maintained bidirectional integrations, customer context from other systems shown inside the ticket, 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
The Shopify depth is what my team would actually use daily: order history, product details and shipping status inside every ticket, returns and cancellations processed without leaving the product, and a documented API with named read and write calls such as create thread, list orders and upload tracking information. But the captured pages give different figures for which plan unlocks the API — one says an Enterprise plan is required, another lists an advanced RESTful API under Professional — and I found no public information on webhooks, SSO, SCIM provisioning, documented rate limits or a sandbox; beyond the ecommerce stack the "300+ apps" line is a count I cannot check. 1 11 12
The Agent Advocate
Customer context from other systems really does show inside the ticket — Shopify order history, shipping status and previous conversations — and the API documents concrete calls like create thread and upload tracking information. I found no public information on webhooks, rate limits, single sign-on or SCIM provisioning, and the captured pages give different figures for which plan unlocks API access. 11 12 1
The Data Protection Officer
A deep, vendor-maintained Shopify integration shows order history and shipping status inside the ticket and processes returns and cancellations from within the product, alongside a documented REST API with named calls and a claimed 300+ connected apps. The captured pages give different statements about which plan includes API access — one lists an advanced API in the Professional plan, another says the Enterprise plan is required — and we found no public information on webhooks, rate limits, a sandbox or SSO. 1 11 12
The Shop Operator
The Shopify integration is the deep kind I need: every ticket carries complete order history and shipping status, agents process returns, cancellations and order adjustments in-ticket, and tracking details can be written back through API calls. We found no public information on webhooks, documented rate limits, single sign-on or SCIM provisioning. API access also sits behind a plan gate the captured pages name differently — one ties an advanced RESTful API to the Professional plan, another says the API requires the Enterprise plan. 1 11 12
The Integrator
Shopify, WooCommerce and Magento are named with real depth — order context shown inside the ticket, returns and order adjustments processed from the helpdesk — and the API documentation covers write calls like Create Message and Upload Tracking Information. Full API access requires the Enterprise plan, and we found no public information on webhooks, documented rate limits, SCIM provisioning, SSO, a sandbox, or any named CRM integration. 11 1 12
The Skeptic
The Shopify integration is the strongest thing here: every ticket shows complete order history and shipping status, and returns, cancellations and order adjustments are processed from inside eDesk, with a documented API covering create and list calls for threads, messages and orders plus a tracking upload. We found no public information on webhooks, SSO, SCIM provisioning, documented rate limits or a sandbox; and the captured pages give different figures for where the API begins — the Professional plan lists an "Advanced RESTful API" while the API help article says "You'll need to be on the eDesk Enterprise plan to access this feature." 1 11 12
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.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — support tooling, analytics, AI features — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, 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 Irish — xSellco Limited, Dublin — under Irish data-protection law, with processing stated for the United Kingdom and the European Economic Area and transfers outside those covered by adequacy decisions, standard contractual clauses or binding corporate rules. But the subprocessor list is not published — service-provider and retention details come by email on request — no data-centre provider is named, no certification is published, and since the end of June 2025 WhatsApp traffic passes through Meta. I found no public information on vendor support access to customer instances. 2 6 10
The Agent Advocate
The captured privacy pages name an Irish contracting entity and processing in the UK and the EEA, transfers out are covered by adequacy decisions or standard contractual clauses, and WhatsApp traffic is named as running through Meta. Subprocessor details are available only on request, I found no public information naming the data-centre provider or any certification, and the independently sourced attributes left jurisdiction, ownership and residency unconfirmed. 10 2 6
The Data Protection Officer
The vendor's own privacy page names an Irish contracting entity with Dublin offices and processing in the UK and the EEA, with transfers covered by adequacy decisions, standard contractual clauses or binding corporate rules. The subprocessor list is not published — details only on request by email — no data-centre provider is named, and WhatsApp messages have flowed through Meta Platforms since June 2025 with no specific safeguard stated for that leg. 2 6 10
The Shop Operator
A captured privacy page names an Irish contracting entity, xSellco Limited of Dublin, and states processing in the United Kingdom and the European Economic Area, with transfers outside those regions guarded by adequacy decisions, standard contractual clauses or binding corporate rules. We found no public information on the subprocessor list beyond 30 days' notice of additions, the data-centre provider, or ownership, and the WhatsApp channel runs through Meta as platform partner. The independently sourced sovereignty attributes returned unknown across the board, so I cannot place this higher. 2 6 10
The Integrator
The captured pages name an Irish contracting entity, xSellco Limited of Dublin, processing in the UK and the European Economic Area, with Stripe Payments Europe as payment processor and adequacy, contractual-clause or binding-rules safeguards for transfers. The service-provider list is available only by email request rather than published, WhatsApp connections run through the Meta platform partner, and we found no public information on a named data-centre provider or on vendor support access to customer data. 10 6 2
The Skeptic
The German privacy page names an Irish contracting entity, xSellco Limited of Dublin 4, and states processing in the UK and the European Economic Area, with 30 days' notice promised before any new third-party processor. Against that, the subprocessor list is available only by email on request, we found no public information on the data-centre provider, and WhatsApp traffic has run through Meta since June 2025 covered by generic adequacy or contractual-clause language; independent sovereignty sourcing could not confirm hosting, ownership or residency from the vendor's own captured pages. 2 6 10
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 per-agent headline exists, but the tier where the needed channel or SLA feature begins is unstated, or light-agent and contact limits are not mentioned.
5 — Per-agent prices public for the main tiers with billing period stated, but at least one commonly needed capability (telephony, messengers, SLA policies) sits in an unpriced bundle.
8 — Every tier and add-on priced publicly with per-agent maths, 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
One number is public — €39 per agent/ month on Essential, with a save-20%-annually toggle — but nothing for Growth or Professional, and "Custom" is a sales conversation, so I cannot price the tier where custom roles, ten stores or the API begin. Worse for computing a real invoice: the erasure documentation reveals that tickets "counted towards the monthly bill" continue to count, a metered dimension with no public rate, and I found no public information on VAT treatment, minimum term or channel add-on pricing. 1 9 11 12
The Agent Advocate
A single headline is public: €39 per agent/month for Essential with a 20% annual saving stated, plus a 14-day all-features trial. I found no public prices for Growth or Professional — the tiers where custom roles and the API begin — no public price for the Knowledge base add-on, and no VAT treatment, minimum term or ticket-count limits, so the real annual invoice can't be computed from the captured pages. 1 12 11 9 7
The Data Protection Officer
A per-agent price of €39 per agent/month is published with a stated 20% saving on annual billing, and a 14-day trial includes every feature. We found no public price for the Growth or Professional tiers where custom roles and the advanced API sit, and no statement of VAT treatment or minimum term, so the real annual invoice for anything beyond the entry tier is not computable from public pages. 1 12
The Shop Operator
Only the Essential plan carries a captured price — "€39 per agent/ month" with a stated 20% saving when billed annually — and we found no public prices for Growth, Professional or the custom tier, so a support lead cannot compute the annual invoice for their agent count. We found no public information on VAT treatment, minimum term, or light-agent and contact limits. The captured pages also give different plan names for where API access begins. 1 11 12
The Integrator
Only Essential carries a public figure — €39 per agent/ month with a 20% annual saving — while Growth and Professional are listed with feature detail but no price, and the captured pages give different names for the top plan (Custom on the pricing page, Enterprise on the API page). We found no public information on VAT treatment, minimum term or light-agent limits, so the annual invoice for a given agent count is not computable from public pages alone. 1 11 12
The Skeptic
One number is public and exact — €39 per agent/ month on Essential, with a 20% annual saving stated and a 14-day trial of every feature — and the store and marketplace allowance per tier is listed. But the Growth and Professional tiers carry no public price in the captured pages, the AI chatbot line carries an asterisk that is never resolved, we found no public information on light-agent terms or VAT treatment, and the captured pages give different figures for the plan where the API begins. A support lead can price the smallest configuration and nothing above it. 1 11 12
European sovereignty — proven facts
0 of 4 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 | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
Questions about eDesk
Is eDesk European?
Not determined: the vendor’s pages as captured do not say where eDesk is based.
Where does eDesk store data?
Not stated on the vendor’s pages as of 20 Oct 2026.
Does eDesk have a free plan?
Not stated on the vendor’s pages as of 20 Oct 2026.
What are the best alternatives to eDesk?
As of 21 Oct 2026, the panel rates Zendesk (3.5/5), Intercom (3.5/5) and HubSpot Service Hub (3/5) highest among the other 28 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). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: eDesk alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 20 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data residency, Subprocessors, Legal entity. Not confirmed on the vendor’s own pages as captured.
- 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.
- 15 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
- 4 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
- 2 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
- 1 pricing 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page edesk.com Checked 20 Oct 2026 Details →
- 2 Privacy policy — found from the homepage www.edesk.com Checked 20 Oct 2026 Details →
- 3 Ticketing, queues & SLA — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
- 4 Ticketing, queues & SLA — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
- 5 Channels in one queue — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
- 6 Channels in one queue — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
- 7 Knowledge base & deflection — found from sitemap www.edesk.com Checked 20 Oct 2026 Details →
- 8 Knowledge base & deflection — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
- 9 Customer data protection — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
- 10 Customer data protection — found from sitemap www.edesk.com Checked 20 Oct 2026 Details →
- 11 Integrations & API — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
- 12 Integrations & API — found from sitemap www.edesk.com Checked 20 Oct 2026 Details →