Keep your data clean
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.
Built 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.
Runner flags the likely duplicates and shows why each pair turned up
The trade-show list went in on Tuesday, and now the same buyer at Northwind is in there twice, once at northwind.example and once at nortwhind.example. Runner's duplicate queue reads every contact in the product and pairs the records that look like the same person: a shared email, phone number or name, a name that's nearly identical, or the same address typed twice with a one-letter slip in the domain.
Each pair card shows what matched and a confidence level, so the obvious pairs are quick and the doubtful ones get a closer look. When two records really are different people, dismiss the pair. That decision is recorded, and the pair stays out of the queue from then on.
Accounts get a queue of their own, reviewed the same way.
A person chooses the record that stays, and the stricter consent comes with it
Nothing merges until someone picks which record to keep, and the confirmation names both records before anything moves. The merge carries product memberships, consent, activity and message history across to the record you keep, along with notes, tasks, tags, custom fields and links.
Where both records hold a consent decision for the same product, the more protective one wins. An unsubscribe, a refusal or a do-not-call beats anything less restrictive, a known answer beats an unknown one, and the earliest opt-out date is the one kept. Your organization's opt-out list is kept by email address, so a merge leaves it exactly as it was.
The record you don't keep is marked as merged and leaves the directory. It's never deleted, and clicking merge twice doesn't merge anything twice.
Picture this
One of the two Northwind records unsubscribed from product updates last spring. The other is marked as consented. After the merge, the record you kept is unsubscribed, and last spring's opt-out date is the one it carries.
Undo moves the rows back, or refuses and tells you why
Every merge writes down the ids of the rows it moved, and only the ids: never a value, a name, an address or a number. That record is what makes undo exact. Reverse a merge from the prompt that appears right after it, or later from the list of recent merges.
An undo is all or nothing. If any row the merge moved has been changed or removed since, the whole undo is refused, rather than moving most of the rows back and leaving a half-split pair behind.
One part stays merged on purpose. Where both records held a consent decision for the same product and the two were combined, the combined decision isn't split apart again, and the merge history says how many of those there are before you confirm. An account merge has no such remainder, so undoing one moves every row back.
Every merge is one pair and one person's choice. There's no scheduled job and no bulk action that merges records on its own.
Questions buyers ask
Can I undo a contact merge?
Yes. The merge records every row it moved, and an undo moves them all back, either right after the merge or later from the recent merges list. It refuses if any of those rows has changed since, and a consent decision that was combined with the kept record's stays combined.
What happens to an unsubscribe when two duplicate contacts are merged?
The more protective decision wins. An unsubscribe, refusal or do-not-call beats a less restrictive one, and the earliest opt-out date is kept.
Does Runner merge duplicates automatically?
No. Runner flags the pairs, and each merge happens when a person picks which record to keep. Nothing merges on a schedule or in bulk.
Is the duplicate contact deleted after a merge?
No. It's marked as merged into the record you kept and removed from the directory, which is what lets an undo bring it back.
What if two flagged contacts are different people?
Mark them as not duplicates. The decision is recorded, and that pair no longer appears in the queue.
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.
How teams often buy this job
Usually bought as Insycle or Dedupely.
InsycleDedupely
Trademarks of their owners. No affiliation or endorsement.