whats-best.ai

Customer Service & Helpdesk

eDesk

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–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

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

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

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

eDesk alternatives, European ones first →

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

The Skeptic

Weighted verdict

Counts the channel logos on the marketing page, then asks which of them share one queue and one history. Reads for the tier where SLA policies begin, what a "light agent" may actually do, and whether the AI summariser is included or metered.

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

Scored by The Skeptic

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

Ticketing, queues & SLA

How this is scored

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

0 — 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.

Report an error

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

Report an error

Channels in one queue

How this is scored

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

0 — 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.

Report an error

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

Report an error

Knowledge base & deflection

How this is scored

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

0 — No knowledge base; 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.

Report an error

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

Report an error

Customer data protection

How this is scored

A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights, 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.

Report an error

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

Report an error

Integrations & API

How this is scored

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

0 — 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.

Report an error

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

Report an error

European sovereignty

How this is scored

Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it.

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.

Report an error

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

Report an error

Pricing transparency

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.

Report an error

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

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

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

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

What we left out

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

Sources (12)

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

  1. 1 Vendor page edesk.com Checked 20 Oct 2026 Details →
  2. 2 Privacy policy — found from the homepage www.edesk.com Checked 20 Oct 2026 Details →
  3. 3 Ticketing, queues & SLA — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
  4. 4 Ticketing, queues & SLA — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
  5. 5 Channels in one queue — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
  6. 6 Channels in one queue — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
  7. 7 Knowledge base & deflection — found from sitemap www.edesk.com Checked 20 Oct 2026 Details →
  8. 8 Knowledge base & deflection — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
  9. 9 Customer data protection — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
  10. 10 Customer data protection — found from sitemap www.edesk.com Checked 20 Oct 2026 Details →
  11. 11 Integrations & API — found from sitemap support.edesk.com Checked 20 Oct 2026 Details →
  12. 12 Integrations & API — found from sitemap www.edesk.com Checked 20 Oct 2026 Details →