Stop reconciling two platforms manually. Alex connects Intercom conversations and Salesforce records in real time, giving every team a single, accurate view of each customer.
Connect Intercom conversations and Salesforce records through Alex, ending manual data entry and giving every team a single, reliable customer truth.
Support teams working in Intercom and sales teams working in Salesforce are often looking at different versions of the same customer. A contact closes a support conversation in Intercom, but that signal never reaches the sales rep in Salesforce who is about to send a renewal pitch. A lead converts in Salesforce, but the support agent in Intercom has no idea the person is now a paying account. The gap between these two platforms is where customer context goes missing, and where manual data entry, copy-pasted notes, and out-of-date records quietly erode the customer experience. For DTC and e-commerce brands, that erosion translates directly into missed upsell moments, duplicated outreach, and churn that could have been prevented. The problem is not the tools themselves; it is the absence of a layer that keeps them speaking the same language in real time.
Alex sits between Intercom and Salesforce as an active intelligence layer, not a passive connector. Once integrated, Alex pulls conversation data, contact records, lead status, and company information from both platforms and builds a unified customer profile that is visible to every team. Intercom users sync bidirectionally with Salesforce contacts, Intercom leads sync with Salesforce leads, and Intercom companies sync with Salesforce accounts. Conversation activity logs as Salesforce tasks or cases, so sales reps see support history without leaving their CRM. On top of the structural sync, Alex layers in its own signals: loyalty scores, engagement levels, upsell fit, and interaction history across chat, email, WhatsApp, and voice. That combination turns a raw data sync into a living customer profile that drives proactive, personalised engagement rather than reactive ticket management. For brands focused on improving customer lifetime value, this unified view is the foundation everything else is built on.
Getting the sync right requires deliberate choices about which platform owns which data. Alex guides teams through field mapping, where each Intercom attribute is matched to its Salesforce counterpart, and the data types must be compatible for the sync to hold. Intercom text fields map to Salesforce string, textarea, phone, URL, email, and picklist types; Intercom number fields map to Salesforce integer, double, currency, and percent types. Required Salesforce lead fields, including email, last name, first name, and company, are mapped by default. Beyond field types, teams must decide which platform is the source of truth for specific data categories. Salesforce typically owns deal stage and account tier; Intercom typically owns conversation sentiment and engagement recency. Defining these boundaries before go-live prevents conflicting overwrites and keeps both systems clean. Alex also recommends matching records by a unique customer ID rather than email alone, which is the more precise deduplication method and avoids false merges when a contact appears in both systems under slightly different email formats.
With Intercom and Salesforce connected through Alex, the practical changes are immediate. Support agents in Intercom see the full Salesforce deal context, account tier, and open opportunities alongside the conversation they are handling. Sales reps in Salesforce receive Intercom conversation history and intent signals before they make a call. CX leaders can build stronger, data-informed customer relationships because every touchpoint, whether it originated in chat, email, or voice, is captured in the same profile. Alex's omnichannel design means it meets customers wherever they communicate and routes the resulting context back into both platforms. The outcome is a support and sales motion that feels coordinated rather than siloed, and customers who experience that coordination are measurably less likely to churn. Brands using Alex report 35% less churn compared to traditional ticket-based support models, and 3x more repeat purchases, outcomes that depend directly on the kind of unified customer view this integration creates.
Start by connecting your Intercom workspace and your Salesforce org to Alex from the integrations panel. Alex supports Salesforce Enterprise and Unlimited editions natively; if you are on Professional edition, you will need the API add-on enabled first. Authentication establishes the secure channel through which all subsequent data movement flows, so confirm that the Salesforce user account used for the connection has the API access permissions your org requires. This step typically takes a few minutes and does not require developer involvement.
Once both platforms are authenticated, map each Intercom attribute to its Salesforce equivalent and confirm the data types are compatible. Required lead fields, including email, last name, first name, and company, are pre-mapped by default, so focus your attention on custom attributes specific to your business. For each mapped field, set the sync direction: Intercom to Salesforce, Salesforce to Intercom, or bidirectional. Designate which platform is the source of truth for contested fields such as job title or company name, to prevent overwrites when both systems hold different values. This is also the stage to configure your deduplication logic; matching on a unique customer ID rather than email alone is the more reliable approach. See how omnichannel customer service platforms handle data routing for broader context on these decisions.
Define the events that initiate a sync: a new Intercom lead converting, a support conversation closing, a Salesforce opportunity moving to a new stage, or a contact attribute updating. Updates from Intercom to Salesforce run immediately; Salesforce is checked every 5 minutes for changes flowing back into Intercom. Configure whether closed Intercom conversations log as Salesforce tasks, cases, or both, depending on how your sales and support teams prefer to track activity. Sync starts from the moment you save your settings; historical records that have not been touched since setup will not be backfilled automatically, so plan a one-time data review if legacy records matter to your workflow.
Activate the integration and confirm that records are flowing correctly by checking a sample of known contacts in both platforms. Alex begins building enriched customer profiles immediately, layering loyalty scores, engagement levels, and upsell fit signals on top of the raw CRM and conversation data. Review user access controls to ensure support agents and sales reps see only the data their role requires, particularly for sensitive Salesforce fields. From this point, Alex operates continuously, responding to customers across chat, email, WhatsApp, and voice while keeping both Intercom and Salesforce updated in real time. For teams exploring what a fully automated customer service platform looks like in practice, this live state is where the relationship-building begins.
Alex merges Intercom conversation data and Salesforce CRM records into a single customer profile, so every team works from the same information rather than maintaining parallel, often contradictory records.
Changes in Intercom reach Salesforce immediately; Salesforce is polled for updates on a continuous basis. No manual exports or scheduled batch jobs are needed to keep the two platforms aligned.
Alex matches records using a unique customer ID rather than email alone, which is the more precise method. Duplicate contacts and conflicting records are resolved systematically, not left for support agents to untangle case by case.
Sales reps in Salesforce receive Intercom conversation history, sentiment signals, and engagement recency before they reach out. Outreach informed by recent support interactions is more relevant and less likely to land at the wrong moment.
Brands using Alex report 2.5x higher customer lifetime value and 35% less churn compared to ticket-based support models, outcomes that depend on the kind of coordinated, data-rich engagement this integration makes possible.
A support agent in Intercom receives a message from a customer asking about a delayed order. With the Salesforce integration active through Alex, the agent can see the customer's account tier, open opportunities, and recent deal activity directly alongside the conversation. The agent responds with full commercial context, avoiding the kind of generic reply that frustrates high-value accounts. The interaction is automatically logged as a Salesforce task, so the account owner sees the touchpoint without needing to be briefed separately. This is the kind of coordinated experience that builds durable customer relationships rather than just resolving tickets.
Before a renewal call, a sales rep opens the Salesforce contact record and finds the customer's full Intercom conversation history: three support interactions in the past month, one flagged as unresolved, and a pattern of questions about a feature the customer has not yet adopted. That context reshapes the call entirely. Rather than leading with a standard renewal pitch, the rep addresses the unresolved issue first and positions the feature as a solution. Alex's loyalty and engagement signals, surfaced in the same profile, help the rep gauge whether the customer is at churn risk or ready for an upsell. For teams thinking about AI-powered customer engagement platforms, this kind of pre-call intelligence is a core use case.
A CX leader at a DTC brand wants to identify customers who have had multiple unresolved Intercom conversations in the past 30 days and cross-reference them against Salesforce account health scores. With Alex connecting both platforms, that analysis runs on a unified data set rather than requiring a manual export and spreadsheet merge. Alex's loyalty scores and churn risk signals are layered on top of the raw CRM data, giving the CX leader a prioritised list of accounts that need proactive outreach. Alex then executes that outreach automatically across the customer's preferred channel, whether chat, email, or WhatsApp, without the CX leader needing to brief a separate team. This is what customer lifetime value optimisation looks like when it moves from strategy to daily operations.
There is no single universal answer; the source of truth is configured field by field during setup. Salesforce typically owns deal stage, account tier, and commercial history, while Intercom typically owns conversation sentiment and engagement recency. Alex guides teams through assigning a source of truth for each mapped field, so conflicting values are resolved by a rule rather than by whichever system wrote last.
Alex matches records using a unique customer ID rather than email address alone, which is the more precise deduplication method. Email-based matching can produce false merges when the same contact appears under slightly different email formats in each system. Configuring the unique ID match during setup prevents duplicate contacts from accumulating as the two platforms continue to receive new data.
Sync starts from the moment you save your settings; historical records are not backfilled automatically. A record that has not been updated since before the integration went live will remain unsynced until something touches it again, such as a new conversation, an attribute update, or a manual edit. Teams with large legacy data sets should plan a one-time review to identify records that need a manual trigger to enter the sync.
Yes. During configuration, teams define the specific events that initiate a sync: a lead converting, a conversation closing, an opportunity stage changing, or a contact attribute updating. Conversation logging can be directed to Salesforce tasks, cases, or both, depending on how sales and support teams prefer to track activity. This flexibility means the integration adapts to existing workflows rather than requiring teams to change how they work.
The Intercom Salesforce integration requires Intercom's Advanced or Expert plan and Salesforce Enterprise or Unlimited edition for full API access. Salesforce Professional edition is compatible if the API add-on has been purchased; Group and Contact editions do not support API access and cannot be used with this integration. Confirming your edition before setup avoids authentication failures during the connection step.
Alex connects your Intercom conversations and Salesforce records into a single, continuously updated customer profile, so your support and sales teams always work from the same truth. If you are ready to move beyond manual data entry and siloed tools, the setup starts with a single integration.