Your AI agent is only as good as your duplicates: a data readiness guide

The short answer: Agentforce data readiness comes down to four things an agent needs from your records: one record per customer, fields that mean what their labels say, a history of changes, and enough written context to ground an answer. You can test each with reports and Setup pages you already have. Clean up only what the first use case touches.

A new hire who finds two accounts for the same company walks over to the account owner and asks which one is real. An agent doesn’t walk anywhere. It picks one, writes a reply with your company’s name on it, and moves on to the next conversation. Multiply that by every duplicate, every half-used field and every contact owned by someone who left in March, and you have the real reason people say “get the data ready first”. It isn’t a slogan. It’s the difference between a person noticing a problem and a process repeating it.

Why is an agent more exposed to bad data than a person?

An agent has no memory of why your data looks the way it does. A person knows that “Region” was repurposed in 2022 and that the top Acme account is the one with the contracts. An agent knows what the records and field descriptions say, and acts on it at speed.

Two things make that worse. An agent working as a service agent runs as its own agent user, and as reported by Salesforce Ben, verifying a customer’s identity tells it who the customer is, not what it may read. So it works with the access its user has, which is often broader than anyone planned. And its mistakes repeat. A person’s slip is one slip. An agent’s slip is every conversation that hits the same record. Salesforce’s own readiness advice says the same thing in fewer words: old or incorrect data leads to unreliable outcomes, including made-up answers.

Is there one record per customer?

You need one record per customer because an agent can’t tell which duplicate is the live one. It may answer from the thin copy, update the wrong record, or update both.

Here is how to look with native tools, cheapest first:

  1. A grouped report. Build an Accounts report, group by Account Name, and sort by Record Count, highest first. It only catches exact name matches, but that is where the worst offenders live.
  2. Matching and duplicate rules. Salesforce ships standard matching rules for business accounts, contacts and leads, and person accounts, and a matching rule does nothing until a duplicate rule uses it (Trailhead). They stop new duplicates. They don’t find the ones you already have.
  3. Duplicate jobs. To scan existing records, Setup has Duplicate Jobs. As reported by Salesforce Ben, they’re limited to Performance and Unlimited editions, to the standard Lead, Contact and Account objects, and can fail in orgs with many records. Check your edition first.
  4. A duplicate-bypass report. Trailhead describes a custom report type with Duplicate Record Items that shows records saved after someone clicked past the warning. That report is your list of where people routinely override the rules.

Merging is a separate decision, and a wrong merge can’t be taken back by the platform. Our guide to merging duplicate accounts covers it.

Do your fields mean what they say?

An agent trusts the label and the description, so a field that means something other than its name is a trap. Salesforce’s own Trailhead guidance on agent-ready flows says agents use a flow’s description and the descriptions on its variables, and that without a solid name and description the agent can’t reliably decide what to do with the data.

That guidance is about flows, but the habit carries over to the fields an agent reads. Pick the ten fields the first use case depends on, then:

  • Open each in Object Manager and read the Description and Help Text boxes. If they’re empty, write one sentence each.
  • Report on each picklist, grouped by value. Two spellings of one value, and a big “Other”, are what an agent can’t interpret.
  • Ask two people what each status means. If you get two answers, write a third, official one down.

This is slow work and nothing in the platform shortcuts it, because only a human knows what a field was meant to hold.

Does the org keep a history of changes?

You want history because an agent that can update records will eventually update one wrongly, and “what was it before?” is the first question afterward. Field History Tracking answers it for the fields you turn it on for.

As reported by Salesforce Ben, native tracking covers 20 fields per standard or custom object, keeps changes for up to 18 months in the UI and 24 months through the API, and starts only when you select a field, with nothing recorded retroactively. To turn it on: Object Manager, the object, Fields & Relationships, Set History Tracking. For a custom object, tick Track Field History in its Details section first. Our guide to field history tracking limits covers what to do when 20 isn’t enough.

For readiness, the rule is plain. List the fields the agent might change, and make sure each one is tracked before the pilot, not after the first surprise.

Is there enough text on the record to ground an answer?

An agent can only ground an answer in what’s written down. A case with a blank description and a one-word subject gives it nothing to quote, so it fills the gap with something plausible.

You can’t audit this with a formula, so sample it. Pull 20 recent records of the kind the agent will handle and read them as if you’d never seen the customer. Can you tell what happened and what’s next? Count the ones where you can’t. If the long-text fields hold pasted email chains or “see call notes”, the agent will quote those. Opinion: this is the check most teams skip, because there’s no report for it.

How much of the cleanup does the first use case need?

Only the part the first use case touches. Salesforce’s readiness guidance says not to clean all your data: define the business problem, identify only the data the agent needs for it, and get “enough good data to get the agent started”. An agent that answers order-status questions needs reliable orders and contacts. Your 2019 lead data can wait.

So choose the use case first (our post on choosing your first Agentforce use case helps), then run the four checks against only those objects and fields. That turns “fix our data” into a list you can finish.

What to do Monday:

– Write down the first agent use case in one sentence and list the objects and ten fields it would read.

– Run the grouped Accounts report and note the top ten duplicate names.

– Open those ten fields in Object Manager and add a Description wherever it’s empty.

– Turn on field history for any field the agent might change.

– Download the Agent Readiness Checklist and answer the 25 questions with someone who knows the org.

Where we come in

Sounding, by GTM Cloud, is a read-only data quality assessment that scores duplicates, completeness, staleness, ownership and agent readiness inside your org. It’s in pre-release and in pilot, not publicly listed yet. It measures and recommends, and it won’t merge or fix anything. If you’d rather have a person do the first read, we also run the Agentforce Readiness Sprint.

Questions people ask

How clean does my data need to be for Agentforce?

Clean enough for the first use case, not perfect everywhere. Salesforce’s own guidance says to identify only the data the agent needs for its task and start there. If the agent reads orders and contacts, those two objects need to be reliable. Everything else can wait for the second use case.

Can Agentforce handle duplicate records?

Don’t count on it. An agent works with the records it can see, and nothing in the sources we opened says it picks the right duplicate for you. Salesforce’s own readiness advice is to merge duplicates into one profile per customer before the agent runs, not after it has picked a copy.

What is the first thing to check for AI readiness in Salesforce?

Access, then duplicates. Find out what the agent’s user can see and change, because an agent works within that. Then run a grouped report for duplicate account names. Both take under an hour, and both often surprise people. The checklist covers the rest in a sensible order.

Sources