Auto Dealer CRM Lead Deduplication Checklist

Duplicate leads can make a dealership appear slower than it is, create competing follow-up, and obscure which source produced the inquiry. Deduplication should protect the original context while giving staff one trustworthy record to work.

Inventory every lead source

List inventory forms, trade-in requests, finance forms, service booking, parts requests, chat, phone imports, campaigns, and third-party providers. Record the source event, timestamp, vehicle, department, and destination fields for each path.

Choose matching signals carefully

Use combinations of normalized email, phone, customer reference, vehicle identifier, time window, and department. Do not merge records on a shared household phone or a generic email without enough context to avoid false matches.

Define merge and non-merge rules

Document which record remains primary, how notes and consent are combined, how vehicle context is preserved, and when separate inquiries should remain separate. Give staff a way to review uncertain matches instead of forcing every case.

Preserve ownership and timing

Deduplication should not erase the first-received timestamp, source, assigned person, response events, or department. Connect related activity while keeping enough history to measure service levels accurately.

The lead response dashboard checklist and lead source tracking checklist depend on this context.

Protect personal data

Limit who can view merged records, avoid putting sensitive details in matching logs, document retention, and provide a correction path. Include vendor imports and exports in the access review.

Test, monitor, and review

Create test cases for repeated submissions, multiple vehicles, service and sales inquiries, changed contact details, provider retries, and shared contact points. Monitor false merges, missed duplicates, response delays, and manual overrides.