Duplicate lead records can split a conversation between salespeople, trigger conflicting messages, and make reporting unreliable. A merge should be a reviewed decision with a clear surviving record and a recoverable history.

Find reliable match signals

Compare email, phone, vehicle, request time, source, conversation, and appointment context. Treat a shared household contact or similar vehicle interest as a reason to review, not automatic proof of duplication.

Show a merge preview

Display records, field differences, activities, consent states, assignments, attachments, and source history before any change. The lead deduplication checklist helps make the decision criteria explicit.

Set field precedence

Define which value wins for contact details, vehicle, department, owner, status, source, and next task. Preserve both values when the difference itself is useful evidence.

Protect customer preferences

Do not erase opt-outs, channel preferences, or an interaction that explains why a customer should not receive another message. Keep consent history tied to the correct person and purpose.

Keep merge history auditable

Record actor, time, reason, source records, surviving record, field decisions, and restore path. Restrict access to personal details and attachments while allowing the right manager to investigate.

Measure correction quality

Track duplicate rate, false merges, split conversations, response delay, restore events, and lead outcome. Review after form, CRM, campaign, import, or assignment changes.

Duplicate leads splitting customer ownership? Ask Vertinus to make CRM merge decisions visible and recoverable.