Enrichment on creation and on a schedule, and a sandbox that charges you to test.
ZoomInfo Sales with Enrich, the AppExchange package, and a Salesforce edition with API access
Contacts, Companies, Lists, one way, in.
This is the deepest enrichment integration in the directory and the one with the most ways to spend money you did not plan to. The capability is real: Instant Enrich fills a lead, contact or account as it is created, Scheduled Enrich keeps the back catalogue current, and you control matching, accuracy thresholds and field-level overwrite behaviour. What decides whether the project goes well is three documented details nobody mentions in a demo: a sandbox run charges credits exactly like production, the Person Has Moved setting rewrites employers unless you turn it off, and Instant Enrich spends two Salesforce API calls on every record it touches. That last allocation is shared with every other integration in the org, which is why this one usually gets discovered from somewhere else.
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 |
|---|---|---|
| New leads, contacts and accounts | One way, in | Instant Enrich appends ZoomInfo data as the record is created, optionally filtered by a SOQL query so only the right teams' records are enriched. |
| Existing records | One way, in | Scheduled Enrich jobs run on a cadence over all records, a list view, or criteria you define. Jobs begin at 12:00 AM Eastern on the scheduled day. |
| Intent and Scoops | One way, in | Written to a ZoomInfo custom object rather than onto the standard record. |
| Buying committee contacts | One way, in | Creates and enriches new contacts on matched accounts, charged as credits and reported separately on the dashboard. |
| Anything back to ZoomInfo | One way, out | Nothing on this integration. Enrich is a one-way pipe into Salesforce. |
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.
Mapping here is explicit and per field, which is unusually controllable. The thing to understand is not where a field lands but whether it is allowed to overwrite what is already there.
| In Salesforce | In ZoomInfo | What to know about the match |
|---|---|---|
| A ZoomInfo data point | Any Salesforce field, custom included | Chosen row by row, so nothing lands anywhere you did not pick. |
| Update Option | Overwrite, or complete only if missing | Set per mapping. This single column is the difference between enrichment that reps trust and enrichment they work around. |
| Intent and Scoops | A ZoomInfo custom object | Deliberately not written onto the standard record, so your reporting has to reach into the custom object to use them. |
| Buying committee contacts | New contacts on the matched account | Created rather than matched, and chargeable. A hard limit of up to 10 contacts per account is available and worth setting. |
| Anything at all | Back to ZoomInfo | Nothing. Enrich is a one-way pipe into Salesforce, so your corrections stay yours and never improve the source. |
Three 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: five field mappings and three documented exclusions, each one's note, and the two 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.
Work down the Update Option column before go-live rather than the field list: the mapping decides what arrives, and that column decides whether it is welcome.
ZoomInfo quotes its editions rather than publishing them, so the grid that decides this project is not licence against licence. It is which enrichment mode you run against which environment, because both sides meter you and only one of them is obvious. Pick one on each side and the grid marks the answer.
Pick one on each side.
| Enrich mode | Production | Sandbox |
|---|---|---|
| Instant Enrich, on create | Two API calls per record | Credits charged anyway |
| Scheduled Enrich, 200 per batch | Most Bulk API calls | Credits charged anyway |
| Scheduled Enrich, 10K per batch | Fewest Bulk API calls | Credits charged anyway |
Counted off that grid, of six pairings: one gives you two API calls per record, one gives you most Bulk API calls, one gives you fewest Bulk API calls, three give you credits charged anyway. The two meters do not move together, which is the trap: tuning the batch size down to be gentle on one system spends more of the other, and neither shows up on the invoice you were watching.
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.
Salesforce AppExchange: ZoomInfo, GTM Intelligence Platform
Click Get It Now and choose Production or Sandbox. ZoomInfo documents that running Enrich in a sandbox still consumes credits, so a sandbox trial is a real purchase rather than a free rehearsal.
Salesforce: Users
ZoomInfo asks you to connect as a user dedicated to Enrich. That user's permissions become the integration's permissions, and a named person's account takes the integration down with them when they leave.
ZoomInfo Admin Portal: Integrations, Connect Enrich
Under Scheduled Enrich, click Connect on the Salesforce tile, choose the environment and click Grant Access. The authorisation opens in a popup, so a popup blocker makes this look like a failed connection rather than a blocked window.
Admin Portal: Manage, New Job
A job takes a single Object Type of Accounts, Contacts or Leads. Name it, decide whether you want email alerts, and set the recurrence; jobs start at midnight, so a daily job is an overnight job.
The job: Credit Usage Limits
The default is No limit, which enriches every record in the run and charges for all of it. Limiting credits per job run is the setting that turns a misconfigured filter into a small mistake instead of a month of budget.
The job: Batch Size
The options are 10K, 1K, 500 and 200 records per Bulk API call. A larger batch means fewer calls; reducing it increases Salesforce API consumption, which matters because that allowance is shared with every other integration in the org.
The job: Accuracy Score for Enrichment
Records matched below the threshold are not enriched and are marked No Match with the reason Below selected Accuracy Score. That is a better outcome than a confident guess, and it is also the number somebody will use to judge the integration later.
The job: field mapping
Each row pairs a ZoomInfo field with a Salesforce field, custom fields included, and each has an Update Option of overwrite or complete only if missing. Default to complete if missing on anything a human types into.
Two of those eight are the whole project: the credit limit, which caps the downside, and the overwrite option, which decides whether reps keep trusting the record.
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/salesforce-zoominfo/SKILL.md https://www.reversecontact.com/integrations-hub/skills/salesforce-zoominfo.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.
WhyA popup blocker. ZoomInfo opens the Salesforce authorisation in a popup and says so.
Disable the blocker for the Admin Portal and reconnect. Nothing is wrong with the credentials.
WhyCredit Usage Limits defaults to No limit, so the job enriched every record it matched.
Set a per-run credit limit before the next schedule, and test any new filter against ten records first.
WhyA Salesforce contact with no account relationship is private to its creator, which is Salesforce behaviour rather than ZoomInfo behaviour.
Make sure created contacts attach to an account. Practitioners use a placeholder account everyone can see, or route to the Lead object instead.
WhyThey matched but fell below the accuracy threshold, and the reason field says so.
Read the reason before lowering the threshold. A lower score buys coverage with confidence, and that trade should be a decision rather than a reflex.
WhyAn Update Option set to overwrite on a field people type into, or Person Has Moved rewriting an employer.
Switch those mappings to complete only if missing, and check the Person Has Moved setting, which is on unless somebody turned it off.
WhySalesforce API consumption. Instant Enrich costs two calls per record and a small batch size multiplies scheduled calls, all drawn from one shared daily allowance.
Raise the batch size, narrow the job filters, and check the org's API usage rather than ZoomInfo's job log, because the failure appears somewhere else entirely.
WhySome capabilities need the ZoomInfo Sales native application at version 1.33 or higher.
Upgrade the AppExchange package before raising a support ticket about a missing screen.
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 this pair by name, in the words a person would use. 14 threads from 2018 to 2026 were read in full on 11 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.
You can create a contact without an account relationship, but the issue is I believe (off hand) that when there is no account assigned, the contact is seen as private to the creating user and not visible to others (outside of view all and modify all).
r/salesforce·May 2024·5 points
Salesforce behaviour rather than ZoomInfo behaviour, and it is the one that makes a successful enrichment run look like a failed one. The reply underneath suggests a placeholder account everyone can access, or using the Lead object instead.
You do not own the contacts from them and they will actively try to sue you if you keep the contacts after your contracts expires and you don't renew.
r/salesforce·February 2025·4 points
One practitioner's account of their own agreement, not a published term, and this directory is not going to assert it as one. It is worth raising because it is checkable: data ownership after termination is a clause in your contract, and the time to read it is before you write that data across every record in the CRM.
I feel like you need to have an actual conversation with your account manager about what the business needs. Everything you described is doable with zoominfo but you have to let them know you need this
r/sales·September 2025·4 points
Consistent with a vendor that quotes rather than publishes. It also means a capability gap you hit on this page may be a commercial question rather than a technical one, which is a different meeting and a different budget.
My company is on an older instance of SFDC, but they are saying that it will take "months" to integrate ZoomInfo with SFDC. I'm calling BS.
r/salesforce·February 2018·5 points
Mostly right, and the instinct is still correct eight years later: the package install is an afternoon. What takes a quarter is agreeing the field mapping, the overwrite rules and the accuracy threshold, which is organisational work wearing a technical costume.
My new company just assigned me around 400 new accounts however none of them have any up to date contacts listed. It would take me at least 2 months to manually enter all these contacts.
r/salesforce·April 2021·4 points
A clean statement of the value, and the reason the credit limit matters: the same impulse that makes 400 accounts worth enriching makes 40,000 look tempting at two in the morning.
Two topics dominate and neither is the integration itself. One is Salesforce's own object model getting in the way of contacts ZoomInfo creates. The other is commercial: what the data costs, what you are allowed to keep, and whether the account manager has to be in the room for you to get what you are paying for. The mechanics, by contrast, barely come up, which fits a package install that works.
Nothing in the threads suggests the integration fails. The complaints are about what it writes, what it costs and what you are allowed to keep, which is where the settings above are pointed.
The configuration that decides whether this project is remembered fondly is field mapping, and ZoomInfo's own recommendation is the right one: set every standard Salesforce field to Complete if missing, which is the default, and reserve Overwrite for custom fields created specifically for ZoomInfo. That single rule prevents the argument that otherwise arrives in month three, when a rep finds a title they corrected has been replaced by a machine. Give the external source its own properties, then let a Salesforce admin decide with a flow or a formula what gets promoted into the fields people trust.
The accuracy threshold is the second control worth understanding before the first job, because it changes what a failure looks like. Set a minimum accuracy score and matched records that fall below it are not enriched and are marked No Match with the reason "Below selected Accuracy Score". That is a much better outcome than a confident guess, and it is also a number that will appear in a dashboard someone uses to judge the integration. Agree what the threshold is and why, so the match rate conversation happens once rather than every month.
None of this is unique to ZoomInfo, which is the useful thing to take from the page. Every enrichment integration in the data layer raises the same three questions: which fields may it own, how confident must it be before it writes, and what happens when the person has moved on. The difference here is that ZoomInfo exposes all three as settings and documents what the defaults do, which is more than most. If the Salesforce edition or the credit model is the obstacle rather than the data, the same job can be assembled through the Salesforce data layer build, with a different cost shape and considerably more work.
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 Salesforce, ZoomInfo 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.
Enrich is a feature of ZoomInfo Sales, so the edition is the purchase and the connector is free. On the Salesforce side you install the ZoomInfo native application from the AppExchange, which ships the managed ZoomInfo Contact ID and Company ID fields that mapping depends on, and you grant the connecting user API Enabled, Apex REST Services, Customize Application, View Setup and Configuration, read and write on Account, Contact and Lead, and field-level security on every field you intend to map.
Instant Enrich fills a lead, contact or account at the moment it is created in Salesforce, which is the half that changes how routing works. Scheduled Enrich runs jobs on a cadence over records that already exist, so the back catalogue does not stay stale while new rows get the good treatment. They are configured separately and most teams need both, for different reasons.
Yes, and this is the most expensive surprise on the pair. ZoomInfo documents that using Enrich in a sandbox incurs bulk credit charges exactly as production does, and recommends testing in small batches. A full-volume rehearsal against a sandbox copy of your database is therefore a real invoice, not a dry run. Plan the test as a sample and talk to your implementation specialist before pointing a job at everything.
By default, yes. The Person Has Moved setting is enabled unless you disable it, and when ZoomInfo sees that somebody has changed organisations it enriches the record to the new one. Disable it and the person's record keeps the old company while the company fields are still enriched as though they had not moved, with the status set to Company Match Only. Neither behaviour is wrong, but one of them silently rewrites who your contacts work for, so decide deliberately before the first job runs.
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.