CRM

Zendesk Sell

Provenance unknown Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 4 dimensions proven

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

An AI-assisted analysis of public evidence — not a hands-on test.

Every score, rationale and verdict on this page is AI-generated. Every claim cites the source it was read from. Nothing here is a human star review — and no score can be bought. How scores are made →

Method and versions

The Solo Seller v1.2 · The Data Protection Officer v1.0 · The Sales Ops Lead v1.0 · The RevOps Integrator v1.0 · The Migrator v1.1 · The Skeptic v1.2 · rubric v1 · evaluated 29 Sep 2026

Report an error on this page Is this your product? →

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

The Migrator

Weighted verdict

Has moved a company off a CRM twice and remembers every scar. Optimizes for clean import with dedupe, full export of every object including notes and activity history, and contract terms that permit leaving. Rejects export behind support tickets and per-record API metering that makes exit a project.

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

Scored by The Migrator

Contact & data model

How this is scored

Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.

0 — A flat address book; no relations between people, companies and deals.

3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.

5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.

8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.

10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.

Report an error

The Migrator

The captured page is a service-suite pitch listing AI agents, tickets and a knowledge base, and we found no public information on contacts, companies, deals, custom fields or deduplication — the exact records and hygiene a clean import depends on. With nothing evidenced on the core data model, the absence itself is the score. 1

Report an error

Pipeline & forecasting

How this is scored

Whether the pipeline enforces a process and produces reporting a finance department accepts.

0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.

3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.

5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.

8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.

10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.

Report an error

The Migrator

The only reporting signal is a generic reports-and-analytics bullet aimed at service teams; we found no public information on deal stages, stage requirements, win/loss capture, quotas or forecast views. A finance department cannot be asked to accept a pipeline nobody will show. 1

Report an error

Automation & workflows

How this is scored

Triggers, sequences and routing that remove manual work without a consultant.

0 — No automation beyond email templates.

3 — Simple if-this-then-that on records; no multi-step sequences, no branching.

5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.

8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.

10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.

Report an error

The Migrator

Automation is central to the vendor's own pitch — up to 80 percent automation rate with AI Agents and Copilot that learn from interactions and handle more complex workflows — so named automation exists. We found no public information on multi-step sequences, branching, routing or workflow limits for sales records, which caps this at simple-trigger territory. 1

Report an error

Integrations & API

How this is scored

Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.

0 — No API, no sync; data enters by CSV and leaves never.

3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.

5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.

8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.

10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.

Report an error

The Migrator

The feature list covers messaging, live chat and voice — channels, not connections — and we found no public information on an API, two-way email and calendar sync, webhooks, OAuth apps or a native directory. Without an evidenced API I cannot treat external systems as first-class. 1

Report an error

European sovereignty

How this is scored

Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.

0 — US entity, US-default hosting, no public DPA or subprocessor list.

3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.

5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.

8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.

10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.

Report an error

The Migrator

The legal entity is Zendesk, Inc. and a Trust Center link exists alongside a marketing line on extended privacy and security, but we found no public information on hosting regions, a DPA, a subprocessor list or EU processing. For other people's personal data, a trust-center link with nothing behind it on record is not something a DPO can sign. 1

Report an error

Import, export & exit

How this is scored

Getting in with history intact, and out with everything — the anti-lock-in criterion.

0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.

3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.

5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.

8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.

10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.

Report an error

The Migrator

We found no public information on import tooling, dedupe on entry, export of notes and activity history, or any API metering that would price an exit — every fact that decides whether leaving is a weekend or a project. The 14-day trial with no credit card is friendly to arriving, but the exit door is entirely unevidenced. 1

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone.

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

3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.

5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.

8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.

10 — Complete price computability: every tier, add-on, usage meter and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.

Report an error

The Migrator

The only pricing-adjacent fact on record is a 14-day trial requiring no credit card; we found no public prices for any tier, no billing-period split, no seat maths and no add-on pricing. A buyer cannot compute even a first invoice, let alone a renewal, from what is published. 1

Report an error

European sovereignty — proven facts

2 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.

Legal entity	Incorporated in DE ⚠ unverified	3/3 pts	2 Report an error
Ownership	Not determined	—	uncited Report an error
Data residency	Not determined ⚠ unverified	—	uncited Report an error
Subprocessors	US CLOUD Act reach ⚠ unverified	0/2 pts	3 Report an error

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 — Legal entity. Zendesk GmbH is the German subsidiary; the same page's footer shows "© 2026 Zendesk, Inc.", indicating the US parent, which may be the contracting entity for the service.
Weak sourcing — Data residency. Not confirmed on the vendor’s own pages as captured.
Weak sourcing — Subprocessors. AWS is US-headquartered regardless of server region, and the trust center also names US provider Cloudflare for edge/DDoS protection; the full subprocessor list is not shown in these excerpts.
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.

24 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 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
6 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
2 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
2 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
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
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
6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us

Do you know more about Zendesk Sell? Tell us Report an error on this page

Sources (9)

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

1 Vendor page www.zendesk.com Checked 29 Sep 2026 Details →
2 Imprint — found from the homepage www.zendesk.de Checked 30 Sep 2026 Details →
3 Security / trust page — found from the homepage www.zendesk.de Checked 30 Sep 2026 Details →
4 Contact & data model — found from sitemap www.zendesk.com Checked 1 Oct 2026 Details →
5 Contact & data model — found from sitemap www.zendesk.com Checked 1 Oct 2026 Details →
6 Pipeline & forecasting — found from sitemap www.zendesk.com Checked 1 Oct 2026 Details →
7 Pipeline & forecasting — found from sitemap www.zendesk.com Checked 1 Oct 2026 Details →
8 Automation & workflows — found from sitemap www.zendesk.com Checked 1 Oct 2026 Details →
9 Automation & workflows — found from sitemap www.zendesk.com Checked 1 Oct 2026 Details →