How to link a Gong call to the Intercom conversation from the same customer

There's no native connector between Gong and Intercom, so nothing links a call to a support conversation for you automatically. But the two systems don't need to hand each other an identifier for this to work: on any call worth flagging, the rep already knows who they're talking to and what email reaches that person, and it's the same email Intercom already indexes every conversation by. Linking a call to a conversation from the same person is a search, not an integration, and it takes under a minute once you know to do it.

The part that doesn't happen on its own is remembering to do it. A rep hears something worth flagging on a call, and the natural next step, typing a Slack message or moving on to the next agenda item, doesn't touch Intercom at all. Below is exactly how the match works today, a manual routine that holds up at low volume, and the point where teams doing this by hand start losing mentions they don't even know they lost.

How Gong and Intercom each handle the same person

Gong doesn't fingerprint a caller's voice to figure out who they are. Per Gong's own documentation on how it identifies speakers, the system matches the name a participant enters when they join, or the phone number they dial in from, against the invite list for that meeting. That's enough to label the transcript by name; Gong's docs don't describe email as part of the matching step. Where email comes in is the CRM side: Gong's Salesforce export documentation says a call only exports "when at least one external participant matches a Salesforce contact or lead," which is the account's existing contact record, email included, that a rep working that account already has open.

That same call is searchable inside Gong directly by name. The call search filters include Participants and Account name, so pulling up every call a specific person or company has been on doesn't require the CRM step at all, just the search bar under Conversations.

Intercom's side of the match is more direct. Per the inbox search documentation, typing an email address straight into the inbox search bar, no filter needed, returns every conversation tied to that person. A company-level search works the same way through the Company filter, returning conversations "explicitly associated" with that company plus any conversation involving at least one participant from it.

So the piece that actually needs to move between the two systems isn't anything either one generates for you, it's the email a rep already has from the CRM contact record or from the invite they sent to book the call in the first place. Gong tells you who was on a call and finds it again by name. Intercom finds every conversation with that person the moment that email hits its search bar. Nobody has to invent an identifier; someone has to remember to carry the one they already have from one search bar to the other.

The renewal call at Windmere Payments

Windmere Payments sells invoicing and reconciliation software to mid-market logistics companies. Tobias Renn is one of seven CS reps there, each carrying around thirty accounts, which puts him on four or five calls most days. On a regular check-in call with Bexley Rail, recorded in Gong, their ops lead Jonas Weir raises something in passing near the end of the agenda, after Tobias has already worked through two other renewal calls that morning.

Jonas Weir: One thing that's still annoying us, when we process a batch of refunds after a service credit, we're doing it one at a time through the UI. Is there a CSV upload for that anywhere?

Tobias: Not today, that's export-only right now. I'll pass it along.

Tobias types a line into the account's internal notes doc and moves to the next call on his calendar. He doesn't open Intercom, because nothing about a Gong call points him there, and by the end of the day he's taken three more calls on top of this one.

Three weeks later, Jonas opens an Intercom conversation with Windmere support, this time asking almost the same question in different words: "Is there any way to bulk-process refunds instead of doing them one by one?" Farideh Kasrai, who runs support and lives in the inbox all day, answers honestly that it's not supported yet and logs it as a request. She has no reason to know Jonas already raised this on a call Tobias sat in on, one of dozens Tobias took that month. To Farideh, it's one conversation from one account. To Windmere as a whole, it's the same person asking twice, three weeks apart, and neither system is the one that would have caught it.

Three ways to close that gap by hand

None of this requires new tooling, just a habit applied at the moment it matters:

• Search Intercom by the caller's email right after a call worth flagging. If Jonas's email is already in Windmere's Intercom, the search bar shows every conversation he's had, immediately surfacing whether this is a repeat.
• Clip the moment and drop it into an Intercom note. Gong's snippet feature lets you select a piece of a call from the transcript or timeline and share it internally, per Gong's own docs. Whatever that share action hands you, drop it into an internal note on the matching Intercom conversation, visible only to teammates, so a support rep has the original quote without asking the customer to repeat themselves.
• Tag Gong-sourced mentions with the account name, every time, no exceptions. A rep typing "customer asked about bulk refunds" into an internal doc is exactly the failure mode, no name and no way to search for it later. The account name has to survive the trip out of the call.

This works as long as one person remembers to do it for every call. That's also its entire failure mode.

Where the habit stops working

At a handful of flagged calls a month, one attentive CS lead has time to search Intercom after each one and catches nearly everything. Past a few dozen a month spread across a team of reps, each juggling their own thirty-account book, the habit gets uneven. Some reps search Intercom every time, some skip it on their busiest days, and nobody is checking whether Jonas's second mention got connected to his first. The two systems didn't get any less compatible; there's just more volume moving through more reps than one habit can carry without cracks.

That's the point where reading both sources directly, instead of relying on someone to search and paste, starts to pay for itself. Modem ingests Gong call transcripts and Intercom conversations as two of its sources, and matches each call and conversation to the same person and company across your other sources, the way Modem's Gong integration and Intercom integration each describe independently. Calls and conversations are ingested, classified, and grouped with everything else Modem already knows about that person. When Jonas's call and his Intercom message describe the same ask, Modem merges them into one topic with both quotes attached, instead of two separate signals that only connect if a human happens to notice. Modem is what we sell, which is exactly why the comparison above matters: a habit one CS lead can run by hand at Windmere's current call volume beats installing a tool to do it. The trade only flips once the searching itself starts getting skipped, and that's a rep-count-and-volume problem, not a Gong-versus-Intercom one.

Two related guides worth reading next: how to keep the customer account attached to a feature request after it leaves Gong, on the account and deal-size half of this same problem, and the best tools to mine feedback from Intercom conversations, for teams weighing options on the Intercom side specifically.

The one rule that catches most of it

Pick one rule and enforce it starting with the next call. Any time a customer raises something worth flagging, search Intercom for that person's email before typing the write-up anywhere else. It costs thirty seconds, and it's the single step that would have told Farideh that Jonas had already said this once, on a call she never saw.