Intercom
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Intercom, Inc. · www.intercom.com
Compare with Zendesk → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Intercom at a glance
- Vendor
- Intercom, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Outside the EU by default source, captured 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Intercom 3.5/5, the mean of 6 judges. Intercom is a customer service and helpdesk platform whose scores are strongest on omnichannel (8 to 9) and knowledge and self-service (a flat 8), and weakest on sovereignty (4 to 5). how scores are made
- As of
- Vendor pages captured 11 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Intercom is a customer service and helpdesk platform whose scores are strongest on omnichannel (8 to 9) and knowledge and self-service (a flat 8), and weakest on sovereignty (4 to 5). Judges credit nine channels — email, phone, SMS, Messenger, Slack, WhatsApp, Instagram, Facebook and Discord — landing in one inbox on one customer record, plus deflection machinery: suggested articles before search, search that can be required before contact, a help centre in 45 languages, and an articles report naming what customers searched for and could not find. The genuine split is customer data protection (0 to 7): five scores fall between 5 and 7 on the strength of a published DPA with the 2021 SCCs and irreversible before-save redaction, while the agent advocate scored 0 because the terms grant Intercom use of Customer Data including for Intercom AI model training. Ticketing core (6 to 7) is a real routing engine, but SLAs appear only on the Expert plan; pricing transparency (7 to 8) loses points where the captured pages give different figures for the bundled seat price.
Speaks for it
- Nine channels — email, phone, SMS, Messenger, Slack, WhatsApp, Instagram, Facebook and Discord — connect from a single workspace, with the customer's history visible across every channel and a documented messaging-to-call transition that preserves context and history.
- Deflection is built in: suggested articles before customers search, an option to require help-centre search before a conversation starts, help centres in 45 languages, and an articles report that names the topics customers searched for but did not find.
- The GDPR DPA incorporating the 2021 SCCs is folded into the terms with no separate signature, alongside export and permanent deletion of an individual's data and irreversible before-save redaction with built-in card and social-security rules.
- All three plans carry public per-seat prices — Essential $29, Advanced $99, Expert $139 per seat/month — with annual and monthly billing, stated free Lite seat counts, and a cost calculator keyed to team size and expected Fin outcomes.
- Ticketing core includes three ticket categories with forms, a workflows automation builder, round-robin assignment, and per-teammate ticket limits honoured by balanced assignment logic.
Held against it
- The terms grant Intercom use of Customer Data to provide and improve the services, including for Intercom AI model training.
- The privacy policy states the services are provided and hosted in the United States, the EU region appears only in a subprocessor row and a Regional Data Hosting Addendum, and no self-hosted option is offered.
- Service level agreements appear only as a feature of the top Expert plan, with no public information found on business-hours SLA policies, breach warnings or escalation.
- Phone, SMS and WhatsApp are pay-as-you-go with no unit rates on the captured pages, and the captured pages give different figures for the seat-plus-outcome bundle ($19 and $29 per seat/mo + $0.99 per outcome).
- Connectors can only be fully tested in production rather than test workspaces, and the terms merely reserve a right to place API call limits rather than documenting any.
Best for
- You support customers across many channels and want one inbox on one customer record — omnichannel scores run 8 to 9 across nine documented channels.
- You want to deflect volume before contact — knowledge and self-service scored a flat 8, with suggested articles, a required-search option, and Fin reported at an average resolution rate of 76%.
- You need predictable software pricing up front — all three tiers publish per-seat prices, and a 14-day free trial is offered with no credit card required.
- You run a Shopify storefront and want order data inside support answers — Fin pulls Shopify, Salesforce and HubSpot data and can execute write actions such as processing refunds.
Avoid if
- Your data processing terms cannot accept vendor use of customer data for AI model training — Intercom's terms grant that use of Customer Data, the clause behind the 0 on customer data protection.
- You require EU hosting by default or a self-hosted deployment — the services are stated as provided and hosted in the United States, the EU region surfaces only in a subprocessor row and a hosting addendum, and no self-hosted option is offered.
- You need SLA enforcement below the top tier — SLAs are listed only on the Expert plan.
- Your spend is dominated by phone, SMS or WhatsApp — those channels are pay-as-you-go, and the metered part of the invoice stays uncomputable from public pages.
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 3 of 5 |
| Channels in one queue | 4 of 5 |
| Knowledge base & deflection | 4 of 5 |
| Customer data protection | 3 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 3.5 of 5 |
Ticketing, queues & SLA
Show reasoningHide reasoning
How this is scored
The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.
0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.
3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.
5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.
8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.
10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.
The Support Lead
Ticket types with their own data fields, three ticket categories, a workflows automation builder and round-robin plus balanced assignment that honours per-teammate ticket limits give me genuine routing, and there is a teammate table with filtering, bulk updates and export. But service level agreements appear only as a named feature of the top plan — I found no public information on per-queue SLA policies, breach warnings, escalation, or first-response and resolution reporting by agent and queue, nor on macros, ticket merge or search across tickets. A strong queue engine whose SLA machinery I could not verify. 6 7 2
The Agent Advocate
Three ticket types with forms and one-click conversion, team inboxes, a workflows automation builder and round-robin assignment are documented, and per-teammate assignment limits with least-assigned-first balancing is genuine load control. But we found no public information on macros, merge and split, business-hours SLA policies with escalation, or first-response and resolution reporting by agent and queue; service level agreements appear only as a named feature of the top plan, and nothing documents search that finds the old ticket from a half-remembered phrase. 6 7 2
The Data Protection Officer
Three ticket categories with definable ticket types and forms, an automation builder and round-robin routing into multiple team inboxes, and per-teammate ticket assignment limits following balanced assignment logic show a workload engine rather than a tracker, and service level agreements are listed at the top tier. We found no public information on business-hours SLA policies with breach warnings and escalation, ticket merge or split, or first-response and resolution reporting by agent and queue. 6 7 2 2
The Shop Operator
Ticketing is real and volume-ready: three ticket categories with their own forms and data fields, one-click conversation-to-ticket conversion, workflow automation, round robin, and per-teammate assignment limits with balanced distribution logic. SLAs appear only as a feature of the top Expert plan, and I found no public information on breach warnings, escalation paths, or first-response and resolution reporting per agent. 6 7 2 1
The Integrator
Three ticket categories with typed fields, ticket forms and one-click conversation-to-ticket conversion give the engine real structure, and balanced assignment with separate per-teammate ticket and conversation limits, round-robin routing and a workflow automation builder take it beyond a shared inbox. Service level agreements appear only as a feature of the top Expert plan, and I found no public information on business-hours SLA policies, breach warnings, escalation, or merge and split. 6 7 2
The Skeptic
Three documented ticket types with forms, statuses cross-posted to the customer conversation, a Workflows automation builder with round-robin assignment, and per-teammate ticket assignment limits governed by balanced logic (least assigned, then last assignment date) — real workload management in places. But service level agreements appear only as a bullet on the top Expert plan, with no stated business hours, breach warnings or escalation. We found no public information on macros, ticket merge or split, or search across tickets. 6 7 2 2
Channels in one queue
Show reasoningHide reasoning
How this is scored
Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.
0 — No customer channel of its own; the product only works on tickets entered by hand or by another system.
3 — Email turned into tickets, with a web form or one further channel.
5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.
10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.
The Support Lead
Email, phone, SMS, the Messenger, Slack, WhatsApp, Instagram, Facebook and Discord all land in one inbox in a single workspace, the team sees the customer's history across every channel, and the pages document moving from messaging to a call and back without losing context or history, with GDPR recording consent and new call metrics noted for phone. What I did not find is a customer portal where a requester can see their own tickets, or stated consent handling for WhatsApp specifically. 9 9 11 9
The Agent Advocate
Nine channels — email, phone, SMS, Messenger, Slack, WhatsApp, Instagram, Facebook, Discord — are documented landing in one inbox on the same customer record, with the history visible across every channel and agents answering without switching tools. The documented move from messaging to a call and back without losing context is exactly the mid-issue channel change I want; we found no public information on a customer portal where requesters see their own tickets. 9 9 9
The Data Protection Officer
Email, phone, SMS, the Messenger, Slack, WhatsApp, Instagram, Facebook and Discord connect from a single workspace, every Slack conversation lands in the same inbox as chat, email and phone, the customer's history is visible across every channel, and a move from messaging to a call and back is stated to preserve context and history. Recording consent for calls is stated for GDPR; we found no public information on a portal where a requester can see their own tickets. 9 9 9 11
The Shop Operator
Email, phone, SMS, Messenger, Slack, WhatsApp, Instagram, Facebook and Discord all connect from a single workspace, the customer's history is visible across channels, and a move from messaging to a call and back is documented without losing context or history. Phone and WhatsApp are pay-as-you-go with GDPR recording consent noted for calls; what I did not find documented is a customer portal where a requester sees their own tickets, or consent handling stated for WhatsApp itself. 9 9 2 11
The Integrator
Email, phone, SMS, Messenger, Slack, WhatsApp, Instagram, Facebook and Discord are documented as connecting from a single workspace, with the customer's history visible across every channel and a stated messaging-to-call-and-back transition that preserves context and history. GDPR recording consent for phone and pay-as-you-go WhatsApp and SMS are both stated, though I found no public information on a portal where a requester can see their own tickets. 9 9 9 2
The Skeptic
Nine channels — email, phone, SMS, Messenger, Slack, WhatsApp, Instagram, Facebook and Discord — are documented connecting to one Inbox with the customer's history visible across every channel, and messaging-to-call transitions are stated to keep context and history; phone brings call metrics and GDPR recording consent. We found no public information on a customer portal where a requester can see their own tickets, or on WhatsApp consent handling. 9 9 9 11
Knowledge base & deflection
Show reasoningHide reasoning
How this is scored
Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.
0 — No knowledge base or self-service of any kind; the product is a ticket inbox only.
3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.
5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning that flag stale content, and reporting on which articles deflect.
10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.
The Support Lead
Suggested articles before customers even search, an option to require a help-centre search before a conversation starts, articles inserted from the inbox and powering Fin and Copilot, forty-five languages, and multibrand help centres. The articles report shows helpfulness, what to improve and what is missing, including the topics customers searched for but did not find, and the resolution claims for Fin are tied to help-centre content. I found no public information on versioning or review dates that would flag stale articles. 10 11 11
The Agent Advocate
Article suggestions before the customer searches, search that can be made mandatory before contact, articles insertable from the inbox, forty-five languages, multibrand help centres, and an articles report that turns failed searches into a what-to-write-next gap list — that is deflection machinery, with Fin's resolution rate as the number. We found no public information on article versioning, review dates or approval workflows. 10 11 11
The Data Protection Officer
A public help centre with collections and a rich editor, suggested articles before customers search, the option to require a help-centre search before a conversation starts, article insertion from the inbox, articles powering Fin and Copilot, 45 languages, and an articles report showing the topics customers searched for but didn't find. We found no public information on versioning or review dates that flag stale content, and the deflection figures attach to Fin resolution rates rather than to individual articles. 10 11 11 11
The Shop Operator
Deflection is treated as a number you can act on: customers are prompted, and can be required, to search articles before starting a conversation, articles power an AI agent reported as resolving 76% of questions on average, and the articles report shows helpfulness plus the topics people searched for and never found. Forty-five languages, collections and multibrand help centres round it out, though I found no public information on review dates or versioning that flag stale content. 10 11 11 1
The Integrator
Deflection is taken seriously: suggested articles before a customer even searches, an option to require help centre search before a conversation starts, articles inserted by teammates and powering the AI agent and Copilot, forty-five languages, multi-brand centres, and an articles report showing helpfulness plus the topics customers searched for but could not find. I found no public information on versioning or review dates that flag stale content, or on deflection reported as a number the team can act on. 10 11 11 11
The Skeptic
A public, branded, multilingual help centre (45 languages) with suggested articles before customers search, an option to require a help centre search before starting a conversation, article insertion from the Inbox, outbound article sending, and an articles report that names gaps from searches that found nothing; Fin's 76% average resolution rate gives a deflection number. We found no public information on review dates or versioning that flags stale content. 10 11 11 1
Customer data protection
panel disagrees
Show reasoningHide reasoning
How this is scored
A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.
0 — The vendor's own terms state that ticket content is used for purposes beyond providing the service, or that a data processing agreement is not offered.
3 — A privacy policy and a data processing agreement (DPA) offered, with agent roles that limit what an agent can do.
5 — A DPA published or signable online, agent roles and group- or queue-level visibility, and deletion of tickets or of a requester's data documented in the help centre.
8 — Automatic retention or deletion rules per queue or data category, attachment handling stated, an audit log of agent access or changes, documented support for access and erasure requests, and redaction of ticket content.
10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.
The Support Lead
The DPA with the 2021 SCCs is incorporated into the terms without separate signature, permanent deletion of an individual's data is documented, visitor data auto-expires after nine months, and redaction is real engineering — irreversible, applied before save, with built-in card and social-security rules plus custom regex rules across messenger, email and call transcripts. Against that, the terms grant Intercom use of Customer Data to provide and improve the services, including AI model training, and I found no public information on an audit log of agent access, attachment handling, or configurable retention per queue. That training clause is the first thing my data protection officer would ask me about. 12 13 5 4
The Agent Advocate
The terms themselves grant the vendor a royalty-free right to use customer data to provide and improve the services, including its own AI model training — a use of ticket content beyond providing the service, which is the condition the lowest level describes. The captured pages also document a published DPA with the 2021 standard contractual clauses, export and permanent deletion of an individual's data, a nine-month visitor expiry, and irreversible content redaction with built-in card and social-security rules; I still cannot get past a training licence written over my customers' words. 5 13 12
The Data Protection Officer
The GDPR data processing agreement incorporating the 2021 SCCs is published within the terms, redaction of card and social-security numbers plus ten custom regex rules happens before save, is irreversible across messenger, inbound email and call transcripts, and export and permanent deletion of an individual's data plus a nine-month automatic expiry of unseen visitor data are documented. We found no public information on an audit log of who read or changed a ticket, on attachment handling, or on retention rules per queue or data category; and the terms grant Intercom usage rights over Customer Data including for AI model training, with beta offerings placed outside the agreement's security measures. 12 13 5 3
The Shop Operator
Strong tools are documented: a self-serve GDPR DPA incorporating the 2021 SCCs, export and permanent deletion of an individual's data, automatic nine-month expiry of visitor data, and irreversible before-save redaction with built-in card and SSN rules. The weight against it is that the terms grant Intercom use of Customer Data "including for Intercom AI model training", and I found no public information on an audit log of agent access or retention rules per queue. 12 13 5 7
The Integrator
A data processing agreement incorporating the 2021 SCCs is folded into the terms with no separate signature, export and permanent deletion of an individual's data is documented, subject rights run through a privacy request form, and redaction is irreversible and applied before save across messenger, email and call transcripts. Against that, the terms grant Intercom a right to use Customer Data to provide and improve the services including Intercom AI model training, and I found no public information on per-queue retention rules, attachment handling, or an audit log of agent access. 5 12 13 3 3
The Skeptic
Strong pattern-based redaction that runs before save, is irreversible, and covers Messenger, mobile SDKs, inbound email and call transcripts; access, erasure and export of all data per individual are documented, and a DPA with the 2021 SCCs is folded into the terms with no separate signature. Against that, the terms grant Intercom use of customer data to provide and improve the services including Intercom AI model training, and we found no public information on an audit log of agent access, attachment handling, or retention rules per queue — only a nine-month visitor expiry. 13 12 5 7
Integrations & API
Show reasoningHide reasoning
How this is scored
The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.
0 — A closed tool with no API and no integrations; context is copied in by hand.
3 — A handful of named integrations or a connector service such as Zapier, or an API with basic documentation.
5 — Named integrations for common CRM, shop or collaboration tools, a documented REST API, and webhooks or triggers that call other systems.
8 — An app marketplace with maintained bidirectional integrations, customer context from other systems shown inside the ticket, SSO and SCIM provisioning, documented rate limits and a sandbox.
10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.
The Support Lead
A documented REST API connector with read and write operations, token or OAuth authentication and field mapping, bidirectional webhooks usable in workflows, and named Salesforce, HubSpot, Shopify, Slack, Github and Zapier connections that pull customer data into answers — enough to wire CRM context into the conversation. But rate limits are only reserved in the terms rather than documented, SSO sits on the top plan, and I found no public information on SCIM provisioning or a maintained app marketplace. The pages also state connectors can only be fully tested in production, not in test workspaces — I would be testing refund actions against live customers. 14 14 15 5 2
The Agent Advocate
Named connectors for Slack, Shopify, GitHub, Salesforce and HubSpot, Zapier, a documented REST connector to any endpoint with token-based or OAuth authentication, and bidirectional webhooks clear the middle mark, with SSO priced into the top plan. But rate limits appear only as a reserved right in the terms, connectors are documented as fully testable only in production, and we found no public information on SCIM provisioning or vendor-maintained marketplace apps. 14 14 15 2
The Data Protection Officer
A documented REST API connector with field mapping and token-based or OAuth authentication, bidirectional webhooks, MCP support, named Salesforce, HubSpot, Shopify, Slack and Github integrations with CRM data pulled into the answer, plus SSO at the top tier. The terms only reserve the right to impose API rate limits without documenting them, connectors can be fully tested only in production and not in test workspaces, and we found no public information on SCIM provisioning or a maintained app marketplace. 14 14 15 2 5
The Shop Operator
The order can reach the agent without a second login: Fin pulls Shopify, Salesforce and HubSpot data into answers and executes read and write actions like processing refunds over a custom REST connector, webhooks run bidirectionally with token or OAuth authentication, and MCP is supported on both sides with a developer hub. What holds it back: connectors can only be fully tested in production rather than test workspaces, and I found no public information on published rate-limit numbers or SCIM provisioning. 14 15 2 8
The Integrator
The pieces I need mostly exist: a REST API connector with read and write operations, field mapping and token or OAuth authentication, bidirectional webhooks with per-webhook auth usable in workflows, MCP support, a developer hub, and named Salesforce, HubSpot, Shopify, Slack and Zendesk connections. But connectors can only be fully tested in production, not in test workspaces — the opposite of a sandbox — the terms merely reserve a right to place API call limits rather than documenting any, and I found no public information on SCIM provisioning, an app marketplace, or API versioning with a deprecation policy. 14 15 15 5 2 1 10
The Skeptic
Salesforce, HubSpot, Shopify, Slack, Zendesk import and Zapier are named, alongside a documented REST connector with read and write actions, bidirectional webhooks, field mapping and MCP support, with CRM context pulled into answers. SSO sits on the top plan only, we found no public information on SCIM or published rate limits, and the documentation itself states connectors can only be fully tested in production, not in test workspaces. 14 15 15 2 8
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.
The Support Lead
EU hosting is selectable — the subprocessor list shows AWS hosting of Customer Data as USA or EU depending on the customer's selected region, backed by a Regional Data Hosting Addendum — and buyers outside the US and Brazil contract with the Irish entity, with a DPA and a published subprocessor list with locations. But the services are stated as provided and hosted in the United States, the email-delivery subprocessors are US-based, the parent's seat is not stated, and no self-hosted option is offered. Workable if I pin the EU region in the contract, but not sovereign by default. 4 5 3 3
The Agent Advocate
An Irish entity contracts for customers outside the US and Brazil, the DPA is published with transfer clauses, and the subprocessor list is published with locations — while the privacy policy states the services are hosted in the United States, an EU region appears only in a subprocessor row and a regional hosting addendum rather than as an advertised option, and email delivery sits with two US-based subprocessors. Selectable EU, an Irish contracting route and a published list, with a US default underneath. 3 4 5 12
The Data Protection Officer
The privacy policy states the services and messenger domains are provided and hosted in the United States, with an EU region appearing only in a subprocessor row ("USA or EU dependent upon customer's selected region") and a Regional Data Hosting Addendum, while an Irish entity contracts for customers outside the US and Brazil. The published subprocessor list shows email delivery processors in the USA regardless of the selected region, transfers rest on SCCs, the IDTA and the US Data Privacy Framework, and the captured pages show no self-hosted option. 3 4 5 3
The Shop Operator
The privacy policy states the services are provided and hosted in the United States, and an EU region surfaces only in a subprocessor row and a regional hosting addendum rather than as an advertised option. Rest-of-world customers contract with the Irish entity Intercom R&D Unlimited Company, a self-serve DPA with SCCs is offered, and the subprocessor list is published with locations including named US email processors, under US Data Privacy Framework reliance. Selectable EU hosting plus an EU entity is more than nothing, but US-default hosting of the parcel-complaint archive keeps this modest for a European buyer. 3 4 5 3
The Integrator
Rest-of-world buyers contract with the Irish entity and a Regional Data Hosting Addendum exists, but the captured privacy policy states the services are hosted in the United States, the EU region choice surfaces only in a subprocessor row, and the published subprocessor list shows Mailgun and Sparkpost in the USA with AWS and OpenAI dependent on the customer's selected region. No self-hosted option appears in the captured material, and the parent company's seat is not stated. 5 4 3 3
The Skeptic
The privacy policy states the services are provided and hosted in the United States; an EU region appears only in a subprocessor row and a Regional Data Hosting Addendum link, not as an advertised hosting option, and no self-hosted option is offered. Rest-of-world orders contract with the Irish entity, a DPA with SCCs is offered, and the subprocessor list is published — with Mailgun and SparkPost in the USA and OpenAI and AWS at "USA or EU dependent upon customer's selected region". 3 4 5 12
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price or one priced tier, per agent or flat.
5 — Per-agent prices public for the main tiers with the billing period stated and the main features per tier listed.
8 — Every tier and add-on priced publicly with per-agent maths, telephony or messenger costs and light-agent or contact limits given, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.
The Support Lead
All three plans are priced per seat per month — Essential at $29, Advanced at $99, Expert at $139 — with annual and monthly billing, per-tier feature lists, priced add-ons (Proactive Support Plus at $99/mo, Pro from $100/mo), free Lite seat allowances of 20 and 50, Fin at $0.99 per outcome with spending limits, taxes stated as excluded and the customer's responsibility, and a cost calculator taking team size and expected Fin outcomes. The gaps are the metered channels: pay-as-you-go phone, SMS and WhatsApp carry no published unit rates in the captured pages, Copilot beyond its free ten conversations per agent per month carries no public number, and the captured pages give different figures for the seat price on the combined helpdesk-and-Fin offer ($19 and $29). I could get close to my annual invoice except for the metered channels. 2 2 5 1 1
The Agent Advocate
All three plans carry public per-seat monthly prices ($29, $99, $139), both add-ons are priced, AI is priced from $0.99 per Fin outcome, free Lite seat counts are stated, annual and monthly billing are shown, taxes are excluded per the terms, and a cost calculator takes team size and Fin outcomes as inputs. The pay-as-you-go unit rates for phone, SMS and WhatsApp are not published, and the minimum term lives in the Order Form, so the channel part of the invoice stays uncomputable from public pages alone. 2 2 2 5
The Data Protection Officer
Essential at $29 per seat/month, Advanced at $99 per seat/month and Expert at $139 per seat/month are public with an annual and monthly toggle, add-ons are priced (Proactive Support Plus $99 /mo, Pro from $100 /mo), free Lite seats are stated per tier, and taxes are excluded with the customer responsible. The captured pages give different figures for the seat-plus-outcome bundle ($19 per seat/mo + $0.99 per outcome and $29 per seat/mo + $0.99 per outcome), phone, SMS and WhatsApp are marked pay-as-you-go without public unit prices, and the minimum term sits in the Order Form; a cost calculator is offered but we found no public information on whether it covers usage-metered channels and overage. 2 2 2 5 1 1
The Shop Operator
A support lead can get most of the way to the invoice: Essential at $29 per seat/month, Advanced at $99, Expert at $139, with an annual and monthly toggle, Fin at $0.99 per outcome with a seat-free standalone option, priced add-ons, free Lite seats at 20 and 50, VAT stated as the customer's and excluded, and a cost calculator keyed to team size and expected outcomes. The misses: WhatsApp, SMS and phone are pay-as-you-go with no public unit rates, no minimum term is stated, and the captured pages give different figures for the bundled seat price ($19 versus $29 alongside the $0.99 outcome). 2 2 2 5 1
The Integrator
All three plans carry a public per-seat monthly price with an annual and monthly toggle, tier features listed, two priced add-ons, free Lite seats quantified per tier, taxes stated as the customer's responsibility on top of fees, and a cost calculator keyed to team size and expected AI outcomes. Pay-as-you-go is stated for phone, SMS, WhatsApp and email campaigns without per-unit rates on the captured pages, and the captured pages give different figures for the combined seat price ($19 per seat/mo on some, $29 per seat/mo on others). 2 2 2 5 1 1
The Skeptic
All three tiers carry public per-seat prices with annual and monthly billing stated, add-ons and free Lite seat counts are listed, taxes are stated as excluded and the customer's responsibility, and a cost calculator takes team size and Fin outcomes. The captured pages give different figures for the seat-plus-outcome bundle — "$19 PER SEAT/MO + $0.99 PER OUTCOME" and "$29 PER SEAT/MO + $0.99 PER OUTCOME" — and the pay-as-you-go phone, SMS and WhatsApp channels carry no unit rates on the captured pages. 2 2 5 1 1
European sovereignty — proven facts
3 of 6 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 |
Not determined
unverified
Why unverified?The vendor's pages name a local subsidiary and do not state the parent's seat. |
— | uncited Report an error |
|---|---|---|---|
| Hosting location |
Outside the EU
unverified
Why unverified?The subprocessor list (S1) shows AWS hosting of Customer Data as "USA or EU dependent upon customer's selected region", so EU hosting appears selectable rather than the norm, and the privacy policy adds transfers to Ireland, the UK and Australia. |
0/4 pts | 3 Report an error |
| Hosting options |
EU region selectable
unverified
Why unverified?The EU region choice appears only in a subprocessor row and in the 'Intercom Regional Data Hosting Addendum' link, not as an advertised hosting option on the product or pricing pages, and no self-hosted option is offered. |
1/1 pts | 4 Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The same article also says the DPA 'is available for customers to sign upon request' and that no bespoke DPA terms are accepted, though the Data Processing Addendum is also listed as a published document in the legal terms menu. |
1/1 pts | 12 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Intercom
Is Intercom European?
No. whats-best.ai classifies Intercom as Rest of world.
Where does Intercom store data?
Intercom stores customer data outside the EU by default, per the vendor’s page captured 16 Nov 2026.
Does Intercom have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Intercom?
As of 18 Nov 2026, the panel rates Zendesk (3.5/5), LiveAgent (3.5/5) and Deskpro (3/5) highest among the other 35 Customer Service & Helpdesk products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Zammad (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Intercom alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 11 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 — Data processing agreement. The same article also says the DPA 'is available for customers to sign upon request' and that no bespoke DPA terms are accepted, though the Data Processing Addendum is also listed as a published document in the legal terms menu.
- Weak sourcing — Legal entity. The vendor's pages name a local subsidiary and do not state the parent's seat.
- Weak sourcing — Hosting location. The subprocessor list (S1) shows AWS hosting of Customer Data as "USA or EU dependent upon customer's selected region", so EU hosting appears selectable rather than the norm, and the privacy policy adds transfers to Ireland, the UK and Australia.
- Weak sourcing — Hosting options. The EU region choice appears only in a subprocessor row and in the 'Intercom Regional Data Hosting Addendum' link, not as an advertised hosting option on the product or pricing pages, and no self-hosted option is offered.
- 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.
- 37 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
- 23 pricing 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 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
- 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 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
- 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (15)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.intercom.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 19 Oct 2026, 15 Sep 2026, 11 Sep 2026 Details →
- 2 Pricing www.intercom.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 15 Sep 2026, 11 Sep 2026 Details →
- 3 Privacy policy www.intercom.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 19 Oct 2026 Details →
- 4 Security / trust page trust.intercom.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 5 Terms of service www.intercom.com Checked 16 Nov 2026 Details →
- 6 Ticketing, queues & SLA — found from sitemap www.intercom.com Checked 16 Nov 2026 Details →
- 7 Ticketing, queues & SLA — found from sitemap www.intercom.com Checked 16 Nov 2026 Details →
- 8 Channels in one queue — found from sitemap www.intercom.com Checked 16 Nov 2026 Details →
- 9 Channels in one queue — found from sitemap www.intercom.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 10 Knowledge base & deflection — found from sitemap www.intercom.com Checked 16 Nov 2026 Details →
- 11 Knowledge base & deflection — found from sitemap www.intercom.com Checked 16 Nov 2026 +2 earlier captures: 9 Nov 2026, 2 Nov 2026 Details →
- 12 Customer data protection — found from sitemap www.intercom.com Checked 16 Nov 2026 Details →
- 13 Customer data protection — found from sitemap www.intercom.com Checked 16 Nov 2026 Details →
- 14 Integrations & API — found from sitemap www.intercom.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 15 Integrations & API — found from sitemap www.intercom.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →