A Practical Guide to ServiceNow CRM Data Enrichment

Enrichment done well makes ServiceNow the system of record your revenue team actually trusts. Done carelessly, it overwrites good data with bad, burns API credits on records that didn't need refreshing, and creates a new category of data-quality complaints. This guide walks through the setup decisions that separate the two.

Before you install anything

Answer these three questions first:

Which records matter most? Enrichment capacity is finite. Open accounts with active opportunities deserve fresh data far more than accounts with no activity in two years.
What does "good" look like per field? Define which fields must be populated, which are nice-to-have, and which should never be touched by automation (more on that below).
Who arbitrates conflicts? When enrichment says one thing and a rep's direct conversation says another, the rep must win—and the process needs a way to make that stick.

Field mapping: the decisions that matter

Protect the human-entered fields

Nothing destroys trust in enrichment faster than a system overwriting a phone number a rep just confirmed on a call. Configure write protection: if a user updated a field more recently than the enrichment source, don't overwrite it. Most enrichment apps support this pattern—use it.

Map to your existing schema

Resist the temptation to create a parallel set of "enriched_" fields for everything. Duplicated fields split reporting and confuse users. The standard account and contact fields—industry, employee count, revenue band, title—are where enriched data belongs, so dashboards built on them light up immediately.

Keep a source field

Add a data-source reference so any admin can answer "where did this value come from and when?" in one click. It costs one field and saves hours of archaeology.

Refresh schedules: match cadence to volatility

Record type	Reasonable cadence	Why
Strategic accounts	Daily to weekly	Frequent touches; changes trigger timely outreach
Open-pipeline contacts	Weekly	Titles and roles change mid-deal
Dormant accounts	Monthly or quarterly	Low cost, catches reactivation signals
Lead records	At routing time	Freshness matters most at handoff

Aligning cadence to record priority is also the single biggest lever on enrichment cost: most instances find that refreshing everything daily spends the majority of API credits on records nobody is actively working.

Instrument the outcome

Enrichment without measurement is faith-based. Track three numbers from week one:

Match rate — what share of submitted records return usable data. A low match rate usually points to dirty input domains and emails, not the enrichment provider.
Field fill rate — how much of each mapped field is now populated, before vs. after.
Downstream impact — connect rates, campaign personalization errors, and duplicate counts over time.

The 80/20 of getting started

If you do only four things: install from the ServiceNow Store, map enrichment to your standard account/contact fields with overwrite protection, set strategic accounts to refresh weekly and everything else monthly, and review bounce and connect rates monthly. You can refine endlessly after that—but those four steps deliver most of the value.

NowEnrich handles this entire flow from inside your instance—install from the ServiceNow Store, configure your API key, and set per-record-type intervals. See the setup guide →