Merging contacts
Combine duplicate contact records into one — every channel, conversation, note, and team membership moves under the record you keep.
Duplicates happen. You promote a phone number to "Priya," and a teammate's intro email creates "Priya Sharma." A month later, the same person exists twice in your contact list. If you merge contacts, CommSync folds those records into one — you choose which record to keep, and everything from the others moves under it.
Like every change to your contact graph, merging is always something you do. CommSync never merges contacts on its own, and there is no suggestion queue. See Merging identities for the same rule at the channel level.
Contact merge vs. identity merge
Two tools, two different problems:
| You have… | Use |
|---|---|
| A loose phone number or email that already belongs to a contact | Attach or merge identities — see Merging identities |
| Two (or more) full contact records for the same human | Merge contacts — this page |
An identity merge moves one channel. A contact merge moves everything: all channels, conversations, notes, labels, team memberships, and the shared-contact promotion if there is one.
How to merge from the Contacts view
Find the duplicates
Search the Contacts view; type "Priya" and both records surface side by side.
Select them
Hover a row and tick the checkbox that appears (or right-click → Select for merge). If you select two or more contacts, an overlay action bar appears.
Choose Merge
The merge dialog shows each record with its channels and notes.
Pick the record to keep
CommSync pre-selects the record with the most activity — most channels, notes, recent activity — but switching is one click. The After the merge panel previews the final contact: its name and the combined channel list.
Confirm
The button spells out exactly what will happen — for example, "Merge 2 contacts into Priya Sharma".
For a quick pairwise merge, right-click any contact and choose Merge into another contact…. You can also open the contact and use the ⋯ menu. Then search for the duplicate.
What happens to everything
Say you merge "Priya (mobile)" into "Priya Sharma" at Northwind Clinical:
- Channels — Priya's mobile number moves onto the surviving record. The survivor keeps its name.
- Conversations — every thread follows its channel.
- SMS conversations collapse into one thread; email chains keep their own threads but all open under Priya Sharma.
- Unread counts add together; they do not reset to zero.
- Notes — combined, never dropped.
- CommSync prepends the note from "Priya (mobile)" to the survivor's notes.
- A small "— from Priya (mobile) —" header marks where it came from.
- Labels — the survivor gets every label from both records, deduplicated.
- Teams — if "Priya (mobile)" was in the Northwind Clinical team, the surviving record joins it too.
- CommSync does not duplicate a membership the surviving record already has.
- Shared contacts — if you shared the duplicate with your team, the share moves to the surviving record.
- Members keep their access, and comment threads carry over.
- If you shared both records, the two member lists combine, and each teammate keeps their higher permission of the two.
Merging can't be undone
CommSync deletes the duplicate contact records as part of the merge. You never lose messages or channels — but there is no "unmerge" button. If you merged the wrong records, you can still split individual channels back out and rebuild a contact from them.
Scope and permissions
Your contact graph is private to you (see Core concepts), and the same rule applies to merges: you can only merge contacts you own. Teammates' contacts that appear in your list via shared contacts cannot join a merge — even org admins cannot merge someone else's records.
From an agent
Agents with an API key get the same capability over MCP:
merge_contacts(survivorPersonId, sourcePersonIds)The tool enforces the same rules as the UI: all records must belong to the key's owner, and the survivor keeps its name. CommSync deletes the sources. See MCP server for the full reference.