Finding and merging duplicates

How likely duplicate contacts are surfaced and how merging safely combines both records without losing anything.

Open in Jordyn:/clients

Finding and merging duplicates

The same person sneaks into a book twice — once from a CSV import, once from a booking, spelled two ways. Jordyn watches for this and makes fixing it safe.

How duplicates are found

When two records look like the same person, a card surfaces the likely pair in the Clients section (/clients). You review it — Jordyn suggests, you decide. Nothing is merged automatically.

Merging is safe

Merging combines the two records and keeps everything: emails, calls, notes, tasks, cases, files, and history from both records end up on the single merged contact. You do not lose the timeline from either side, and nothing already sent or filed changes.

If the pair is not actually the same person, dismiss the card and the two records stay separate.

Preventing duplicates in the first place

CSV imports already refuse to create duplicates — re-importing a list updates matching records instead of doubling them. The duplicate cards catch what imports cannot: the same human arriving through two different doors.

Related

Can’t find it? Ask the Guide — it answers from these same articles.