View all app connections
View all AI automations
View all chatbots
View all lead automations
View all booking automations
View all payment automations
View all workflows
View all Shopify
View all WooCommerce
View all HubSpot
View all Salesforce
View all Stripe
View all Google Sheets
View all Slack
View all dental practice
View all law firm
View all medical practice
View all real estate
View all restaurant and food
View all home services
View all construction
See all: get more leads
See all: get paid faster
See all: save admin time
See all: support customers
See all: book more appointments
See all: sell more online
See all: hire and onboard
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations

BoldBellowsIntercom Salesforce CRM sync for revenue teams that need every chat on the right record

Intercom to Salesforce automation that upserts leads and contacts on an external ID, logs each chat as an activity and opens opportunities by rule

Salesforce will not create a Lead without a last name and a company, and the same person can already exist as a Lead, a Contact or both, which a chat tool rarely knows. To sync Intercom conversations to Salesforce without clutter, BoldBellows stamps each notification with its topic, its workspace and its conversation ID, gives a late delivery time to land and checks the order before it writes, then searches Salesforce for the contact by email and external ID, decides between a Lead and a Contact by your written rule, upserts on an Intercom external ID field, logs the conversation as an activity on the record and its account, and opens an opportunity only when the conversation meets your criteria. Salesforce keeps the story; Intercom keeps the chat.

View Pricing

From $870, billed once.

  • Intercom Salesforce CRM sync
  • Intercom Salesforce lead capture on an external ID
  • Conversations logged as activities
Intercom chats matched to Salesforce leads and contacts through an external ID, logged as activities and turned into opportunities by rule, built by BoldBellows
Intercom to Salesforce: synced, zero duplicate recordsStatus card: Duplicate blocked, Conversation #1042 matched, not added.Duplicate blockedConversation #1042 matched, not added Intercom to Salesforce: live Conversations resolved cardMini chart card: net activity, live trend.CLOSED ACTIVITY · LIVE1.24k+8.2%

What this Salesforce route promises, and how

  • External ID upsertone Intercom contact, one Salesforce record
  • Lead or contact by rulean existing customer never becomes a new lead
  • Activity on the recordeach chat is logged where reps work
  • Opportunities by ruleonly qualifying conversations open one
  • Evidence keptEach decision stores the identifiers and timestamps behind it
  • No subscription$870 to start, then nothing recurring from us

01the duplicate-lead problem

A chat lead pushed blindly into Salesforce duplicates a customer you already have

A visitor who is already a paying contact starts a chat, and the integration creates a fresh Lead beside the Contact. The rep emails a customer as if they were new, while the account owner has no idea the customer asked about pricing. Create opportunities from every chat and the forecast fills with questions about password resets, so nobody trusts the numbers.

A customer worked as a lead

No search for the existing contact.

A rejected create

Company or last name was missing.

Duplicate rules firing

A near match blocked the record.

The same Intercom chats, on the Salesforce record the rep opens

Before: a lead for every retry

Before Intercom to Salesforce automation: manual conversations exports, duplicates and broken formulasThe old way: a pile of error messages that each need a manual fix.!Formula broke in row 88Needs a manual fix!Open conversations count doesn't matchNeeds a manual fix!Resolution is missing 3 conversationsNeeds a manual fix3
  • A retried delivery adds another lead
  • Every chat risks a new lead
  • History stays in Intercom

After: retries find the lead they made

After Intercom to Salesforce automation: one clean org that matches IntercomThe new way: live tiles for conversations, net activity, handoffs and open conversations, all in sync.Live · synced 2 min agoConversations142Closed activity1.24kHandoffs6Open conversationsIn sync
  • An Intercom contact ID held in an external ID field on the Lead or Contact, plus the conversation ID on the activity links every lead to its source
  • Existing customers are recognized first
  • Each conversation is an activity on the right record

02how it works

How an Intercom conversation becomes the right Salesforce record and an activity

Three moves: decide whether it counts, locate the Intercom lead, then write and prove it.

How Intercom to Salesforce automation works: conversations in, one clean record each, on a scheduleIn 4 steps: Your Intercom workspace; The sync; Your Salesforce org; Reports. Every change is checked before it lands.1STEP 1Your Intercom workspaceConversations, contacts, teammates, replies2STEP 2The syncRuns daily, hourly or in minutes3STEP 3Your Salesforce orgClean reports, no duplicate records4STEP 4ReportsConversations, response time, resolutionsEvery change checked against IntercomLIVE SYNCHow Intercom to Salesforce automation works: conversations in, one clean record each, on a scheduleIn 4 steps: Your Intercom workspace; The sync; Your Salesforce org; Reports.1STEP 1Your Intercom workspaceConversations, contacts, teammates, replies2STEP 2The syncRuns daily, hourly or in minutes3STEP 3Your Salesforce orgClean reports, no duplicate records4STEP 4ReportsConversations, response time, resolutions
  1. Interpret the source state. The route reads the Intercom record behind the event and confirms the conversation change meets the documented rule.
  2. Verify, search, decide. The signature is checked, Salesforce is searched by external ID and email, and your rule picks Lead or Contact.
  3. Upsert, log, qualify. The record is upserted on the external ID, the activity is logged and the opportunity rule decides whether one is created.

Why the Intercom to Salesforce route is built this way

  • Notes stay internal. A note added through the reply endpoint is visible only to teammates while a comment is visible to the customer, so the route chooses on purpose which one it writes.
  • Leads need two fields. A Salesforce Lead requires a last name and a company, and an upsert on an external ID field needs that field created and marked as an external ID first, so the build checks both before the first write.
  • Uncertain results. A missing confirmation starts a lookup in Salesforce by an Intercom contact ID held in an external ID field on the Lead or Contact, plus the conversation ID on the activity; a new write is never the first response.

03What you get

The parts of an Intercom to Salesforce build, and what each does

Start with Core, which admits events and claims identity; Scale then shapes the lead; Stewardship checks Salesforce long after go-live.

CoreScaleStewardship

Owner dashboard fed by Intercom to Salesforce automationOwner dashboard: a funnel from conversations received to verified and logged records, with zero duplicates.From event to verified recordToday · every step countedConversations received1,204Matched to a record1,199Checked against Intercom1,199Verified and logged1,198Duplicates0Held for review5

Trigger gatekeeper Core

Lets only the agreed conversation changes through and keeps a reason for every one it stops, for this Intercom to Salesforce route.

Stable identity ledger Core

Holds the record ID and modified time for each Intercom change, so a repeat is recognized rather than re-created.

Payload trimmer Core

Cuts each Intercom payload down to the fields Salesforce needs before the lead is prepared.

Lead-or-contact resolver Scale

Reads an Intercom contact ID held in an external ID field on the Lead or Contact, plus the conversation ID on the activity on every event so a repeat is recognized before it writes.

Activity logger Scale

Logs the conversation as an activity on the record and its account, with the topic and outcome.

Opportunity rule matrix Scale

Decides, by topic, plan and account, whether an opportunity opens, for which owner and at which stage.

Record register Stewardship

Finds records where Salesforce has drifted from Intercom and shows how long they have been wrong.

Permission and field drift monitor Stewardship

Catches a removed field or a lost permission for the integration user before writes fail.

Case register Stewardship

Keeps evidence, status and next step for every Salesforce lead that could not be confirmed.

Teams asking about sync intercom conversations to Salesforce often add intercom to Salesforce service and intercom to Salesforce Zapier. Related searches include intercom Salesforce lead capture, intercom to Salesforce duplicate prevention, connect intercom to Salesforce, intercom contacts Salesforce mapping, intercom to Salesforce implementation, intercom lead to Salesforce opportunity, intercom to Salesforce, intercom Salesforce automation, intercom to Salesforce Zapier alternative, intercom Salesforce contact create, intercom Salesforce webhook, intercom Salesforce CRM sync, intercom Salesforce workflow, intercom Salesforce integration without Zapier, intercom to Salesforce historical migration, intercom Salesforce opportunity, intercom to Salesforce error handling, intercom to Salesforce consultant, Salesforce activity from intercom conversation, intercom Salesforce integration and intercom Salesforce external id upsert.

04Who it's for

If you are among the teams that pair Fin with human teammates in Intercom, you may also need to put chat leads into Salesforce as the right object, with the conversation logged and opportunities opened only when your rule says so

Intercom is where interest and questions appear first; Salesforce is where the company records what it means.

Sales rep

"Show me what they asked before I reach out."

The conversation is an activity on the record, with the account attached.

Account executive

"Do not treat my customer as new."

Existing contacts are found first and never become leads.

Revenue operations

"Keep the pipeline honest."

Opportunities open only when a rule you wrote is satisfied.

Salesforce admin

"Respect my duplicate rules."

The build searches before it creates and reports near matches instead of forcing them.

Support lead

"Sales keeps asking what we said."

The topic and outcome are logged on the record.

Founder

"One record for each customer."

Chat history and the deal sit together.

05Compare

A managed package that copies every chat, a zap or an external-ID lead and activity route: choosing how Intercom reaches Salesforce

Each can create a lead. Only one finds the existing contact first, logs the chat as an activity and opens an opportunity by rule.

Comparison table: A managed package that copies every chat, a zap or an external-ID lead and activity route: choosing how Intercom reaches Salesforce
How a run startsa managed package that copies every chatA no-code Intercom to Salesforce recipeOur Intercom-to-Salesforce route
What starts the workWhoever is watching IntercomWhatever the trigger allowsYesAn approved conversation change, judged before any write
How identity is decidedMatched by eyeThe title or a labelYesAn Intercom external ID on the lead or contact, plus the conversation ID on the activity
What reaches SalesforceA pasted summaryA raw payloadYesOne correct record, an activity per conversation and an opportunity only by rule
After an uncertain resultStaff search Salesforce manuallyA blind retryYesFinds the lead first, then decides

Events arrive out of order

Delivery order is not trusted. Each Intercom event is ranked by its own time against the state already held in Salesforce.

A lead converts to a contact between two conversations

The external ID is carried over, the route resolves the new Contact and the next activity is logged against it, with the earlier history left intact. A search on an Intercom contact ID held in an external ID field on the Lead or Contact, plus the conversation ID on the activity finds what exists; a comparison says whether it matches; the outcome is written down. Creation is allowed in one case alone: the Salesforce lead is confirmed missing.

Everything in this route hangs from an Intercom contact ID held in an external ID field on the Lead or Contact, plus the conversation ID on the activity, so it is agreed before any mapping begins.

PricingThe price follows objects, fields and opportunity rules

Build your Intercom to Salesforce quote, one choice at a time

Entry pricing begins at $870.

One setup fee · Range shown first · PDF handover included

View Pricing
Pricing

Build your Intercom to Salesforce price

Pick a package, answer three short questions about how Intercom data should reach Salesforce, and your price and turnaround move as you choose.


Choose your packageRequired

The three packages differ by how much routing, reconciliation and governance sits around the Intercom to Salesforce route.

A focused production route for one Intercom environment and one Salesforce destination, delivering Intercom Salesforce integration that decides lead or contact, upserts on an external ID, logs each conversation as an activity and creates opportunities only when your rule is met with identity and failure controls from day one.

  • One approved Intercom event family and business-state admission rule within the Intercom to Salesforce service.
  • One authorized account, workspace, organization, or base boundary within the Intercom to Salesforce service.
  • One Salesforce object contract with field and relationship mapping within the Intercom to Salesforce service.
  • Stable matching through workspace ID plus contact ID and conversation ID and a Salesforce External ID mapped to the source identity
  • Tests for duplicates, stale events, malformed data, denied access, and timeouts within the Intercom to Salesforce service.
  • Implementation map, test record, and premium PDF operations handover within the Intercom to Salesforce service.

Adds branching, matching and a bounded historical pass for teams whose route into Salesforce cannot be one straight-through action, while still delivering Intercom Salesforce integration that decides lead or contact, upserts on an external ID, logs each conversation as an activity and creates opportunities only when your rule is met.

  • Everything in Launch
  • Up to four approved routing or state-transition branches within the Intercom to Salesforce service.
  • Existing-record resolution and one bounded historical checkpoint within the Intercom to Salesforce service.
  • Lookup-before-replay protection for uncertain writes
  • Named exception ownership and a decision-ready evidence packet within the Intercom to Salesforce service.
  • Field, permission, and destination-state validation before mutation within the Intercom to Salesforce service.

Adds reconciliation and governance for teams that now depend on Intercom Salesforce integration that decides lead or contact, upserts on an external ID, logs each conversation as an activity and creates opportunities only when your rule is met, with drift detection and an exception register for Salesforce.

  • Everything in Operations
  • Scheduled source-to-destination reconciliation
  • Schema, field, scope, and webhook drift checks within the Intercom to Salesforce service.
  • Volume-aware retry ceilings and stale-event protection
  • Aged-exception reporting with ownership status
  • Thirty-day release watch and operating review

For the Intercom to Salesforce service, multi-business-unit routing, unrestricted bidirectional synchronization, regulated archives, unsupported extensions, or additional destination systems receive a separate written quote. Third-party subscriptions and usage charges are excluded.

Which Intercom events should reach Salesforce?Required

Governed lifecycle set: Use this when several approved Intercom transitions must converge on one Salesforce record.

How should Salesforce recognize an Intercom record it has already handled?Required

Ambiguity queue: Route zero-match and multi-match cases to an owner instead of letting Salesforce guess.

Which Intercom events should reach Salesforce?Required

Managed repair case: Capture evidence, ownership and a safe next action whenever a Salesforce write is uncertain.

How soon do you need it live?Required

Standard follows the schedule your other choices set. Pay to move up the queue and go live sooner.

Optional extrasOptional

Each one begins switched off. Turn on what your rollout needs, watch the total, switch it back off.

06The process

Six steps from a first message to a Salesforce record reps rely on

Every step ends with something you can inspect: a map, a key, a test result or a signed note.

  1. Choose what counts

    We list the chat topics, plans and company details that justify a record, an activity or an opportunity, and the ones that justify none.

  2. Approve access

    The Intercom and Salesforce connections are configured with the narrowest permissions that work.

  3. Agree objects and rules

    The Lead-or-Contact rule, the external ID field, activity types and the opportunity criteria are written out and signed off.

  4. Rehearse the failures

    Duplicates, out-of-order events, blank values and timeouts are staged in a test area so the repairs are proven.

  5. Launch with notes

    The live route starts from a fixed boundary, followed by a handover PDF for your administrators.

  6. Settle in

    We watch the live route through its first cycle, compare both sides and tune thresholds where the data says to.

Handover for Intercom to Salesforce automation: notes, a checked run and a health checkHandover preparation: a checklist of what is settled, next to a rehearsal run with all test events passed and zero duplicates.Before we open your filesWhich event starts the syncWhich reports and fields it fillsHow far back to importWho owns an exceptionSet once, then it runsRehearsal run48/48test events passedDuplicates0Held1

07Turnaround

How fast each package runs

We start the clock when Intercom and Salesforce are ready for us.

Core

6 to 10 business days

Scale

10 to 16 business days

Stewardship

16 to 24 business days

08Before we start

Getting started: what you provide

The go-ahead to connect to Intercom with limited scope

A Salesforce org where an integration user can write to the agreed objects and fields, and Intercom access granted through a developer app

Read access to the Intercom objects this route depends on

A plain-language list of the conversation changes to include and exclude

The people who should be told when something fails

A time window in which testing can happen safely

09Security and ownership

Scoped access, small payloads, and no changes to either tool

The route reads what you approve in Intercom and writes only where you point it in Salesforce.

Published interfaces only

Every request goes through the public interfaces of Intercom and Salesforce. No core file, theme or application code is touched.

Scoped, revocable access

Access ends the moment you disconnect, with no lingering copies.

Data kept to the job

The lead carries the values the business needs and no more; the rest of the Intercom record is never copied across.

Retries that cannot duplicate

Every repair starts from an Intercom contact ID held in an external ID field on the Lead or Contact, plus the conversation ID on the activity and a read of Salesforce, so trying again is safe by construction.

Minimal logging

History is kept as outcomes and references, so a leak would reveal little.

Full handover

Nothing is rented back: the configuration and the notes transfer to you.

10In their words

What BoldBellows clients say

Verified reviews from operations and finance teams who trust BoldBellows to keep their data moving correctly.

AI Workflow Automation for Agencies

Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.

Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.

Samuel BoatengVerifiedAccra, Ghana

AI CRM Automation

Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.

Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.

David KimVerifiedSeoul, South Korea

AI Video & Voice Automation

We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.

The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.

Lucas SteinerVerifiedMunich, Germany

AI Email & Smart Inbox Management

Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.

It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.

Chloe AndersonVerifiedMelbourne, Australia

AI Booking & Scheduling Automation

Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.

No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.

Emily CarterVerifiedLondon, United Kingdom

AI Translation & Localisation

When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.

The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.

Kenji NakamuraVerifiedOsaka, Japan

AI HR & Recruitment Automation

Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.

It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.

Olivia MartinezVerifiedAustin, USA

AI Accounting & Invoice Automation

BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.

Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.

Ravi PatelVerifiedNew Delhi, India

AI Data Entry & Reporting Automation

We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.

The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.

Sarah MüllerVerifiedZurich, Switzerland

11FAQ

Intercom, Salesforce and lead capture: what revenue teams ask

Answers from real scoping conversations, so you can decide faster.

How is this different from an Intercom to Salesforce Zapier workflow?

For a Salesforce lead for each new chat alone, a basic zap is enough. What it will not do is decide between lead and contact, upsert on an external ID, log the conversation as an activity and open an opportunity only by rule. This build covers exactly what a basic connector leaves open.

How does Intercom lead capture work with Salesforce?

A chat with an email is matched to an existing Contact or Lead through the external ID and email, or created a single time, and the conversation is logged as an activity.

How does Intercom Salesforce contact create work for existing customers?

Yes. If the email belongs to an existing Contact, or your rule says the person is a customer, the route writes to the Contact and never creates a Lead.

How is an Intercom Salesforce opportunity decided?

By your written rule on topic, plan and account. Pricing or upgrade chats from a known account can open one, while support questions never do.

What if Salesforce duplicate rules block a record?

The block is recorded, the item goes to a named person with the matching record shown, and nothing is forced past the rule.

Which Intercom fields can be mapped?

Name, email, company, role, tags, custom attributes and the conversation topic, as long as a Salesforce field exists for them.

Does Salesforce data flow back to Intercom?

No. The route is one way, from Intercom to Salesforce, so a CRM edit never changes a conversation.

Who signs off the mapping?

Think of it as an Intercom Salesforce field mapping service with the results on paper.

Can different records take different paths?

Yes. You describe the logic, we build a custom Intercom workflow for Salesforce, and we advise as an Intercom Salesforce integration consultant along the way. From $870.

What if the interfaces change after launch in the Intercom to Salesforce route?

Nothing is silently patched. A platform change surfaces as a paused step with a clear reason, and remediation after your review window is quoted apart.

Next stepPut every customer chat on the Salesforce record that needs it

Give Salesforce the conversation behind every lead

Decide what a good result looks like in Salesforce; we take care of how you automate Intercom data to Salesforce to reach it. Pricing starts at $870.

  • From $870, paid once
  • External ID upsert
  • Activities logged
  • No monthly fee from us

Special requirements are handled as a separate quoted extension.