Intercom vs Zendesk

Intercom

There's a real engine here — shared inbox with tickets, multiple team inboxes, a workflows automation builder and round-robin assignment — but SLAs appear only as a feature label on the top tier, with nothing on timers, breach warnings, escalation chains or per-agent resolution reporting. "AI-powered ticketing" is a marketing claim I can't check against the queue. That puts it at the rules-based-routing anchor and not a step above.

Zendesk

Ticket distribution, automations/triggers and skill-based routing are named, so routing is beyond manual. But nothing in the evidence evidences SLA timers, breach warnings, escalation chains or search behaviour — the exact machinery I run my SLA on — so it sits between the anchors.

Intercom

The channel list is genuinely broad — live chat, support email and in-app chats free and unlimited, phone, WhatsApp and SMS as pay-as-you-go, plus Slack — all claimed under one "omnichannel inbox". But the evidence never evidences that a customer's history follows them across channels, there's no customer portal where a requester sees their own tickets, and WhatsApp consent handling isn't stated. Breadth of an 8, proof of a 5.

Zendesk

Email, messaging/live chat, telephony, a customer portal and community forums are all named with 'Omnichannel-Verteilung' as a stated feature, which covers the one-queue claim. What's missing is the fine print: no messenger consent handling, no call logging, and no explicit statement that one history follows the customer across channels.

Intercom

Deflection is the heart of this product: a public help centre, multilingual and multibrand help centres, a Knowledge Hub feeding Fin and agents, and a reported resolution rate averaging 76% across 12,000+ customers — that's deflection stated as a number my team could act on. What's missing is the management layer: no editorial workflow, no review dates flagging stale content, no article-level deflection reporting or gap analysis from unanswered tickets.

Zendesk

A hosted Guide help centre demonstrably exists and Enterprise names 'Automatische Hilfe', so there is a public KB with hints of suggestions. But editorial workflow, versioning, stale-flagging and deflection reporting are nowhere in the evidence, and the '80% automation rate' is a homepage claim, not a number I could act on.

Intercom

The legal scaffolding exists — DPA offered, subprocessor list published, DPO appointed, a full set of data-subject rights including deletion — but nothing executes at the ticket level: no stated retention period for the archive, no agent roles or queue-level visibility, no audit log, no attachment or redaction handling. And the policy says generative AI "may" process personal information with no detail on which content or what safeguard, which I would need answered before letting it near my queue.

Zendesk

This is genuinely solid: manual and automatic redaction including credit cards in logs and database entries, a deletion policy, subject-rights tools for access and erasure, and a published subprocessor list. I knock it back from 8 because the compliance-grade pieces — configurable retention, masking, access logs — sit in a paid add-on, and audit logs only arrive at Enterprise plans.

Intercom

Three named integrations (Slack, Shopify, Github), Salesforce only through Fin, SSO gated to the top tier, and an API plus MCP asserted through Fin's "takes action" claims — but the evidence shows no documented REST API, no webhooks, no rate limits, no SCIM, no sandbox. That's a handful of integrations and an API I can't build against on paper.

Zendesk

An API exists (the Support API is an audit-log source) and an 'App Builder' is named at Professional, but the evidence names not a single CRM, shop or identity integration and says nothing about webhooks, rate limits or API documentation. For a helpdesk that has to reach the order system, that's a marketing line, not evidence.

Intercom

The service is "provided and hosted in the United States" by a Delaware corporation, with transfers out to Ireland, the UK and Australia under SCCs and the EU-US DPF — legal cover, not sovereignty. A published subprocessor list is the only mitigation keeping this off a flat zero; there is no EU hosting option or EU contracting entity in evidence anywhere on the evidence.

Zendesk

The contracting entity is Zendesk, Inc. — US — while EEA hosting is offered as an option on AWS and the subprocessor list with names and locations is published, which is exactly the anchor-3 pattern with some transparency credit. No EU contracting entity, nothing on vendor support access to instances, and no self-hosted path, so it cannot climb the ladder.

Intercom

$19 per seat/month plus $0.99 per Fin outcome is public, the billing toggle is stated, free allowances and spending limits are numerated, and 20-50 free Lite seats are named — better than most. But I still can't compute my annual invoice: SLAs sit in the Expert tier with no price shown, "From $0.99" means outcome costs vary, and phone, WhatsApp and SMS are pay-as-you-go with no per-unit rates, VAT treatment or term stated anywhere.

Zendesk

I can compute most of my invoice: three tiers priced per agent per month with annual billing stated, plus priced add-ons for Contact Center, Copilot and workforce. It loses points because the top tier is 'contact sales', VAT treatment and minimum terms are unstated, and there's no light-agent pricing — and notably the tier where audit logs live is the unpriced one.