Gong is the leading revenue intelligence platform, and for good reason. It records calls and video meetings, transcribes them, analyses talk patterns and topics, and surfaces coaching and forecasting insights across a whole sales organisation.
It is exceptionally good at that. The question worth asking is what happens to the conversations it never sees.
How Gong captures
Gong's model depends on integrations with systems that already produce recordings:
- Telephony and dialler platforms
- Zoom, Teams, Google Meet
- Email and calendar for context
- CRM for opportunity association
Each of these hands Gong a clean recording plus structured metadata about who was on it and which deal it belongs to. That is what makes the analysis possible at scale.
A face-to-face conversation produces none of that. There is no platform, no automatic recording, no metadata. It simply does not enter the system.
Why the gap matters more than it appears
For a fully remote sales team, this is not a problem — Gong sees essentially everything.
But for teams whose sales motion includes field visits, customer sites and industry events, the consequence is subtler and more serious than "some conversations are missing." It is that the analysis is systematically biased toward the remote portion of the process.
If Gong shows that deals correlate with certain call patterns, that finding is drawn only from calls. If the decisive conversation happened at a customer's factory or a trade show booth, it contributed nothing to the model — while contributing heavily to the outcome.
In sectors where in-person selling dominates — industrial, medtech, construction — that blind spot can cover the most important conversations in the cycle.
They are not competitors
It is worth being clear about this, because the comparison is often framed wrongly.
| Gong | Event lead capture | |
|---|---|---|
| Where in the funnel | Existing opportunities | Before the CRM record exists |
| Primary purpose | Coaching, forecasting, deal intelligence | Creating qualified leads |
| Input | Recorded calls and video meetings | In-person conversations |
| Output | Insights across many conversations | Structured fields on one lead |
| Who uses it | Sales leadership, enablement | Reps at a booth |
Gong analyses conversations inside the pipeline. Event capture creates the pipeline. Many organisations run both, with event capture producing the opportunities Gong later analyses.
Can you upload in-person recordings?
Gong supports audio import, so in principle a separately captured conversation can be added and associated with an opportunity.
The practical constraint is upstream: something has to capture it first, at usable quality, in an environment Gong's integrations do not reach. A phone in a pocket at a trade show does not produce a usable recording — the acoustic problem discussed in our Otter comparison applies fully.
So the question is less "can Gong ingest this" and more "what captures it in the first place."
Closing the gap
For organisations with significant in-person selling, the sensible architecture is:
- Event and field conversations captured by hardware designed for that environment, producing structured CRM fields
- Calls and video meetings captured by Gong through its native integrations
- Both associated with the same CRM opportunity
That gives revenue intelligence a more complete picture, and it means the field conversations that actually decide industrial and medtech deals stop being invisible.
Confee addresses the first layer — a beamforming array built for noisy in-person environments, extracting structured fields into the CRM. It is not a revenue intelligence platform and does not compete with one.
The consent question is different too
Worth noting because it catches teams out.
Gong operates within a company's own systems, and consent is typically handled through call-recording notices and internal policy. In-person capture at a trade show involves members of the public in varying jurisdictions, which is a materially different legal analysis — see our guides for Germany, the US and others.
An organisation comfortable with its Gong compliance posture should not assume it transfers to booth recording. It does not.
The short version
Gong does not capture in-person meetings, because its model depends on platforms that produce recordings automatically and face-to-face conversations produce none.
For remote-heavy teams that is fine. For teams selling at customer sites and trade shows, it leaves the most consequential conversations outside the revenue data entirely — and the fix is capture, not analysis.
Related reading:
- Best AI Meeting Recorder for In-Person Meetings — the capture layer
- Otter.ai Alternative for In-Person Meetings — the acoustic problem
- How to Record In-Person Sales Meetings — practical mechanics
FAQ
Does Gong work for in-person meetings?
Not natively. Gong's capture relies on integrations with telephony and video platforms that produce recordings automatically. A face-to-face conversation produces none, so it never enters the platform unless captured separately and uploaded.
Why does the in-person gap matter for revenue intelligence?
It biases the data. If Gong analyses every call but no field conversation, the picture of what drives deals reflects only the remote portion — a substantial blind spot for field-heavy sectors.
Can you upload in-person recordings to Gong?
Gong supports audio import, so it is possible in principle. The constraint is upstream — something must capture the conversation at usable quality first.
Is Gong a competitor to trade show lead capture tools?
Not really. Gong analyses conversations within existing opportunities; event capture creates records for prospects not yet in the CRM. Many organisations use both.