Skip to main content
CRMs accrete duplicate records the way oceans accrete plastic. The exact-match dedup is easy; the fuzzy cases — “Acme Corp” vs “Acme Corporation” vs “Acme Inc” — eat hours of RevOps time. A dedup Agent does the fuzzy matching with reasoning, merges what’s safe, and surfaces the ambiguous cases for a human to decide.

​
When this pays off

Duplicate accounts everywhere

Sales operations reports keep getting flagged because the same company exists under three names.

Manual dedup is hours

Each quarter, someone spends a day or two going through dedup candidates and merging by hand.

Conflicting fields after merge

Even when records get merged, field-level conflicts (which address? which industry?) get resolved arbitrarily.

Bad merge erodes trust

A wrong merge wipes deal history; teams stop trusting the dedup process and the queue grows.

​
The shape of this use case

A dedup Agent takes a candidate pair (or a list of candidates) and returns a merge decision with reasoning.

Inputs

Candidate records, full field-level data, related activity / deal history.

Sources

CRM, your dedup heuristics / playbook, parent-child hierarchy, third-party data for ground-truth checks.

Output

A decision (merge / keep separate / human review) with confidence, plus field-level conflict resolution recommendations.

Delivery

High-confidence merges applied directly (with audit log); ambiguous cases queued in a review tool or posted to RevOps Slack.

​
Where to start

Two ways in, depending on whether you want something running today or built to your exact spec.

Clone a pre-built Agent

Open the CRM Agent. More in the Marketplace.

Build your own

Start from scratch in the builder, or by describing it in Claude Code or Cursor with Programmatic GTM.
Either way, these are prompts your team can use on day one:
  • “These two HubSpot accounts both look like Acme Corp — are they the same company? Compare addresses, websites, contact overlap.”
  • “Run dedup on the leads imported from this trade-show CSV — flag the high-confidence matches and the ones I should look at.”
  • “Did we already have a record for this contact? Check across CRM and prior tickets.”

​
Where to take it

Once it’s running, deepen it in three moves:

Give it a playbook

Shape it with a prompt, your matching rules in Knowledge, and Bulk Schedule.

Automate it on signals

Wrap it in a workflow that fires on a trigger.

Let it improve

Feed merge undos and disputes back into the Agent’s evals so its confidence thresholds track what’s reliable.

​
Common pitfalls

A wrong merge loses deal history. Always log what got merged and offer one-click undo for the first quarter of running.
Aggressive auto-merge merges records that should have stayed separate. Start with high thresholds and loosen as you watch outcomes.
Merging accounts without a rule for which address / industry / size wins produces garbled records. Document field priority rules in Knowledge.
Merging an account with an active opportunity into one without can break attribution and rep ownership. Have the Agent factor open-deal status into the decision.