AI CRM Data Enrichment NZ: Check Sources Before Updating Customer Records

What is CRM enrichment—and when is cleanup enough?

Enrichment brings additional facts into a record, such as a company's published website or business location. Cleanup corrects the records you already hold: duplicates, inconsistent stages and missing owners. If two records describe the same customer, enriching both does not resolve the underlying problem.

Use the CRM cleanup checklist before adding external facts. This guide tackles a different decision: which source may change which field, under whose authority?

Check native settings before adding an agent

Your CRM may already provide enrichment, property mapping and activity history. Check the features and permissions available in your account before commissioning another integration. The HubSpot workflow guide covers the wider sales-preparation decision; enrichment alone is not a reason to build an agent.

Decide who owns each CRM field

Agree a field-authority policy before collecting proposals. Treat the following as a starting design to adapt, not a universal CRM configuration.

1. Separate three update rules

• ✓
  Fill-empty: propose a value only when a permitted field is blank; still review the source and identity match.
• ✓
  Propose-only: show a suggested correction beside the current value, without changing the customer record.
• ✓
  Never-overwrite: exclude customer instructions, consent preferences, negotiated terms and other protected fields from the enrichment writer.

Record the owner and permitted sources for each field. A current customer instruction should not lose to an older directory listing. If the customer later corrects a detail, use an authorised correction process—not an enrichment rule that silently replaces it again.

Copy a source-to-field review register

Use one row per proposed field change, rather than approving a whole contact with a vague “looks good”. Keep this register in a controlled document or staging area accessible to the reviewer.

Do not copy unnecessary personal information into the register. A model's confidence score is not evidence that a source describes the right person or company.

Run one small, reversible enrichment test

Choose a limited set of approved company-level fields and records. Keep customer messages, consent fields and sensitive notes outside the initial write scope. Company records can still contain personal information; check the actual contents.

2. Confirm the identity and source

Match the company using an approved identifier and supporting context, not its name alone. Check whether the page is current and describes the right branch or legal entity. If the match is ambiguous, hold the proposal rather than guessing a domain, job title or contact address.

3. Test every route that can write

HubSpot's enrichment settings documentation describes mapping and overwrite rules, but warns that conversational enrichment and the Enrich record workflow action can overwrite properties regardless of mapping rules. Test the actual method you will use; a fill-empty setting elsewhere is not sufficient protection.

4. Approve, write and read back

Approve the exact field and value. Immediately before writing, recheck the current value; if someone has changed it since review, stop for another decision. After writing, read the exact destination record and compare it with the approval. Retain the previous value and a recovery procedure. Do not reverse a later legitimate customer correction during rollback.

Worked example: hold a conflicting company location

This is a fictional Christchurch business example, not a client result or tested integration. Record DEMO-CRM-14 has a customer-confirmed city of Christchurch. An older directory proposes Auckland, while the company's current website lists both locations without naming a head office.

The reviewer records both sources and holds the city change. More sources do not settle which location the CRM field is supposed to represent. First define whether the field means billing city, branch or head office, then obtain appropriate confirmation. A separate blank website field could be reviewed independently; approving it would not approve the disputed city.

Check privacy and downstream permissions before expanding

5. Review collection and vendor terms

The Privacy Commissioner's IPP3A guidance explains notification requirements for indirect collection of personal information from 1 May 2026, with exceptions. Have your privacy lead review the purpose, sources, notification position, retention and access before enriching contact records. Public availability is not a blanket permission for every subsequent use. This checklist is operational guidance, not legal advice.

Review the vendor's current data-sharing and AI-training terms separately; do not assume one opt-out describes every use. Record the settings and terms checked. Use the AI privacy impact assessment guide to prepare the questions.

Enrichment approval is not outreach approval. Keep sending, list enrolment, lead reassignment and other downstream actions blocked during the test. Check whether a field update triggers an existing workflow before granting write access.