Free skill · October 3, 2026

CRM Duplicate Merge Impact Review

Prepare the field and related-record consequences of a proposed duplicate merge without merging records.

Prepare the field and related-record consequences of a proposed duplicate merge without merging records. The download provides a specific review process. It does not make decisions or act in an account.

Download the free skill

One complete Markdown file. No subscription, checkout or fabricated setup files.

Download SKILL.md

What to provide

Approved duplicate candidates, stable IDs, field values, related activities and survivor policy.

How it works

  1. Treat a matching record as a candidate, not proof of one identity.
  2. Compare fields and retain conflicts. Newer values are not automatically correct.
  3. Map related activities and consent restrictions to the proposed survivor using supplied rules.
  4. Return dry-run effects and identity gaps. Do not merge, delete or remove opt-outs.

The output

candidate IDs | identity evidence | conflicting field | proposed survivor rule | related-record impact | blocker

Worked fictional example

Fictional C1 and C2 share a name but have different verified emails. Identity is unresolved. Matching phone with conflicting opt-out flags still requires consent review.

Checks and limits

Preserve source versions and original values. Unknowns stay unknown. Use a qualified reviewer for regulated, legal or hiring decisions. No send, share, account change, schedule, ledger update or payment is authorized. No live account test is claimed.

More sales workflows · How-to guides

Method: reviewed source. Demand lead: GSCsalesanalytics9andpipeline6priorfullqueryread;methodleadnotvolume. These are site-query cluster impressions and method evidence, not exact new-topic monthly search volume or a traffic promise. Checked October 3, 2026.