We put a question box in the deal record instead of stuffing Gong values into fields

Field Note · Andrew O'Driscoll, Founder, RevOps Sherpas · Jul 2026 · 6 min read

We stopped syncing Gong values into Zoho CRM fields and built a question box in the deal record using Gong's MCP server. Why asking beats field-stuffing.

One common way to get Gong into a CRM is to pick a set of fields, map Gong's output to them, and sync on a schedule. Next steps. Competitor mentioned. Stakeholder coverage. The rep opens the deal, reads the value, and moves on.

We did this for a client recently, and then we stopped. Instead of pushing Gong values into their Zoho CRM fields, we put a question box in the deal record.

It's a panel inside the deal, wired to Gong's MCP server. The rep opens the deal and asks. "What are the deal risks." "What is the current status of this deal." "What are the next steps." Gong analyzes the calls and emails linked to that deal and answers in plain language, at the moment the question is asked. Nothing gets written into a field to make it work. No mapping, no sync, no dropdown compressing a competitive threat into a picklist value.

This is a small build. But it changes something we'd stopped noticing was a problem.

What a field can't do

A CRM field holds a value. That's its whole job, and for a lot of what a revenue team does, a value is exactly right. Amount, stage, close date — you want those pinned down, reportable, the same for everyone looking at them.

The trouble starts when you try to make a field hold something that isn't a value. "What's the risk on this deal" is not a value. It's a question with a paragraph behind it: a hesitation on the last call, a champion who went quiet, a budget caveat buried in an email thread. Reduce that to a "Risk Level: Medium" dropdown and you've thrown away the part that mattered. You kept the label and lost the reason.

Every field is also a question somebody chose in advance. Someone sat down months ago, guessed what the team would want to know, and built a field for it. Anything they didn't anticipate isn't there, and a rep can't ask the record for it. That is how organizations end up with hundreds of custom fields, each one a fossil of a question asked once, most of them empty most of the time.

This matters most on a CRM Gong doesn't natively support. On Zoho, NetSuite, or Bullhorn there's no out-of-the-box way to write Gong values back into your fields, so every one of those guessed-at fields is a custom integration to build and keep running. The cost of guessing wrong is higher exactly where the guessing is hardest to undo.

A question box doesn't need the guess. You ask what you want to know when you want to know it, and the answer is computed against the calls and emails on the deal right then.

Why this is possible now

None of this worked cleanly a year ago. What changed is that Gong ships MCP support.

MCP — the Model Context Protocol — is a supported, standard way for an application to ask a model a question and get an answer grounded in real data. Gong exposing an MCP server means we can send a natural-language question from inside Zoho and have Gong answer it from the actual interactions on the deal, rather than screen-scraping, rather than maintaining a brittle field-sync job, rather than shipping the transcript somewhere else and hoping the context comes along with it.

That last part is the whole game. You can paste a single Gong transcript into a chat tool and get a decent read of one call. What you can't do that way is join that call to the CRM record, the email thread, the prior calls, the deal stage. Gong's value was never the transcript on its own. It's the transcript joined to everything around it. MCP lets that joined context stay where it lives and still be queryable from the CRM.

Meeting the rep where they work

There's a quieter reason this matters, and it has nothing to do with data models.

Reps are drowning in systems. Gong wants to be where they work. The CRM wants to be where they work. Every tool in the stack is asking for attention, and the rep is caught in the middle deciding where to actually do the job. A field sync is one answer to that tension: pull Gong's insight into the CRM so the rep doesn't have to leave. But a synced field only answers the one question it was built for, and it answers it whether or not that's the question the rep has today.

A question box in the deal record is a different answer to the same tension. The rep stays in the CRM, in the deal they already have open, and asks whatever they need. The insight comes to them, in the place they were already standing, shaped to the question they actually have.

Where this goes

Amit Bendov, Gong's CEO, wrote last week that "have AI update my CRM" is one of the most requested things they hear, and that the request will eventually fade. His argument is that the interactions themselves become the thing you query directly, and the fields stop mattering as the system of record.

We think he's right, and the panel we built is one version of what that looks like once it's running in a real deal record. It doesn't retire anyone's custom fields. Amount, stage, and close date are still fields, and should be. What it retires is the reflex to turn every question into a field and every answer into a value.

Nobody is deleting 600 custom fields this quarter. But it's worth asking which of them a rep would still open if they could just ask the deal directly. If your team could ask their pipeline anything this morning, what would they ask first?

RevOps Sherpas is a Gong Gold Tier partner. We build CRM Connect integrations for Gong across Zoho, NetSuite, Bullhorn, SugarAI (formerly SugarCRM), and other non-native CRMs. If you're thinking about how Gong and your CRM should actually talk to each other, that's the work we do.

Tags: Gong, Zoho, MCP, CRM Connect