CRM
Zendesk Sell
Provenance unknown Report an errorPanel 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.
by Zendesk, Inc. · www.zendesk.com
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 panel's verdict
Zendesk Sell is listed as a CRM, but the captured pages market a customer-service suite — AI Agents, Copilot, ticket creation, knowledge base, voice — and that framing is the finding. The weakest band, 0–1, covers contact management, sales pipeline, integrations and data portability: we found no public information on contacts, companies, deal stages, deduplication, forecasting, an API, or export coverage. Automation is the strongest criterion at 1–3, built on the stated automation rate of up to 80% via AI Agents; judges weighed that claim differently, some crediting the vendor's central pitch, others capping it because it is framed around service interactions and no workflow builder, triggers, branching or routing is documented. Sovereignty runs 0–2: the pages name Zendesk, Inc., link a Trust Center and market extended data protection and security, while no hosting regions, data processing agreement or subprocessor list is on record. The only commercial term is a 14-day trial with no credit card required, and the Gartner "Leader" rating cited is for a CRM Customer Engagement Center report.
Speaks for it
- Automation holds the table's highest scores, 1–3, on a vendor-stated automation rate of up to 80% via AI Agents
- A 14-day trial requiring no credit card is stated plainly, the one commercial term a buyer can act on
- A Trust Center link and a marketed line on extended data protection and security are captured
- The pages cite a Gartner "Leader" rating for the 2025 CRM Customer Engagement Center Magic Quadrant
Held against it
- Contact management scored 0–1, with no public information on contacts, companies, deals, custom fields or deduplication
- Sales pipeline scored 0–1; the captured feature list is a service desk's, and reports and analytics appear only as an unelaborated bullet
- Integrations scored 0–1, with no public information on an API, webhooks or two-way email and calendar sync
- Data portability scored 0–1; we found no public information on import tooling, export coverage or data-return terms
- Sovereignty scored 0–2, with no sovereignty attributes on record and no public information on hosting regions, a data processing agreement or a subprocessor list
Best for
- Your priority is automated service interactions, where the captured evidence is strongest and automation scores 1–3
- You want to test before spending: the only commercial term on record is a 14-day trial requiring no credit card
Avoid if
- You must verify a contact, company and deal model before purchase; the core records scored 0–1
- Your finance team needs pipeline, forecast and quota reporting it can inspect in public documentation
- Your revenue stack depends on an API, webhooks or two-way email and calendar sync
- You need hosting regions, a data processing agreement and a subprocessor list in writing for European contact data
The scores
Contact & data model
Show reasoningHide reasoning
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.
The Solo Seller
We found no public information on the CRM data model — contacts, companies, deals, custom fields or dedupe; the captured page instead markets a service suite with tickets, a knowledge base and voice. For someone whose whole business lives in the contact list, that silence is the whole story. 1
The Data Protection Officer
The captured pages describe a customer-service platform — tickets, knowledge base, live chat, community forums — and we found no public information on contact or company records, deal objects, custom fields, required fields or duplicate handling. For a CRM evaluation the core data model is entirely unevidenced. 1
The Sales Ops Lead
We found no public information on contacts, companies, deals, custom fields or deduplication — the captured page markets a service suite (ticketing, live chat, knowledge base) and never touches the sales data model. With the core records wholly unevidenced, this is scored as not evidenced. 1
The RevOps Integrator
The captured page markets a service suite — AI Agents, ticketing, knowledge base, voice — and we found no public information on the contact and company model, deal objects, custom fields, or deduplication tooling. For a CRM that would be my system of record, silence on the records themselves is the deciding fact. 1
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
The Skeptic
The captured pages are a service-suite catalogue — AI Agents, Copilot, messaging, knowledge base, ticket creation, voice, workforce management — and we found no public information on contacts, companies, deals, custom fields, required fields or deduplication. A Gartner Leader rating for a CRM Customer Engagement Center report is a badge, not a data model. 1
Pipeline & forecasting
Show reasoningHide reasoning
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.
The Solo Seller
The capture points to reports and analytics and a Gartner rating for a customer engagement centre, but we found no public information on deal stages, stage requirements or forecasts for the CRM itself. I cannot judge a pipeline from a support-desk feature list. 1
The Data Protection Officer
Beyond a generic listing of reports and analytics, we found no public information on pipelines, deal stages, stage requirements, win/loss capture or forecasting. Nothing captured shows a pipeline that enforces a process or produces reporting a finance department would accept. 1
The Sales Ops Lead
Nothing in the capture speaks to pipelines, stage requirements, win/loss capture or forecasting; the feature list is a service desk's — ticket creation, workforce management, quality assurance — with reports and analytics as an unelaborated bullet. I found no public information on quota tracking or forecast reporting a finance department could accept. 1
The RevOps Integrator
Reports and analytics appear in the feature list, but everything shown is framed around service operations; we found no public information on pipelines, stage requirements, win/loss capture, or forecast views. Nothing captured evidences a pipeline that enforces a process or produces reporting a finance team would roll anything up from. 1
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
The Skeptic
We found no public information on pipelines, stages, stage requirements, forecasts, quota tracking or win/loss capture; the feature list names reports and analytics with no pipeline detail, and the Gartner placement is for a customer engagement centre report rather than sales tooling. Scored at the bottom for absence. 1
Automation & workflows
Show reasoningHide reasoning
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.
The Solo Seller
The page claims AI Agents and an automation rate of up to 80%, but that is framed around service interactions; we found no public information on workflow builders, sequences or lead routing for the CRM. A marketing percentage is not something I can set up in an afternoon. 1
The Data Protection Officer
The only automation evidence is a homepage claim of an automation rate of up to 80 per cent via AI agents that learn from each interaction and handle more complex workflows. We found no public information on triggers, branching, delays, sequences or routing limits, so the figure is marketing rather than documented capability. 1
The Sales Ops Lead
The vendor publicly claims an automation rate of up to 80 percent via AI Agents that learn from every interaction and handle more complex workflows, so real automation machinery clearly exists. But we found no public information on workflow triggers, multi-step sequences, branching or lead routing — the mechanics my team would configure are unevidenced, which caps this at simple automation. 1
The RevOps Integrator
The one automation signal is a headline claim of an automation rate of up to 80 percent from AI Agents that learn from every interaction and handle more complex workflows. We found no public information on a workflow builder, triggers, sequences, routing, or webhooks as steps, so this reads as service-AI marketing rather than designed automation a revenue team can build on. 1
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
The Skeptic
The one automation fact is a headline rate — an automation rate of up to 80% via AI Agents that learn from every interaction and handle more complex workflows — attached to service resolution, and we found no public information on a workflow builder, triggers, branching, delays, routing or tier limits on automation. An "up to" percentage on a marketing page is the cheapest automation claim there is, and it is the only one on offer here. 1
Integrations & API
Show reasoningHide reasoning
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.
The Solo Seller
We found no public information on two-way email or calendar sync, native connections, or an API in the captured material. Without that, I have no way to tell whether my inbox history would even flow in. 1
The Data Protection Officer
Messaging, voice and live chat are native product channels rather than third-party connections, and we found no public information on two-way email and calendar sync, a native integration directory, or a public API. Evidence of data flowing in or out through any documented interface is absent. 1
The Sales Ops Lead
We found no public information on an API, two-way email and calendar sync, or native connectors to the revenue stack. The messaging, live chat and voice items on the feature list are product channels, not integrations. 1
The RevOps Integrator
This is the first thing I look for, and we found no public information on a public API, webhooks, OAuth apps, a marketplace, or two-way email and calendar sync. The native channels listed — messaging, live chat, voice — describe where conversations arrive, not how the product connects to the systems money already flows through. 1
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
The Skeptic
We found no public information on two-way email or calendar sync, native connections to the revenue stack, webhooks, OAuth apps, an API or a marketplace. The channels named — messaging, live chat, voice — are the product's own surfaces, which is not evidence of connections outward. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
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.
The Solo Seller
The capture names a US-incorporated vendor and points to a trust centre whose contents we could not verify; we found no public information on EU hosting, a data processing agreement or a subprocessor list. For European contact data that is an open question, not a resolved one. 1
The Data Protection Officer
The copyright names Zendesk, Inc., a US corporate form, and we found no public information on hosting regions, an EU processing option, a published data processing agreement or a subprocessor list — for a system claiming 830 million AI interactions, whose law governs that personal data is the first unanswered question. The only positives captured are a link labeled Trust Center and advanced data privacy and security as a marketing bullet. 1
The Sales Ops Lead
The entity on record is Zendesk, Inc., and the capture points to a Trust Center and an advanced data protection and security claim — that is the entire privacy posture. We found no public information on hosting locations, a DPA, or a subprocessor list, and the sovereignty record itself is empty. 1
The RevOps Integrator
The copyright names Zendesk, Inc., a Trust Center is linked, and advanced data protection and security is marketed, but the captured pages do not show a DPA, subprocessor list, EU hosting option, or retention and deletion controls. We found no public information on where personal data is processed or under whose law, and the sovereignty attributes on record are empty. 1
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
The Skeptic
No sovereignty attributes are on record; the only entity named is Zendesk, Inc., and while a trust center is referenced, the captured pages give no hosting location, DPA, subprocessor list, EU-region option or retention and deletion controls. A trust center with nothing captured behind it is a door, not a disclosure, and this scores at the bottom of the scale. 1
Import, export & exit
Show reasoningHide reasoning
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.
The Solo Seller
We found no public information on import tooling or export coverage — nothing on files, activity history or formats. Before I move my database in, exit terms staying invisible is a real cost. 1
The Data Protection Officer
We found no public information on import tooling, export scope or formats, migration paths, or contractual data-return terms. Nothing captured addresses moving data in or, more importantly for a data-protection buyer, out with history intact. 1
The Sales Ops Lead
We found no public information on import, export, migration tooling, API access for extraction or contractual data-return terms. The capture offers scale numbers — 830 million AI interactions, 4.8 billion resolutions — but nothing on getting data in or out. 1
The RevOps Integrator
We found no public information on import tooling, export scope, migration support, or contractual data-return terms. For a buyer weighing exit, the captured page gives me nothing to evaluate in either direction. 1
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
The Skeptic
We found no public information on import (guided or otherwise), export coverage for history, activities and files, or API terms for rebuilding the database elsewhere. The only onboarding-adjacent fact is a 14-day trial with no credit card required, which says nothing about getting data out. 1
Pricing transparency
Show reasoningHide reasoning
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.
The Solo Seller
The only buying term on the page is a 14-day trial with no credit card required; we found no public prices, tiers or per-seat rates. Paying with my own card, I cannot begin to compute an invoice from what is published here. 1
The Data Protection Officer
No price figures were captured — no per-seat numbers, no billing-period or VAT treatment — and we found no public information on tiers, seat minimums or add-ons. The one purchase-related fact is stated clearly, a 14-day trial requiring no credit card, which earns a point of self-serve clarity but computes no invoice. 1
The Sales Ops Lead
The only public commercial term is a 14-day free trial with no credit card required; we found no public prices, tier structure, billing periods or VAT treatment anywhere in the capture. A buyer cannot compute any invoice, at three seats or thirty, from what is published. 1
The RevOps Integrator
The only commercial term captured is a 14-day free trial with no credit card required; we found no public prices, tier definitions, billing periods, or seat minimums. A buyer cannot begin to compute an invoice from what is on the record. 1
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
The Skeptic
The captured pages show no tier names, prices, billing periods, seat minimums or VAT treatment — the only pricing-adjacent fact is a 14-day trial with no credit card — so a real invoice at any seat count cannot be computed from the public information in evidence. Free trials are how vendors get you in; they are not how buyers compute renewal maths. 1
European sovereignty — proven facts
2 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 | 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
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 →