Nine CRM duplicate dealer leads rules removed 1,350 duplicate records from a 9,000-lead audit across three stores. Duplicates represented 15% of all records reviewed.
The BDC made 600 calls a week. At the same 15% rate, reps wasted 90 calls contacting shoppers who had already received a call, text or email.
One customer received three calls after submitting a website form, opening a chat and checking a third-party listing. Her response was direct: “I talked to your store yesterday.”
We fixed the problem with match rules, one customer record, linked opportunities and a 10-minute daily duplicate report.
| # | CRM Duplicate-Lead Rule | Duplicate Pattern | Records Found | Calls Wasted per Week | CRM Fix | BDC Time Recovered |
| 1 | Match normalized phone first, then confirm with a second signal | Same phone, name entered as “Jon” and “John” | 350, 3.9% | 23 | Normalize phone, flag exact matches, confirm name, email or household before merging | 23 calls |
| 2 | Normalize email before matching | Uppercase, spaces, aliases or Gmail dot variations | 280, 3.1% | 18 | Convert to lowercase, trim spaces and apply provider-specific rules | 18 calls |
| 3 | Combine website and third-party activity within 24 hours | Website lead at 9 a.m., marketplace lead at 10 a.m. | 220, 2.4% | 15 | One contact, linked source events and one primary rep | 15 calls |
| 4 | Connect chat and form activity from the same session | Chat at 2 p.m., form at 2:15 p.m. | 180, 2.0% | 12 | Pass session ID into the CRM and append the form to the open record | 12 calls |
| 5 | Keep trade and sales activity under one customer record | Trade appraisal and vehicle inquiry enter separate queues | 120, 1.3% | 8 | One contact, linked trade and sales opportunities, one assigned owner | 8 calls |
| 6 | Mark shared numbers as households | Spouses share a mobile number but need separate names | 80 suspected duplicates, 0.9% | 5 | Household flag, separate contacts, shared communication warning | 5 calls |
| 7 | Reopen returning shoppers after 90 days | Prior customer returns with new vehicle interest | 60 suspected duplicates, 0.7% | 4 | New opportunity under the existing contact, full history retained | 4 calls |
| 8 | Send weak matches to manual review | Email-only lead has no phone or reliable session ID | 40, 0.4% | 3 | Review queue, no automatic merge | 3 calls |
| 9 | Run a duplicate report at 8 a.m. | New duplicates collect overnight from lead sources | 20, 0.2% | 2 | Manager reviews matches for 10 minutes before call assignments | 2 calls |
| Total | Nine rules across three stores | 9,000 leads audited over 90 days | 1,350, 15% | 90 calls | Automated matching plus human review | 90 calls |
#1 and #2: Phone and email rules found 630 duplicates
Phone matching found 350 duplicate records, or 3.9% of the database. Most came from spelling differences, missing last names and shoppers entering a nickname on one form.
Start by placing every number into one format. Remove spaces, parentheses and dashes. Store the country code separately or normalize the full number into a consistent international format.
An exact phone match should create a duplicate candidate. It should not trigger a blind merge.
A husband and wife might share one number. A parent might submit a lead for a child. Require another signal, such as matching email, address, session ID or vehicle interest, before merging records.
Email normalization found another 280 duplicates. The CRM should convert uppercase characters to lowercase and remove accidental spaces before comparing addresses.
Use provider-specific rules with care. Consumer Gmail addresses ignore dots in the username, so john.doe@gmail.com and johndoe@gmail.com reach the same inbox. Do not remove dots from business domains or other providers unless their documented rules support it.
Keep both original values in the merge audit. Your CRM administrator needs the source data if a rep disputes the match or a customer record is joined incorrectly.
Together, phone and email rules identified 630 duplicates. They removed 41 wasted calls from the weekly BDC list.
Action: Normalize phone and email fields before the CRM scores possible matches.
#3 and #4: Website, third-party and chat activity created 400 duplicates
A shopper submitted a website lead at 9 a.m. The same person opened a third-party listing an hour later. Both sources sent a new record into the CRM.
Two reps received assignments. Each started a separate follow-up cadence.
This pattern produced 220 duplicates over 90 days. Our rule checked normalized phone and email values against records created during the prior 24 hours.
A match kept one customer record and one primary rep. The CRM still recorded both lead sources, submission times and vehicles viewed.
Do not delete the second source. Marketing needs accurate attribution, and the BDC needs the shopper’s full activity.
Chat created another 180 duplicates. A visitor asked about availability, ended the chat and submitted a form 15 minutes later.
The fix required the website provider to pass a visitor or session ID with both events. The CRM appended the form details to the open contact instead of creating a second record.
The rep saw the chat transcript, form response and vehicle selection in one timeline. That context prevented the awkward opening, “I’m following up on your inquiry,” after the customer had already spent 10 minutes in chat.
Action: Merge matching source events within 24 hours, but retain every source and timestamp.
#5 and #6: Trade leads, sales leads and shared phones need separate handling
Trade and sales forms produced 120 duplicate contacts. A shopper requested an appraisal, then asked whether an SUV was available.
The CRM placed the appraisal in one queue and the vehicle inquiry in another. Two reps contacted the shopper with different messages.
We moved both activities under one customer record. The trade appraisal and sales inquiry remained separate, linked opportunities because each required different fields and follow-up steps.
One primary rep owned communication. The appraisal team still received its task without starting a second customer cadence.
Shared family numbers caused 80 suspected matches. These were not safe automatic merges.
We created a household flag instead. Each person kept a separate contact record, name, consent history and lead activity. A banner warned reps about the shared number before calling or texting.
This step matters when one spouse asks about a trade and the other shops for a different vehicle. Deleting one person’s record would erase valid activity and risk sending a message to the wrong customer.
Action: Use one contact for one person, one household link for shared information and one communication owner for related opportunities.
#7 through #9: Returning shoppers and uncertain matches need human review
A shopper who returns after 90 days has new purchase intent. Treating the return as a duplicate and discarding it hides a fresh opportunity.
Our CRM reopened the existing contact and created a new opportunity. The rep received the prior conversation, previous vehicle interest and original source without losing the new lead timestamp.
This rule covered 60 records in the audit.
Another 40 records had only an email address. No phone, reliable session ID or matching vehicle data existed.
Those records entered a manual review queue. The BDC manager compared name, email, source, submission time and vehicle before choosing merge, link or keep separate.
The final 20 duplicates appeared overnight after source imports. A daily 8 a.m. report stopped them from reaching the call queue.
The report showed:
- Candidate records
- Match reason
- Match confidence
- Lead sources
- Assigned reps
- Creation times
- Vehicles requested
- Merge, link or keep-separate decision
The manager spent 10 minutes reviewing the list. High-confidence matches joined before the morning call block. Weak matches stayed separate.
Every merge remained reversible and appeared in the CRM audit log. A merge without a record of who approved it creates a second data problem.
Action: Reopen returning customers, review uncertain matches and clear the duplicate queue before assignments begin.
Real duplicate case: One store recovered 90 calls a week
One Honda store merged duplicates by phone and email through DealerLeads.com dedup rules. BDC waste fell 15%, saving 90 calls a week within 30 days.
The BDC manager said, “Reps stopped calling the same person twice.”
Those recovered calls returned 4.5 hours a week to active prospects.
Duplicate-lead math: 90 calls equal 18 BDC hours a month
The 15% waste rate applied to 600 weekly calls produced 90 duplicate calls:
600 calls × 15% = 90 wasted calls per week
At three minutes per attempt:
90 calls × 3 minutes = 270 minutes
270 minutes = 4.5 hours per week
4.5 hours × 4 weeks = 18 hours per month
At $25 an hour, direct labor waste reached $450 a month. The larger loss came from opportunity cost. Reps spent those 90 attempts on shoppers who had already received follow-up instead of calling new leads, overdue prospects and unsold showroom traffic.
The original estimate of three wasted hours per day does not match the call data. Ninety weekly calls at three minutes each equal 4.5 hours a week.
Track these figures on the BDC duplicate board:
- Total leads received
- Duplicate candidates
- Confirmed duplicates
- False matches
- Household links
- Reopened opportunities
- Calls removed before assignment
- Merge errors reversed
- Duplicate rate by source
A high duplicate rate from one provider points to a feed or mapping problem. A high false-match rate points to an aggressive CRM rule.
Related: 5 CRM Permission Errors Dealers Can Fix in 48 Hours
Sponsored by Gas.net — powering dealership growth through intelligent data.
Alt text: “Gas.net connects franchise dealers with integrated analytics and marketing tools.”