Intercom vs Zendesk

Intercom

Real tickets in a shared inbox with multiple team inboxes, a Workflows automation builder and round-robin assignment, and SLAs exist — but SLAs only appear at the top Expert tier, and nothing here shows merge/split, macros, or search that would let an agent find a half-remembered 'parcel' ticket among ten thousand. 'Pre-built reports' is a bullet, not first-response and resolution time by agent and queue.

Zendesk

Triggers, automations, skills-based distribution, prewritten replies and approval workflows are confirmed from the plan listings — routing is clearly beyond manual. But nowhere does the evidence evidence an SLA timer, breach warning, full-text search, priorities or ticket merge/split, and those are the clock and the finder I run a ten-thousand-ticket December queue on.

Intercom

Live chat, support email and in-app land free in one claimed 'omnichannel inbox', and WhatsApp, SMS and Phone are all there — but the metered pay-as-you-go ones, and the evidence never shows call logging, WhatsApp consent handling or a customer portal where a requester sees their own tickets, which is the line between channel logos and one queue with one history. Whether a customer switching from WhatsApp to email keeps their history is simply not evidenced.

Zendesk

Suite Team puts omnichannel routing, messaging, live chat and telephony in one plan, the Contact Center pitch is a unified voice+digital platform, and a customer portal is in the feature list — solidly above the three-channel anchor. But no messenger is ever named — WhatsApp appears nowhere — and consent handling and the one-conversation-one-history claim are not evidenced, which is exactly the test I judge by.

Intercom

Public and private multilingual Help Center plus a Knowledge Hub, and deflection is reported as a real number — Fin averaging 76% resolution across 12,000+ customers — which is exactly the December metric I judge deflection by. What's missing: editorial workflow, review dates flagging stale content, and reporting on which articles deflect rather than the AI agent.

Zendesk

A public Guide help centre is confirmed (free TLS on custom domains) and the AI agents claim up to 80% automation with Vimeo at 30–40% — a deflection number of sorts. What's missing is the article side: no editorial workflow, versioning, multilingual support or stale-content flags, and nothing ties a deflected ticket to the article that deflected it.

Intercom

The privacy policy is genuinely solid — DPA offered, DPO appointed, subprocessor list published, full subject rights including deletion and portability — but that's paper, not plumbing. No stated retention period for the ticket archive, no configurable agent roles or queue-level visibility, no audit log of who opened which ticket, nothing on attachments.

Zendesk

This executes rather than promises: manual and automatic redaction (ticket comments, credit-card numbers, secure attachment deletion), privacy tools covering access, erasure, portability and objection, a service-data deletion policy, published subprocessor list and audit logs. The sting is that configurable retention, masking and access logs sit in a paid add-on and audit logs behind Enterprise, so the protection is tier-gated rather than standard.

Intercom

Shopify, Slack and Salesforce are named, and Fin 'pulls in customer data and takes action through APIs or MCP' — order context in front of the agent is the right direction — plus SSO at Expert tier. But there's no evidence of webhooks, documented rate limits, SCIM or a sandbox, and no proof shop order data renders inside the ticket for the human agent rather than only through the AI.

Zendesk

There is a developer portal, an App Builder and a sandbox, plus SAML/OIDC SSO — real building blocks. But not a single integration is named: no CRM, no shop system, no webhooks, no rate limits, and my test — the order sitting next to the ticket without a second login — is covered only by a generic 'Kundenkontext' line.

Intercom

The ticket archive is 'provided and hosted in the United States' by Intercom, Inc., a Delaware corporation, and no EU hosting option appears anywhere on the evidence at any tier — I can't buy EU residency at all. SCCs, the EU-US Data Privacy Framework and a published subprocessor list keep it a hair above the floor, but only just.

Zendesk

The contracting entity is Zendesk, Inc. of San Francisco and EEA hosting is merely one option among US, AU and JP — which lands precisely on the anchor for a non-EU entity with EU hosting as an option. The published subprocessor list with names and locations is the only mitigation; no DACH hosting and no sovereign or self-hosted path.

Intercom

$19 per seat/mo, an annual/monthly toggle, $0.99 per Fin outcome with spending limits, and a $99/mo Pro add-on are public — good start. But SLAs sit in the Expert tier whose price the evidence never states, WhatsApp, SMS and Phone are 'pay-as-you-go' with no quoted rates, and there's no VAT treatment or minimum term, so my real annual invoice for 20 agents with WhatsApp and phone is not computable.

Zendesk

Four per-agent prices are public with annual billing stated, and the Contact Center, Copilot and Workforce add-ons carry real numbers (€82/€50/€50), so most of the invoice is computable. But Suite Enterprise — where custom roles, sandbox and the advanced security features begin — is 'Vertrieb kontaktieren', and VAT treatment, minimum terms and any monthly alternative are nowhere on the page.