Most data issues fall into four buckets: missing fields (gaps in coverage), wrong values (provider error or staleness), duplicates that didn't merge (identity resolution miss), and stale records (haven't been refreshed). Each has a clear fix.
Missing fields
Symptom: records where critical fields are empty. Cause: enrichment providers don't have data for that record, or the waterfall stopped early. Fix: review the per-field source distribution in Data → Quality → Scorecard; add an enrichment provider that covers the gap; manually fill if the provider gap is real.
Wrong values
Symptom: a field has a value that's clearly wrong (former employer, old title, incorrect phone). Cause: the provider has stale data, or this record hasn't refreshed recently. Fix: manual edit with Lock Value if you're confident; trigger a force-refresh to query providers for current values; review per-source quality to identify chronically-wrong sources.
Duplicates that didn't merge
Symptom: the same person or company appears twice. Cause: identity resolution missed them because of variations in name, domain, or identifiers. Fix: review the records in Data → Match Review; manually merge if they're the same; tune identity-resolution thresholds if this pattern keeps recurring.
Stale records
Symptom: records untouched in 12+ months and the data feels outdated. Cause: nothing has triggered re-enrichment because no signals or activity have fired on these records. Fix: schedule a freshness sweep (Data → Maintenance → Re-enrich Stale Records) to re-pull values for everything aged past a threshold.
When to escalate
If the same issue recurs after fixing — providers consistently wrong on the same field, duplicates that keep appearing despite tuning — file a support ticket. Pattern issues often have configuration root causes that aren't obvious from the symptom.
