Merge Duplicates Dialog
A merge dialog pairing two contact records with per field radio picks for the winning value, a retention note, and keep or merge actions.
A merge dialog pairing two contact records with per field radio picks for the winning value, a retention note, and keep or merge actions.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Merge Duplicates Dialog is the static blueprint for resolving two contact records that look like the same person. Record A and Record B sit side by side with avatars, source badges, and the date each was added. Below them, four field rows put both values against each other, Full name, Email, Phone, and Job title, with a radio pick on each side that highlights the value you choose to keep. A muted callout confirms what carries over: notes, activity, and the 12 deals from both records land on the merged contact, while Record B is archived for 30 days so a wrong merge can be split back apart.
The fields are one typed array and the whole dialog is static markup with no Radix portal opened, so the scrim renders correctly inside the preview iframe. The has-checked utilities light the selected value without any client state, and every phone or email swap is copy, not paint.
Reach for this block in a CRM or contacts app when a dedupe scan surfaces a likely match and asks the user to confirm the winning value per field. Wire each radio group to a controlled field map, then post the merged record and archive the loser on submit.
A natural flow around it on an Application Pro page:
Before
After
One strong use is contact deduplication with a per field keep pick. Other merge dialogs:
Tip: name what survives specifically, the 12 deals and the 30 day archive, so the merge feels safe to confirm.