Customer Service & Helpdesk
Intercom
Rest of world Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 4 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? →
Read this page as one judge. Each weighs the same scores by what they care about.
No written verdict for this product
The panel scored Intercom, but the summary our synthesizer wrote did not survive our own contradiction check — twice. Rather than print a paragraph we cannot stand behind, we print none. Every score, rationale and source below is unaffected; read them and draw the conclusion yourself.
The scores
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 — A shared mailbox with labels; no ownership, no status model, no history beyond the thread.
3 — Tickets with assignment and open/closed status, but routing is manual, there are no SLA timers and search covers subject lines only.
5 — Queues with rules-based routing, priorities, a working status model, SLA timers with breach warnings, and full-text search across ticket bodies.
8 — Business-hours-aware SLA policies per queue or customer, escalation chains, macros and triggers, merge and split, 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
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. 1 2
The Agent Advocate
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. 1 2
The Data Protection Officer
Multiple team inboxes, a Workflows automation builder and round-robin assignment are real routing, and SLAs exist — but only as a named feature of the top Expert tier, with no evidence of SLA timers, escalation chains, priorities, merge/split, or any search over ticket bodies. 'Pre-built reports' is a label, not a statement of what is measured. 2 1
The Shop Operator
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. 1 2
The Integrator
Multiple team inboxes, a workflows automation builder, round-robin assignment and SLAs (Expert tier only) clear the anchor-5 bar, but the evidence says nothing about SLA breach warnings, business-hours policies, escalation chains, macros, merge/split or full-text search across ticket bodies, so I cannot move toward 8. 1 2
The Skeptic
Rules-based routing and assignment are real — 'Workflows automation builder, Round robin assignment, Multiple team Inboxes' — but SLAs begin only at the top Expert tier, and the evidence says nothing at all about SLA timers, escalation chains, macros, merge/split, or what search covers. That lands between the manual-routing anchor and the working-SLA anchor, and the silence on search and breach handling is information, not charity. 2 1
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 — Email only.
3 — Email plus one more channel, but the second lives in its own inbox: no shared history, and a customer who switches channel starts again.
5 — Email, a web form or portal and live chat all landing as tickets in one queue, with the customer's history visible whichever channel they used.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp, Signal or similar) with its consent handling stated, and a customer portal where a requester can see their own tickets.
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
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. 1 2
The Agent Advocate
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. 1 2
The Data Protection Officer
The channel breadth is genuine — live chat, support email and in-app chats free on all plans, phone, SMS and WhatsApp pay-as-you-go, all into an omnichannel inbox — but the rest of the 8 anchor is silence: no call-logging detail for telephony, no consent handling stated for WhatsApp, and no customer portal where a requester sees their own tickets. 2 1
The Shop Operator
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. 1 2
The Integrator
Email, live chat and in-app chats land in one omnichannel inbox, and phone, WhatsApp and SMS exist as pay-as-you-go channels with Fin handing off into a preferred inbox — beyond rubric level 5. But there is no evidence of call logging, of WhatsApp consent handling, or of a portal where a requester sees their own tickets, which is what rubric level 8 demands. 1 2
The Skeptic
The logo count is decent — email, live chat, in-app, phone, WhatsApp, Slack — and an 'omnichannel inbox' is claimed, but phone, SMS and WhatsApp sit on pay-as-you-go meters rather than being simply in the queue. No consent handling for messengers is stated, and nothing evidences a customer portal where a requester sees their own tickets, so this stops short of the anchor that requires those. 2 1
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; answers live in agents' heads and old tickets.
3 — A basic article list, public or internal, with no editorial workflow, no versioning and no link between articles and tickets.
5 — A searchable public help centre with categories, draft and publish states, and agents able to insert an article into a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates 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
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. 1 2
The Agent Advocate
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. 1 2
The Data Protection Officer
A public help centre, private and multilingual versions, and a Knowledge Hub are confirmed, and Fin's 76% average AI resolution rate is deflection sold as the headline number. What is missing is everything editorial: no draft/publish workflow, no review dates, and no reporting that says which article deflected which ticket. 2 1
The Shop Operator
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. 1 2
The Integrator
A public, multilingual help centre, a Knowledge Hub, Copilot assisting agents and Fin deflecting (76% claimed resolution) sit close to rubric level 8. But no draft/publish editorial workflow, no review dates flagging stale content and no per-article deflection reporting for my own instance are evidenced anywhere in the evidence. 1 2
The Skeptic
A public help centre on every plan, private and multilingual from the Advanced tier, plus a 'Knowledge Hub' to centralise content. But no editorial workflow, versioning, review dates, or article-level deflection reporting is evidenced anywhere; Fin's 76% resolution rate is AI answering, not articles deflecting, so the managed-asset story is unproven. 2 1
Customer data protection
Show reasoningHide reasoning
How this is scored
A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights, and what the vendor does with attachments — judged on what executes rather than what is promised.
0 — No retention policy stated, no deletion path, agents all see everything, and no DPA is published.
3 — A DPA on request and coarse roles; deletion is described as something the customer arranges, and there is no stated retention period.
5 — A signable DPA published, configurable agent roles and queue-level visibility, a stated retention period, and deletion of a requester's data that can actually be executed.
8 — Automatic retention rules per queue or data category, attachment handling stated, an audit log of who opened which ticket, documented support for access and erasure requests, and pseudonymisation or 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 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. 3 2
The Agent Advocate
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. 3
The Data Protection Officer
A DPA, a published subprocessor list, an appointed DPO and a documented rights list including deletion are real — but the only retention figure anywhere is a 14-day cookie form-prefill, and the evidence says nothing about ticket retention, agent roles, queue-level visibility, attachment handling, redaction, or an audit log of who opened which ticket. Meanwhile the policy discloses generative-AI processing of personal information, and vendor support access to customer instances is not documented at all. 3
The Shop Operator
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. 3
The Integrator
A published DPA, subprocessor list, an appointed DPO and a full data-subject rights list are more than rubric level 3, but no ticket retention period is stated (only a 14-day form-prefill detail), nothing evidences agent roles, queue-level visibility, audit logs or redaction, and the vendor itself runs generative AI over personal data with unspecified limits. 3
The Skeptic
The DPA is published, a DPO is appointed, the full rights list including deletion is documented, and a subprocessor list exists — better than the on-request anchor. But there is no stated retention period for the ticket archive (the only retention figure is 14-day form prefill), no agent role or queue-visibility model, no audit log, no redaction — and the policy admits AI including generative AI may process personal data via 'service providers and third parties' with no stated boundary. 3
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 — No API and no named integrations; context is copied in by hand.
3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.
5 — Named integrations for common CRM and shop systems, a documented REST API with keys, webhooks for the core ticket events, and SSO.
8 — Maintained bidirectional integrations, customer context from other systems shown inside the ticket, 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
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. 1 2
The Agent Advocate
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. 1 2
The Data Protection Officer
Salesforce, Shopify, Slack and Github are named integrations, SSO sits in the Expert tier, and an API exists — but it is described only as 'APIs or MCP' that Fin uses to pull customer data and take action. No webhooks, no documented rate limits, no SCIM provisioning, no sandbox anywhere in the evidence. 1 2
The Shop Operator
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. 1 2
The Integrator
Salesforce, Shopify, Slack and Github are named and SSO exists, but the only API statement is a marketing line that Fin "takes action through APIs or MCP" — no documented REST API, no webhooks, no rate limits, no SCIM, no sandbox. I have to wire a CRM, a shop and an identity provider behind this, and the evidence gives me named logo integrations, not a developer platform. 1 2
The Skeptic
Named integrations exist (Slack, Shopify, Github, Salesforce) and Fin 'takes action on external systems through APIs or MCP', which is more than read-only. But the helpdesk's own API is a marketing mention, not documented REST with keys; no webhooks, rate limits, sandbox or SCIM appear, and SSO itself is gated to the Expert tier. 1 2
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.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — support tooling, analytics, AI features — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, 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
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. 3
The Agent Advocate
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. 3
The Data Protection Officer
The services 'are provided and hosted in the United States' by a Delaware corporation, with transfers to Ireland, the UK, Australia 'and other such countries as we deem appropriate from time to time' — the transfer clause alone is the kind of language I red-pen. SCCs, the DPF and a published subprocessor list keep this just above the floor, but no EU hosting option is evidenced anywhere. 3
The Shop Operator
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. 3
The Integrator
The contracting entity is Intercom, Inc. of Delaware and the service is "provided and hosted in the United States", with transfers under the DPF/SCCs to Ireland, the UK and Australia — that is the core of rubric level 0, and only the published subprocessor list lifts it slightly. No EU hosting option is offered at all. 3
The Skeptic
The vendor's own privacy policy states the services 'are provided and hosted in the United States', the contracting entity is a Delaware corporation, and no EU residency option is evidenced — that is the non-EU-archive scenario this buyer fails. The mitigants are real but thin: a published subprocessor list, SCCs/DPF for transfers, and a DPO — enough to lift it off the floor, not enough to reach the EU-hosting anchor. 3
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 per-agent headline exists, but the tier where the needed channel or SLA feature begins is unstated, or light-agent and contact limits are not mentioned.
5 — Per-agent prices public for the main tiers with billing period stated, but at least one commonly needed capability (telephony, messengers, SLA policies) sits in an unpriced bundle.
8 — Every tier and add-on priced publicly with per-agent maths, 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
$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. 1 2
The Agent Advocate
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. 1 2
The Data Protection Officer
$19 per seat plus $0.99 per outcome is public, the annual/monthly toggle is stated, and the free-versus-pay-as-you-go channel split is unusually explicit — but the Expert tier, where SLAs live, carries no number, the pay-as-you-go phone/SMS/WhatsApp rates are unstated, and VAT treatment and minimum terms are absent. An outcome-metered invoice is only ever a capped estimate; spending limits help you cap it, not compute it. 1 2
The Shop Operator
$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. 1 2
The Integrator
$19/seat/mo with an annual/monthly toggle and $0.99 per outcome with spending limits let me compute the base invoice, but telephony, WhatsApp and SMS are pay-as-you-go with no unit prices published, and SLAs sit in an Expert tier whose price the evidence never states. A support lead cannot compute the real annual invoice for the channels they actually need. 1 2
The Skeptic
One seat price ($19/seat/mo) with an annual/monthly toggle and $0.99-per-outcome AI pricing is public, and the meter is at least capped via spending limits. But the evidence captures no seat prices for the Advanced and Expert tiers where SLAs and SSO live, the pay-as-you-go channels (SMS, WhatsApp, Phone) have no published rates, what a 'Lite seat' may actually do is never defined, Copilot is metered at just 10 free conversations per agent per month, and VAT treatment and minimum term are silent. 2 1
European sovereignty — proven facts
1 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 | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | US by default ⚠ unverified | 0/3 pts | 3 Report an error |
| Subprocessors | Not determined ⚠ unverified | — | uncited Report an error |
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 — Legal entity, Subprocessors. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Data residency. The trust center shows an optional EU hosting region ("USA or EU dependent upon customer's selected region" for AWS), so the EU location is a customer choice on top of the US default.
- 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.
- 23 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
- 19 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
- 11 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
- 5 data 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
- 4 subprocessors 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 integrations 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
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are 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
- The panel’s written verdict is withheld: our own re-read found claims in it that the evidence does not carry, and a second synthesis did not fix them. The scores and the material below are unaffected. 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 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 2 Pricing www.intercom.com Checked 15 Sep 2026 +1 earlier capture: 11 Sep 2026 Details →
- 3 Privacy policy www.intercom.com Checked 15 Sep 2026 Details →
- 4 Security / trust page trust.intercom.com Checked 30 Sep 2026 Details →
- 5 Terms of service www.intercom.com Checked 30 Sep 2026 Details →
- 6 Ticketing, queues & SLA — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →
- 7 Ticketing, queues & SLA — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →
- 8 Channels in one queue — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →
- 9 Channels in one queue — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →
- 10 Knowledge base & deflection — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →
- 11 Knowledge base & deflection — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →
- 12 Customer data protection — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →
- 13 Customer data protection — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →
- 14 Integrations & API — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →
- 15 Integrations & API — found from sitemap www.intercom.com Checked 1 Oct 2026 Details →