Merge Duplicate Leads Without Losing History

The same customer submits three forms on two sites over a month. Merge Duplicate Records turns those three rows into one lead, one owner and one conversation.

Merge Duplicate Records is the tool on every lead and contact in LeadLocate CRM that finds other records for the same person and combines them into one. The scan checks name, phone and email, so it catches the customer who used a work email on the website and a personal email on a third party site, and the customer who typed a different phone number on the second form. The matches are shown in a list with one marked Keeper, the rep ticks the rows that are truly the same person, confirms, and the CRM folds them into the keeper.

The words in the page title are the important ones: without losing history. A merge writes a note on the keeper describing what was combined, the merged records are retired rather than destroyed, and the keeper is assigned to the rep who did the merge so the combined lead has one clear owner. The customer's communications log, which already holds every call, text, MMS, email and voicemail in one place, keeps building on the single record from that point on. The general problem, why duplicates happen in automotive CRMs and what they cost a store, is laid out on the duplicate lead management for automotive CRMs page. This page is the tool.

A customer named Marcus fills out a form on the store's website on the 3rd asking about a used half ton. A week later he submits a request through a third party site, which sends the lead by email to a different feed, with his cell number instead of the home number he used the first time. Ten days after that he replies to a LeadLocate offer request page for his trade. The store now has three Marcuses: one on the website feed assigned to Dana, one on the provider feed that rotated to Luis, and one on the acquisitions feed that landed on Dana again. Luis texts him about the truck on Tuesday; Dana texts him about the truck on Wednesday. Marcus, reasonably, wonders whether the store talks to itself.

Dana opens the newest lead, clicks Merge Duplicate Records, and the overlay scans. It comes back with two matches: the provider lead matched on phone and the website lead matched on name and email, with the newest record marked as the Keeper. She checks both, confirms, and the three rows become one. The lead is hers, the note on it says what was merged and when, and the next time Marcus texts, one thread lights up on one rep's screen. Luis sees the merge note if he goes looking, and the sales manager, who had two reps working one customer, now has one.

That is the whole workflow. There is no export, no spreadsheet, no admin ticket. The scan takes a few seconds and the merge takes one click after it.

Leave your number and a lead specialist calls you back to answer your questions about pricing, coverage, and setup. Mon - Sat, 9:00 AM - 6:00 PM Pacific.

Prefer to talk right now? Call or text 844-376-2274.

Merge Duplicate Records opens from the lead detail in the Leads view and from a contact in the Contacts view, because duplicates happen to both. The overlay first shows that it is scanning for duplicates and checking name, phone and email matches. If nothing matches, it says so plainly: no other records match by name, phone or email. If something does, it lists each match with the rep it is assigned to, the name, phone and email on the record, its status and when it was posted, and it marks how each one matched, so a rep can tell a phone match (almost always the same person) from a name only match (which might be a different Marcus).

Name only matches are not merged unless the rep ticks them. That is deliberate. A phone number or an email is a strong signal; a name is a hint. The checkbox on each row is how a rep says yes, this is the same person, and the merge only touches the rows that were checked. The whole thing is scoped to the store's own account, so a merge never reaches another dealership's records and never touches a record that was already retired.

On the phone app a rep works leads in the Leads view and sees the merged record like any other. Merging itself is a desktop task, which suits it; it is a decision a rep makes while looking at the details, not something to do one handed on the lot.

Without a merge tool a store has two choices, and both are bad. The first is to leave the duplicates alone, which means two reps work one customer, the customer gets two sets of texts, the store's lead count is inflated, and any report on close rate by source is wrong because the same sale is attributed to a lead that was never the one that closed. The second is to delete the extra rows, which means the history on them goes with them: the first text Luis sent, the call recording from the provider lead, the note about the trade. A month later, when the customer says he already told someone about the lien on the trade, nobody can find it.

Some CRMs charge for a data quality add on that does this; others require an export, a spreadsheet cleanup and a re-import, which is a weekend project a store does once and never again. In LeadLocate the merge is on the lead and is part of every plan. Because Lead Feeds Manager puts every source into one Leads view, the duplicate is visible in the same list where it will be merged, rather than hiding in a separate provider portal.

The quieter cost is the one in the pay plan. When two reps have the same customer and the customer buys, somebody is getting a half deal and somebody is getting a conversation with the desk. A merged record with one owner and a note that says who merged what settles that before it becomes an argument.

Three things happen at the moment of a merge, and each one exists to keep the record honest. First, the CRM writes an audit note on the keeper describing the merge, so a manager reading the lead later knows the record was combined, when, and from what. Second, the merged rows are soft deleted rather than removed, which is the same retirement the trash bin uses elsewhere in the CRM; the CRM keeps what it knew. Third, the keeper is assigned to the rep who performed the merge, so the combined lead has one owner and the assignment history reflects the decision.

From then on, the communications log on the keeper is the single record. Every call, text, MMS, email and voicemail that follows lands on it. The Customer Profile the store builds from the lead, with its encrypted personal information and its co-buyer, sits on one record rather than three. And when the lead becomes a deal in DealTracker, it starts from one lead with one history, which is what the finance office wants to see when it opens the deal.

Duplicates are a compliance problem before they are a tidiness problem. A customer who replied to one of the store's texts asking not to be contacted may have done so on the provider lead, while the website lead, owned by a different rep, keeps texting. The customer experiences that as the store ignoring the request, and the store experiences it as an exposure. Merging the records puts the customer's replies, the store's messages and the customer's status on one record that one rep is responsible for.

The Do Not Call Blacklist is the other half of the answer: a blacklisted phone number or email is hidden from every CRM view, whichever feed it came through, so a duplicate that arrives after a customer asked to stop never reaches a rep's queue in the first place. Together, merge and blacklist mean a store can say with a straight face that it has one record per customer and one place where that customer's wishes are kept. The merge note is part of that record, so the answer to why two leads became one is written down rather than remembered.

There is nothing to turn on. Merge Duplicate Records is available on every lead and contact from the day an account is created. Open the lead, click Merge Duplicate Records, wait for the scan, check the rows that are the same person, and confirm. If the scan finds nothing, the overlay says no duplicates were found and the lead is left alone.

A few habits make it work better. Merge from the newest record, because the newest one is marked as the Keeper and usually carries the customer's most recent contact details. Run the Phone Validator and Email Validator on the keeper afterward, so the surviving number and address show a validity dot on the lead. And after a large contact import, expect to merge a few, because a book of business almost always contains customers who are already in the CRM from a lead. If your store wants a scheduled sweep that finds duplicates across the whole account rather than one lead at a time, it is available on request, and our team puts it in production for your dealership.

Merge is the cleanup; three other features reduce how often it is needed. Lead Feeds Manager puts every source into one Leads view, so a duplicate is visible where it will be merged. Round robin lead assignment gives each lead one owner from the start, which makes the second Marcus obvious to the rep who already has the first. The Contact Import page explains how a store brings its book of business in without creating a duplicate for every past customer who later submits a lead.

Merge Duplicate Records is part of the LeadLocate CRM in every plan, including CRM Only. Plans are month to month and listed on the pricing page. The all features list shows where it sits among the rest of the platform, and the pre-recorded live demo shows the lead views it lives in.

How does LeadLocate find duplicate leads?

Merge Duplicate Records scans the store's own records for matches to the open lead by name, phone and email. Phone and email matches are shown as strong matches; name only matches are shown separately and are merged only if the rep checks them.

What happens to the merged records?

The rows you check fold into the Keeper, which is the newest record. The CRM writes a note on the keeper describing the merge, assigns the keeper to the rep who merged, and retires the merged rows rather than erasing them, so the customer's history stays on one lead.

Can I merge contacts as well as leads?

Yes. Merge Duplicate Records opens from a lead in the Leads view and from a contact in the Contacts view, and works the same way on both.

Will a merge ever touch another dealership's records?

No. Every scan and every merge is scoped to your own account, and the CRM re-checks each selected record against your account before merging it, so a merge only combines records that belong to your store.

What if the scan finds nothing?

The overlay tells you no other records match by name, phone or email, and the lead is left exactly as it was. Nothing is merged unless matches are found and you confirm them.

Is merging an extra cost or an add on?

No. It is part of the LeadLocate CRM in every plan, including CRM Only. Plans are month to month and listed on the pricing page.

Merge Duplicate Records is part of every LeadLocate plan, month to month. See three leads for the same shopper become one lead with one owner and its full history.

Prefer to talk right now? Call or text 844-376-2274.