Dedupely and Runner
Runner proposes duplicate pairs with the reasons they matched, tells the reviewer which kinds of record a merge moves before they confirm, and records every row it moved so the merge can be reversed.
What it is usually bought for
Keep your data clean
The job, on its own page: Keep your data cleanBuilt into Runner
- Duplicate pairs, each with the reasons it was flagged
- Where both contacts sat on the same product, the more protective email, call and recording consent is kept
- Each merge records the rows it moved, so undo can put them back
Worth knowing
Runner brings each likely pair to a person — one reviewed pair at a time, never in bulk on a schedule. A contact undo puts the moved rows back unless one has changed since, and what was combined into the kept contact — consent, and a membership, tag, property or link both held — stays with it. An account undo moves its contacts, opportunities and evidence back as they are now.
When to keep Dedupely
- If Dedupely does this job well for you today, keep it. Nothing on this page asks you to move.
- Runner stops where the bound above says it stops, and a tool you already run may cover exactly that.
Use what already works
Use the imports and connected inputs you already rely on. The duplicate queue reads a product's contacts, imported ones included, and keeps Undo for recent merges on the same page.
InsycleDedupely
Trademarks of their owners. No affiliation or endorsement.