Dealership Lead De-Duplication & Merge

Three Records Walk In.
One Walks Out.

The same buyer reaches your store three ways in one day. Watch what the matcher does with it.

Merge recordcross-channel · one buyer

9:14 AMRecord AWeb form lead: personal email, asking about a used Silverado, mentions a trade.
11:02 AMRecord BPhone-up from a mobile number. Same Silverado, no email left. Filed by the CRM as a brand-new lead.
2:37 PMRecord CInstagram DM, first name only. Same trade-in described in the same words.
2:37 PMMatchedPhone, vehicle of interest and trade details line up across all three. Confidence high enough to act.
2:38 PMMergedOne record, full history from all three channels, one assigned owner. Every rep sees the same thread.
2:39 PMGuardedCompeting follow-ups cancelled. One cadence continues, and nobody quotes against their own store.

Illustration of the matching flow we configure, not a specific customer's record. Match rules and confidence thresholds are set per dealership.

Matched, Merged, Owned.

What clean cross-channel identity actually takes, running on every lead.

Matching

Across Every Channel

Form fills, phone-ups, chats and DMs get compared on phone, email, name, vehicle and trade details, the way a sharp BDC manager would, on every lead.

Merging

History Preserved

Merges combine everything: every message, call note and touch from every channel lands on the surviving record. Nothing is thrown away.

Conflicts

Resolved, Not Clobbered

Two emails? Different spellings? Conflicting data is kept and ranked instead of overwritten, and uncertain matches wait for a human.

Ownership

One Buyer, One Owner

The merged record gets one assigned rep. The awkward version, two reps working one customer against each other, stops happening.

Guarding

Cadences De-Conflicted

Duplicate records mean duplicate follow-up. On merge, competing sequences collapse into one, so the buyer stops getting double texts.

Backfill

Your Existing Mess, Too

The matcher does not just watch new leads. It sweeps the records you already have and folds historic duplicates together on the same rules.

How It Runs At Your Store.

During the build we tune the match rules to your data and your risk tolerance: what merges automatically, what queues for review, what never merges. Then it runs on every inbound lead and, nightly, across the whole book.

Match confidence thresholds set with you: aggressive, conservative, or per channel.
Uncertain matches go to a human review queue, never a blind merge.
Full history from every merged record preserved and visible on the survivor.
Every merge logged with what matched and why, reversible from the audit trail.
Works alongside pipeline management, which handles the rest of the CRM's hygiene.

Straight Answers.

What if it merges two people who are not the same buyer?

That is the failure we tuned this against. Automatic merges only fire on high-confidence matches, everything borderline queues for a human, and every merge is logged and reversible. A wrong merge you can undo in one click is an inconvenience. Two reps quoting against each other is a lost deal.

Does it clean up the duplicates already in my CRM?

Yes. Alongside watching new leads, a sweep runs across your existing records on the same match rules: automatic merges where confidence is high, a review queue for the rest. Most stores are surprised by how much of their "database" is the same buyers wearing different hats.

Why do duplicates actually cost deals?

Because each copy gets its own follow-up. The buyer gets two different prices from two different reps, concludes your store does not talk to itself, and buys where the story was straight. De-duplication is not tidiness, it is message discipline.