AiCrm notifies you of a duplicate as youâre typing it and lets you merge the two contact records into one, field by field, without losing a single note.
The same client, three different contact records: the one entered via the form, the one you imported from the CSV, and the one you manually created.
AiCrm compares every contact you create or edit with the rest of your database in real time, as you fill out the form. If the email matches exactly, it tells you. If you havenât entered an email but the phone number is the same (comparing only the digits, so +34, spaces, or hyphens donât matter), it also tells you. And if the name is very similar âa Levenshtein similarity of 0.8 or more, which covers âMaria Lopezâ versus âMarĂa LĂłpezâ or âMaria Lopez Ruizââ it asks if it might be the same person. The notification appears within the form itself, with two buttons: view the existing contact record or create the contact anyway if they are truly two different people.
Once you have the duplicate in front of you, you open the contact record you want to keep and select âMerge with another contactâ. You search for the duplicate by name, email, phone, or company, and AiCrm presents the two contact records side-by-side: the one to keep and the one to delete. For each field âname, email, phone, company, country, status, and notesâ you decide with a tap which of the two values survives. You donât have to keep an entire contact record: you can retain the phone number from one and the notes from the other.
Merging isnât limited to just copying data. The tags from both contact records are all combined, so you donât have to re-tag anything. The activity history and pending reminders of the duplicate are reassigned to the contact record that is kept, so the activity timeline remains complete and no scheduled call is left orphaned. The creation date becomes the older of the two, and the last activity, the most recent. Afterward, the redundant contact record is deleted, and itâs recorded in the activity timeline that this contact was merged with the other, along with the name and email it had.
If you have your website or chatbot connected via the API, webhooks receive the change: a contact updated event for the contact record that remains and a contact deleted event âmarked as a mergeâ for the one that disappears, so your systems are aware and donât write to the non-existent record again.
The notification arrives before you create the duplicate
the check is triggered as you type the name or email, not after youâve already cluttered the database.
Three criteria, not just email
exact email, exact phone by digits, and similar name by text similarity, which catches accents, typos, and partial names.
Field-by-field merge
you choose which name, email, phone, company, country, status, and notes remain, instead of having to sacrifice an entire contact record.
No context is lost
tags are combined, and activity and reminders from the duplicate are reassigned to the surviving contact record.
A record is kept
the merge is noted in the contactâs activity timeline with the name and email of the absorbed record, to know where that data came from.
Your integrations are informed
webhooks receive the updated contact and the one removed by merge, signed, so your website or external CRM can synchronize.
Also works during import
when uploading a CSV, you can request that rows with existing emails update the contact record instead of creating a new one, and new API entries with an already registered email are not duplicated either.

Create your AiCrm account, bring your contacts, and merge duplicates into a single clean contact record.