Gong Enrich names six data partners. Reverse Contact is not one of them, and bring your own key does not change that.
A Gong technical administrator to create API credentials, a Reverse Contact API key, and somewhere to run the lookup
Activities, Contacts, Companies, one way, out.
Gong knows exactly who was on the call and surprisingly little about them. Its own Enrich feature closes part of that gap with a waterfall over six named data partners, and Reverse Contact is not one of them, so this is an API build rather than a configuration. The fact worth the whole page is what Gong Enrich does when somebody has changed job: it checks, finds they have left, stops before querying anybody, and charges nothing. You learn that the record is wrong and not what it should say instead.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| The calls | One way, out | GET the calls for a date range, then read the internal and external participants on each. |
| The external participants | One way, out | Email addresses that may belong to nobody in your CRM, which is the gap this build exists to close. |
| The lookup | One way, out | POST /v2/enrich/persons on each external address. 2 credits on a match, nothing on an error. |
| The write | One way, in | To the CRM Gong already reads, or through Gong's own CRM upload endpoint if there is no CRM. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
There is nothing to map inside Gong, because the build reads from it rather than writing to it. What is worth laying out is which part of a call Gong hands you, which part of a person Reverse Contact hands back, and where the two meet, which is almost always a CRM record rather than either product.
| In Gong | In Reverse Contact | What to know about the match |
|---|---|---|
| A call, by date range | The Gong calls endpoint, cursor paged | One of 10,000 company-wide calls a day at 3 a second. The records field carries the page and the total, and a cursor arrives when there is more. |
| External participants on that call | Email addresses, and little else | Gong returns internal and external participants along with topics, trackers, public comments, scorecards and transcripts. An external participant who matches nothing in the CRM is the subject of this page. |
| That email address | POST /v2/enrich/persons, 2 credits | Identity, the current role, the history and the company behind it on one schema. A miss returns null with a confidence score and costs nothing. |
| The domain of that address | POST /v2/enrich/companies, 2 credits | Firmographics from a domain. A meeting booked from a personal address has no useful domain, which is the case where the person lookup is the only route to the account. |
| currentPosition.companyName | A comparison against the filed account | The one row on this table that justifies the build. Gong tells you the contact has left; this tells you where they went. |
| currentPosition.title and seniority | The CRM contact record | Who was actually in the room, in the terms a pipeline review uses. Gong has the attendance and not the seniority. |
| The resolved contact | Your CRM, which Gong already reads | One copy of the answer, no Gong calls spent, and it survives replacing the recorder. Gong's CRM upload endpoint is for the case where there is no CRM at all. |
| Anything outbound to Reverse Contact | Only the identifier you send | This is a read layer. No call, transcript or recording is sent anywhere, and there is nothing in the product to send it to. |
Gong is extremely good at the conversation and deliberately thin on the participant, and the split is not obvious from the outside. Each row below is something a pipeline review asks about an external attendee, with where the answer actually comes from.
| The question | Where the answer comes from |
|---|---|
| Were they on the call, and for how long | Gong, in detail. Internal and external participants are part of what the API is documented to return, alongside topics, trackers, scorecards and the transcript |
| What is their email address | Gong, if they were invited by it. Gong Enrich exists precisely because sometimes they were not, and that is the gap it is built for |
| What is their job title | Gong Enrich can make it available as related contact information, or a reverse lookup returns it with the rest of the record. Not something the call itself carries |
| Do they still work there | Gong Enrich checks this and uses it as a stop condition rather than as an answer. It will tell you no and then stop |
| If not, where did they go | Reverse Contact, from the same email address. This is the question Gong's own enrichment is designed not to answer, because answering it is not what a contact-details waterfall is for |
| How senior are they, and who do they report to | Neither, reliably. The response carries seniority and position history; reporting lines are not published by anybody here and should not be inferred from a follower count |
A few things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, six the question rows and four documented exclusions, each one's note, and the twelve vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
Read the fourth and fifth rows together, because they are the page in two lines: Gong establishes that the record is wrong and stops, and a reverse lookup on the same address says what it should be instead. Everything else on this table is a reason to do the work in the CRM rather than in either product.
Gong is the only partner in this directory that ships its own enrichment waterfall, which makes the comparison here a comparison of products rather than of plans. Every figure and every partner name below is from Gong's own documentation, and the first column is the one that explains why this page is an API page. Pick one on each side and the grid marks the answer.
Pick one on each side.
| The route | Reverse Contact can be the provider | A job change says where they went | A miss costs nothing | The answer reaches the Gong record |
|---|---|---|---|---|
| Gong Enrich, a partner on Gong credits | No | No | Partly | Yes |
| Gong Enrich, a partner on your own key | No | No | Partly | Yes |
| Reverse Contact through the Gong API | Yes | Yes | Yes | Partly |
| The CRM enriched, Gong reading it | Yes | Yes | Yes | Yes |
Counted off that grid, of sixteen pairings: nine give you yes, three give you partly, four give you no. The second column is the finding and it is worth stating plainly on a page the publisher of this directory pays for: Gong's own enrichment does detect that somebody has changed job, and then stops, because finding the new employer is not what a contact-details waterfall is for. The bottom row is best on every count and is also the least interesting build on this page, which is usually how it goes: enrich the CRM, let Gong read it, and touch the Gong API only for the participants that never reach a CRM at all.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
Gong: Admin center > Data enrichment
Gong states that once Enrich is enabled it cannot be disabled, though manual and flow permissions can be withdrawn afterwards. It is a separate question from this build and a cheaper answer to a narrower problem, so decide it deliberately rather than while looking for something else.
Gong: whatever is already connected
The limit is 3 calls a second and 10,000 a day for the company, not for your integration. Before designing a sweep, find out what the CRM sync, the BI export and anything else are already spending, because this is the one number on the page that somebody else can exhaust for you.
Gong: the API page, app.gong.io/company/api
You get an Access Key and an Access Key Secret, combined with a colon and base64 encoded for a Basic Authorization header, or a bearer token through the OAuth flow. The base URL is per company and is shown on the API authentication page rather than being a constant you can hard-code.
Gong: the calls endpoints, with the cursor
A list response carries a records field with the page size, the page number and the total, plus a cursor when there is more. Repeat the call with that cursor and change nothing else, and remember that Gong may add JSON fields without warning so ignore what you do not use.
Your middle layer
The internal ones are your colleagues and enriching them is a waste of credits and slightly rude. The external ones are the point, and the subset worth paying for is narrower still: the addresses that match nothing you already hold.
POST /v2/fetch/persons/check
The free check says whether a profile is cached and when it was last updated, so a sweep over a quarter of calls spends 2 credits only where the answer is genuinely new. Errors cost nothing either, which is the opposite of how the Gong side of this works.
Your middle layer
This is the whole reason to do this rather than use Enrich. When Gong decides a contact has left the account it stops and tells you nothing further; a reverse lookup on the same address returns the current position, which is where they went. One comparison, and it is the most valuable line of code in the build.
Your CRM, through its own API
Gong already reads the CRM, so writing there gives one copy of the answer, costs none of the daily Gong allowance and survives a change of recorder. Gong's API can take CRM data if there is genuinely no CRM, and that is the only case where pushing into Gong is the right move.
Your middle layer, with a limit on it
A quarter tells you how many external participants a call actually has, how many of them are unknown, and therefore what the archive would cost in both credits and Gong calls. At 10,000 calls a day for the company, that arithmetic decides whether a backfill is a weekend or a month.
The first step is irreversible and unrelated to everything after it, which is an awkward combination: somebody evaluating this build can accidentally commit the company to a feature while looking at a different one. The seventh step is the one that earns the work, and it is three lines rather than an integration.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/gong-reverse-contact/SKILL.md https://www.reversecontact.com/integrations-hub/skills/gong-reverse-contact.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyGong Enrich supports LeadIQ, Wiza, RocketReach, Lusha, ZoomInfo and Findymail, and the list is not extensible by the customer.
Stop looking for it and build on the API instead, or enrich the CRM and let Gong read it. Bring your own key will not help, because it attaches a credential to a partner that is already on the list.
WhyGong checks whether the contact still works at the company on their record before querying any partner, and stops if they do not, using no credits.
That is the designed behaviour and it is also your signal. Take the same address to a reverse lookup, which returns the current position, and treat the Gong result as a trigger rather than as a dead end.
WhyReturned addresses are validated and a failing one is discarded, and Gong charges the credit anyway because the partner returned data.
Order the waterfall with the most accurate provider first rather than the cheapest, since a wrong answer costs the same as a right one. Nothing on the Gong side refunds it.
WhyWithin 90 days Enrich skips data partners it has already queried for that contact, so a second attempt may have nobody left to ask.
Wait for the 90 days, add a partner that has not been tried, or go round it with a lookup of your own. The second attempt is not a retry of the first.
WhyThe limit is 3 calls a second and 10,000 a day at company level, shared with every other integration connected to Gong.
Honour Retry-After, and find out what the CRM sync and any BI export are spending before scheduling a sweep. Gong says support can raise the limits if required, which is a conversation rather than a setting.
WhyList endpoints page with a cursor, and a response carries a records field with the page size, page number and total.
Repeat the request with the cursor from the previous response and change nothing else. Compare the rows you processed against the total in the records field before believing any run.
WhyGong's enrichment controls carry settings to exclude people located in the European Union and people in California.
Check the exclusion settings before concluding anything about coverage. This is a configured policy rather than a gap in anybody's database.
WhyReverse Contact replaced /v2/resolve with /v2/enrich and /v2/search/persons with /v2/search/people, with the old pair documented as live only until 13 October 2026.
Change both paths in the middle layer. Gong separately warns that it may add JSON fields without notice, so a reader that ignores unknown fields survives both kinds of change.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2023 to 2026 were read in full on 28 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
I cannot see how good your crm hygiene is, this could lead to updates among multiple situations and make you worse off. A job title is not a real issue unless you want it for signal usage. If you want it as a signal, use it like that, and don't automate an update on it.
r/Dynamics365·September 2026·5 points
The best piece of advice in this harvest and a check on the rest of the directory, which usually assumes an enriched value should be written. The distinction is between a fact you act on once, such as this person has moved, and a field you overwrite on a schedule. The comparison in step seven above is a signal in exactly this sense, which is why it belongs in a branch rather than in a field mapping.
I would not make Claude the integration layer or source of workflow state. Let it interpret the request and propose a plan, but use scoped adapters and deterministic services to retrieve records, enforce permissions, validate identifiers, and perform any approved action. Treat CRM fields and transcripts as untrusted data, never as agent instructions.
r/Dynamics365·September 2026·1 points
Written about an agent stack across Dynamics, Gong and ZoomInfo, which is close enough to this page to transfer directly. It matters more here than on most pairs because Gong holds transcripts, and a transcript is the one thing in a sales stack that is both unstructured and written by somebody outside your company. The second half is the reason the build above never reads one.
I've previously purchased Gong whilst at a Series B > D company and I really liked it, but it's difficult to get the full value out of the CI without other teams being willing to use the data that you can grab out of it. [...] I would start on what you plan to utilise rather than the wholesale features a platform has
r/SalesOperations·August 2023·1 points
The honest frame for any build on top of a recorder, and a reason to be suspicious of this one. Resolving every external participant on every call is easy to justify and easy to leave unused, so the test in the verify list is whether the account reaches a record a human looks at rather than a log. Start from what somebody will do with it, which is this comment's advice and good discipline.
It's nice as well because it pulls up for us our prospect info, previous emails, LinkedIn profile, as well as title and job history.
r/salesdevelopment·April 2025·2 points
A dialer user listing what they value, and every item is a field rather than an insight: who, where, what they do now, what they did before. That is the shape of a reverse lookup response almost exactly, and it is a reminder that the output of this build is most useful before a call rather than after one, which the sequencer pages in this directory argue at more length.
Fathom records, summarizes, action points, next steps. Integrates with crms directly etc. Zapier is if you'd like to build automations with that data
r/sales·September 2025·5 points
Said about a cheaper recorder and true of the expensive one too. The division of labour is the same as on every page here: the tool that captures the conversation is not the tool that enriches the participant, and the join is an orchestrator or an API. Worth noting that this whole thread is a group of people talking somebody out of a large recorder purchase, which is the market Gong Enrich is defending.
Nobody discusses this pair by name, so the search was for the job: getting usable facts about the people on a recorded call. The threads are mostly about choosing a conversation intelligence tool, and the useful ones are about what happens to the data afterwards. The best contribution is a warning about automating a field update from an enrichment, which is advice this page needed and does not give itself.
Nobody in this harvest is enriching call participants, which is itself the finding: the discussion is still about which recorder to buy. The one to act on is the first, because it draws the line this page cares about between a field you overwrite and a signal you act on once, and a job change is firmly the second.
A recorder knows who was in the room and almost nothing about them. An external participant arrives as an email address on a calendar invite, and if that address matches nothing in the CRM then the most expensive conversation your company had this week is attached to a person nobody can describe. That is the gap on this page, and it is narrower and more specific than the gap on most pages here.
Gong has closed part of it already, which this page has to say plainly because the publisher of this directory is the alternative. Gong Enrich runs a waterfall over six named partners for email and phone, charges only when one returns data, and enriches the associated account for nothing. What it does not do is tell you about the person: the role, the history and the company behind a contact who has moved are not what a contact-details waterfall is for.
So the honest build is the dullest one, and it is the fourth row of the grid below. Enrich the record in the CRM that Gong already reads, which keeps one copy of the answer and spends none of the 10,000 daily Gong calls. That is the same conclusion the Salesforce page reaches from the other direction, and the Gong API is worth touching only for the participants that never reach a CRM at all.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Gong, Reverse Contact and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
No, and the reason is sharper than usual. Gong has its own enrichment feature with a configurable provider waterfall, and it names the supported partners: LeadIQ, Wiza, RocketReach, Lusha, ZoomInfo and Findymail. Reverse Contact is not on that list, so there is no place to put it inside Gong and the route is the Gong API instead.
No. Bring your own key is a credential swap for a partner Gong already supports: you hover over the data partner row, click the key icon and enter your API key for that provider. It changes who bills you rather than which providers are available, so an unsupported provider has no row to put a key on.
Email addresses and phone numbers, with related account and contact information such as industry, company details, title and LinkedIn information available alongside. Credits are consumed when a partner returns an email or a phone number; account enrichment consumes none. It is a contact-details waterfall rather than a record enrichment, which is why this page is about the half it does not cover.
Three API calls a second and 10,000 a day, at company level rather than per integration, so every tool you have connected to Gong is spending the same allowance. Exceeding it returns 429 with a Retry-After header, and Gong says to contact support if the limits need changing.
In your CRM, which Gong already reads. Writing it there instead of pushing it into Gong keeps one copy of the answer, survives a change of conversation intelligence tool, and spends none of the 10,000 daily Gong calls. That is the fourth row of the grid below and it is the recommendation on this page.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.