Intercom vs Zendesk

Intercom

Multiple team inboxes with a workflows automation builder and round-robin assignment is a real routing engine, not manual triage, which clears the 5-anchor bar. But the evidence is silent on search, macros, priorities, escalation chains and merge/split, and SLAs only surface as a named feature in the top Expert tier — I can't credit the 8-anchor gear from a feature list, and I judge by the hundredth ticket, not the demo.

Zendesk

The engine bones are there at the entry tier — ticket distribution, triggers and automations, vorformulierte Antworten (that's macros) — and skills-based distribution shows up at Professional. But the evidence says not one word about SLA timers, breach warnings, escalation chains, merge/split, or search; after six years, if I can't pull the half-remembered thread out of ten thousand, the rest is decoration.

Intercom

Live chat, support email, in-app chat, SMS, WhatsApp, phone (metered) and Slack are all evidenced, with an 'omnichannel inbox' claim that at least nods at one screen instead of four tabs. Missing for 8: no customer portal where a requester sees their own tickets, no WhatsApp consent handling stated, and no call-logging detail — and the phone channel I'd actually need is pay-as-you-go.

Zendesk

Telefonie, Messaging/Live-Chat, a Kundenportal and 'Omnichannel-Verteilung' are all bundled at Suite Team, and the Contact Center pitch promises voice and digital in one platform 'ohne Middleware'. Missing is the fine print that separates the anchors: no call-logging statement, no consent handling for messengers, and 'one history across channels' is homepage wording, not evidence.

Intercom

A public help center on every plan, private/multilingual up a tier, a Knowledge Hub, and Copilot/Fin answering from it means suggestions reach both agent and customer in some form. No editorial workflow, versioning, review dates or in-product deflection reporting is evidenced; the '76% resolution rate' is a vendor marketing stat, not a number my team could act on.

Zendesk

There's a real help-centre product — Guide with custom domains and automatic TLS — plus Wissensdatenbank at Team tier and 'KI Automatische Hilfe' at Enterprise, which smells like suggestion-before-submit. But nothing on editorial workflow, draft/publish, multilingual or which articles actually deflect; the '80% Automatisierungsrate' on the homepage is a boast, not a deflection number I can act on.

Intercom

A published DPA, subprocessor list, DPO and a full rights list including deletion put it above the floor. But there is no stated retention period for the ticket archive (the 14 days is form prefill, not tickets), and nothing on configurable roles, an audit log of who opened which ticket, attachment handling or redaction — that sits below the 5 anchor.

Zendesk

This is where the evidence is dense: manual redaction of ticket comments and secure attachment deletion, automatic credit-card stripping down to logs and database entries, documented subject-rights tooling for access through deletion, and a published subprocessor list. It loses ground because the strong parts are paywalled — configurable retention, masking and access logs sit in a paid add-on, audit logs are Enterprise-only — so the default tenant gets less than the brochure implies.

Intercom

Salesforce and Shopify are named, SSO & identity management exists at the top tier, and 'APIs or MCP' with Fin taking action on external systems is enough for read-and-write context. But webhooks, documented rate limits, SCIM, a sandbox and actual API documentation are all unevidenced — one homepage sentence is not an API.

Zendesk

APIs and a developer area exist, there's an App Builder and an Enterprise sandbox, and SAML/OIDC SSO is confirmed — but the evidence never names a single integration, no CRM, no shop, and is silent on webhooks, rate limits and SCIM. 'Integrieren Sie Ihre bevorzugten Tools' is a logo wall, not a stack.

Intercom

The service is 'provided and hosted in the United States' by a Delaware corporation, with transfers to Ireland, the UK and Australia under SCCs/DPF, and no EU residency option anywhere in the evidence. The published subprocessor list keeps it off the 0 floor, but the ticket archive sits in the US under a US entity for this buyer — a 2.

Zendesk

The contracting entity is Zendesk, Inc. of San Francisco, and EEA hosting is one of four region options rather than the default — the classic 'EU hosting as an option, US entity on the contract' shape. The published subprocessor list with names and locations is honest of them, but as a buyer my ticket archive's home depends on an option I have to remember to tick.

Intercom

A public $19/seat + $0.99/outcome model with an annual/monthly toggle and spending limits is computable for the core, and allowances (10 Copilot conversations/agent/mo) are stated. But the channels I'd need metered — phone, WhatsApp, SMS — are 'pay-as-you-go' with no unit rates, everything else is 'from'-priced, and VAT and minimum term are unstated, so I cannot produce the real annual invoice from public pages alone.

Zendesk

Largely computable: 19/55/115 € per agent per month with the billing period stated, and the add-ons a support lead actually prices — Contact Center at 82 €, Copilot at 50 € — carry public numbers. It stops short of full transparency because the top tier is 'Vertrieb kontaktieren' and neither VAT treatment nor minimum term appears anywhere on the evidence.