Intercom Salesforce Integration: Setup, Mapping and Pitfalls (2026)

What an Intercom Salesforce integration should do

Intercom is often the first place a prospect speaks: a chat on the pricing page, a question from a trial user, a message to the AI agent. Salesforce is where sales qualifies, owns and forecasts that person. Without a link, a rep calls a lead who complained in chat an hour ago, and an agent doesn’t know the person in front of them is a six-figure renewal.

A useful integration does four jobs:

• Turn conversations into leads. A qualified chat becomes a Salesforce lead with the right owner, source and UTM data.
• Keep people data consistent. Name, company, plan and lifecycle fields match in both tools, each owned by one side.
• Log the conversation. Reps see what the person asked, on the lead or contact record, without opening Intercom.
• Give agents context. In the Intercom inbox, the agent sees the account owner, the open opportunity and its stage.

It is not a full mirror. Every synced field can conflict, and every transcript copied into Salesforce is personal data in one more place. Sync what someone will act on.

What Intercom’s Salesforce app includes

Intercom builds and maintains the app and lists it in the Intercom App Store. According to Intercom’s help center, as of October 2026 it covers these parts:

Requirements

• Intercom plan: Advanced or Expert. Installing against a Salesforce sandbox is available only on Expert, from a test workspace.
• Intercom permissions: the installing teammate needs full admin rights, at least “Apps and Integrations Access” with all permissions.
• Salesforce edition: one with API access, such as Enterprise or Unlimited. Contact, Group and Professional editions lack it, although Professional can buy API access as an add-on.
• Salesforce user: a regular user, not API-only, with API Enabled, View All Data and read and write access to leads, contacts, accounts and tasks. If that user isn’t a System Administrator, the Intercom app must also be installed under Connected Apps OAuth Usage in Salesforce Setup.

What it doesn’t do

Intercom’s documentation lists the gaps. The ones teams hit most:

• No contact or account creation. The app only creates Salesforce leads. Contacts are created and leads converted in Salesforce, and a bulk sync never creates a person who exists on one side only.
• Accounts must already exist. Account sync also needs both records to exist already, and the link between a person and their company or account is not synced.
• No case status sync. Case creation is one-way. Closing the conversation updates the case transcript, not the case status, and Salesforce changes don’t flow back to the conversation.
• Fields it can’t map. Tags and events, compound fields, read-only fields and high-frequency attributes such as last seen. Formula fields sync only when another change triggers a sync. Reference fields arrive as record IDs, not names.
• Case form limits. No field validation, no default formula fields, and required case fields must be filled in Intercom first. A failed automatic case shows up under Sync Errors, not as a message to the teammate.
• Opportunity linking. A conversation is related to an opportunity only when there is exactly one open opportunity; with several, it is ignored.
• Not instant. Changes in Intercom are sent right away, but Intercom checks Salesforce for changes every 5 minutes, so updates can take up to 5 minutes to appear.

Your options compared

Four routes, from least to most effort:

If you run Zendesk next to Intercom, or are choosing between them, our Zendesk Salesforce integration guide covers that pair. For the overall map of Salesforce integration routes, start with the Salesforce integration guide.

Which option fits you?

Answer five questions on your Intercom plan, what must flow back into conversations and how strict your data rules are. One possible answer is to stop syncing and run support in Salesforce.

How the data flows

The design that holds up: Salesforce owns accounts, ownership, lifecycle stage and opportunities. Intercom owns conversations and product-side attributes such as plan or signup date. Transcripts flow one way into Salesforce; account context is read live in the inbox.

Field mapping: what goes where

Start with this minimum set. For each row, one system owns the value and the other only receives it.

Two settings matter most. First, each mapping can skip the sync when the source is empty or when the destination already has a value. Use them so an empty Intercom field never wipes a value sales typed in.

Second, pick the matching key before you connect. Intercom recommends a unique identifier, but leads can only match by email. If you switch email matching off, lead creation from Intercom stops working.

How to set it up, step by step

Settle field ownership and clean duplicates before you click Install: the app matches on whatever it finds on day one. Intercom’s help center shows the current screens for each step.

1. Write down who needs whatWhich chats should become leads, which fields reps need, which conversations should become cases, and which Salesforce fields agents need in the inbox. This becomes your mapping and your list of what must not sync.
2. Check plan and editionConfirm you are on Intercom Advanced or Expert and that your Salesforce edition has API access. If you want to test against a Salesforce sandbox, that needs Expert and a test workspace.
3. Create the connecting userA regular Salesforce user (not API-only) owned by the team, with API Enabled, View All Data and read and write on leads, contacts, accounts and tasks. Add case permissions if you will create cases (Intercom needs Edit on cases to assign case owners). If it isn’t a System Administrator, install the Intercom app under Connected Apps OAuth Usage.
4. Clean duplicates firstMerge duplicate leads and contacts in Salesforce and duplicate users in Intercom. The app matches on what it finds, so dirty data on day one means wrong owners and wrong transcripts.
5. Install and connectIn the Intercom App Store, open Salesforce, click “Install now”, authorize access and sign in as the connecting user (choose “Install using sandbox” for a sandbox).
6. Set matching and mappingsPick the matching attribute, then map attributes one by one with a direction for each, starting with the required lead fields the app maps by default. Turn on the skip rules for empty sources and filled destinations where sales owns the value.
7. Configure ownershipDecide whether Salesforce ownership should follow the Intercom owner (the “Maintain lead and account ownership” setting) or the other way round. Make sure every teammate who should own records has a Salesforce user with the same email.
8. Configure tasks and casesTurn on automatic task creation if reps need transcripts. For cases, pick a default case record type, map conversation attributes to case fields, and decide whether the case owner follows Salesforce rules or the Intercom teammate.
9. Test real scenariosA new chat lead, a lead whose email already exists as a contact, and two leads with one email. Then a person with two open opportunities, a case with a required field left empty, and an owner who has no Salesforce user. Check records, owners and the Sync Errors tab.
10. Pilot, then run a bulk syncRun one team for a week or two. Then run a bulk sync for people who exist in both systems while API usage is low, and brief sales and support on what syncs where.

If you later change the connected Salesforce user, disconnect and reconnect as the new user. Intercom warns that uninstalling the app clears your attribute mappings.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Pitfalls and how to fix them

Personal data deserves a decision, not a default. Privacy laws include the GDPR and US state laws like the California Consumer Privacy Act. Under them, a deletion or access request may have to cover Intercom and every Salesforce task and case that holds a copy of the conversation. The fewer copies, the easier that is.

When to go beyond the app

An iPaaS fills single gaps without replacing the app. Examples: creating a Salesforce contact when an Intercom user signs up, updating a field when a case closes, or posting a qualified lead to Slack. Keep each field with one writer. If you already run MuleSoft, our Salesforce MuleSoft integration guide covers that route.

Custom work pays off when:

• You need accounts created from Intercom, person accounts, custom objects (subscriptions, workspaces, usage) or tags and events in Salesforce.
• Case status and replies must flow back to the conversation.
• Transcripts must be filtered or masked before they reach Salesforce, with rules you can audit.
• You route people between several Salesforce orgs or Intercom workspaces.

A typical build is a small middleware service. On the Intercom side it listens to webhooks (topics such as contact.lead.created and conversation.admin.closed) and calls the Intercom REST API. Intercom’s developer docs set a default of 10,000 API calls a minute per workspace for private apps, spread across 10-second windows.

On the Salesforce side it uses the REST API, Platform Events or Change Data Capture, and a dedicated integration user. Salesforce includes a limited number of Salesforce Integration user licenses in supported editions. Add idempotency so retries don’t create duplicates, a queue and alerts.

Creating contacts on signup is a one-way job; status that flows back from cases to conversations needs a two-way sync. See the API integration cost guide for how these ranges are built.

When Salesforce should run support instead, or alongside

Some teams find the integration is the wrong problem. Salesforce’s own service product, now called Agentforce Service (formerly Service Cloud), handles messaging, cases and AI agents inside the CRM, so there is nothing to sync. It tends to fit when:

• Support depends on Salesforce data every day: entitlements, contracts, assets, field service.
• You already run other Salesforce clouds and want one customer timeline and one reporting layer.
• The Intercom link has grown into several recipes, custom code and a part-time owner.

There is a middle path. Intercom sells Fin for Salesforce, which runs its Fin AI agent on Salesforce cases that arrive by email and web form, following your case assignment rules. It also covers live chat in Fin Messenger, with handoff to Salesforce’s in-app messaging.

According to Intercom, as of October 2026 it is available through its sales team, not self-serve. It suits teams that want Intercom’s AI agent but keep agents and cases in Salesforce. Keep the Intercom messenger and the Salesforce app if support is happy in Intercom and sales only needs context.

Go-live checklist

Go through this before the bulk sync, since that step updates everyone who exists in both tools at once. The score tells you whether to pilot or keep preparing.

FAQ

Where Gilzor fits

An Intercom link works when sales and support agree which side owns each field and which chats become leads or cases. Gilzor is a software development company in Poland and Cyprus that builds and maintains Salesforce integrations.

We can run that mapping with your sales and support leads, configure Intercom’s Salesforce app or an iPaaS, or build a custom integration on the Intercom and Salesforce APIs, and support it after launch. To see how such a project is scoped, visit our Salesforce integration services page.