n-Intercom and Salesforce Can See Each Other. They Still Need to Act on Each Other.
Intercom's native Salesforce integration syncs contact and company records between the two systems and lets support and sales see each other's data without switching tools. It's real, and it's a solid starting point. What it doesn't do is trigger actions across the two systems, a support conversation closing doesn't move a deal forward, and a deal closing doesn't automatically change how support handles that account. That's the part custom work builds on top.
How Intercom and Salesforce connect out of the box
Intercom's Salesforce app is a native, officially supported integration: once connected, it syncs contact and company fields between the two systems and surfaces Salesforce account and opportunity data as a panel inside an Intercom conversation, so an agent can see deal context without logging into Salesforce separately. It also supports pushing conversation data, like a transcript or a tag, into related Salesforce records.
This covers visibility well for most teams. A support agent sees that the person they're talking to has an open opportunity and its stage, and a rep in Salesforce can see recent support activity for an account, both without leaving their own system.
Where the native sync stops
The gap is logic, not data access. A conversation resolving in Intercom doesn't change anything about the related opportunity's stage. A deal closing in Salesforce doesn't automatically kick off anything on the Intercom side, like a welcome message sequence or tagging the contact for a different kind of support. Custom field mapping beyond the standard sync, and anything conditional (only flag an account if support volume crosses a threshold, say), also sits outside what the native app does.
What We Built on Top of Intercom and Salesforce
A SaaS company running both products had reps manually checking Intercom before a renewal call, since the native sync showed recent conversations but not whether those conversations represented a routine question or a serious, unresolved complaint. We built logic that reads conversation tags and resolution status, not just count, and flags the Salesforce account record automatically when support activity crosses a threshold that should change how a rep approaches the renewal. On the other side, a deal marked Closed Won in Salesforce now triggers an onboarding message sequence in Intercom automatically, with the account's plan tier already attached, instead of a rep remembering to kick it off manually. Both directions ran through the native sync's data the whole time. It just never had the logic to act on what it was already syncing.
Running Intercom and Salesforce side by side and still bridging the gap yourself?
Tell us what should happen automatically between the two, a flag on an account, a sequence triggered by a closed deal, a status that should move both ways, and we'll build it on top of the native sync instead of replacing it. If the pairing actually costing you time is two different systems entirely, we build that version too.
Let's talk