The Same Prospect DM Is Duplicated: Deduplicate Before You Reply or Report It

A duplicate LinkedIn DM can arrive through a sync retry, an import, an integration replay, or two genuinely separate sends. The wrong move is replying twice or deleting evidence before anyone checks it.

Create a review record before sending a response. The record needs enough detail to decide whether the events are records of one delivery or two intentional messages, then enough history to explain the reporting decision later.

Are the two events records of one delivery or two intentional messages?

Start with identity and message evidence. Match the prospect, normalize the message text and compare the timestamps; then inspect the LinkedIn thread IDs and delivery evidence. A matching sender alone is weak evidence. Identical normalized text inside the same thread and a tight timestamp gap is stronger evidence of a duplicate event.

Do not merge or discard events merely because they look similar. HubSpot tells users to verify records are duplicates and review associated records before a bulk merge. Its merge guidance also says merged records cannot be unmerged. HubSpot, October 8, 2026

Which instance should receive the response?

Reply from the surviving event. Prefer the event with the clearest delivery evidence and the thread context your team will continue to use. Record the other event as suppressed or linked, rather than silently removing it.

If the evidence is incomplete, pause the response long enough to inspect the original conversation and the ingestion trail. Pipedrive recommends reviewing the available details and previewing the result before completing a merge. Pipedrive, September 3, 2026

• Keep the surviving event visible in the active inbox or CRM timeline.
• Assign one response owner before anyone drafts a reply.
• Preserve the suppressed event ID, review reason, and reviewer in the audit trail.

How should reply reporting avoid double counting?

Count the surviving event once. The suppressed event must not add another inbound reply, conversation, qualified prospect, booked call, or conversion opportunity. Keep the suppressed event in raw-event records so a later audit can reconstruct the decision.

Separate event volume from person-level outcomes. Two stored events may still be records of one prospect reply. A single response owner also prevents two people from answering the same person and creating a false second touchpoint.

Microsoft recommends duplicate-detection criteria based on fields with unique values, such as email, and provides controls for exact matching and blank values. That principle is useful here: make the matching rules explicit, then route uncertain cases to review. Microsoft Learn, December 16, 2025

What should the review rule look like in practice?

Use an automatic review flag when the same prospect has substantially matching message text and overlapping timestamps or thread evidence. Do not turn that flag into an automatic deletion rule. The review outcome must say whether the events were one delivery, two intentional messages, or unresolved.

Keep your rule narrow enough to avoid combining separate messages from the same prospect. Pipedrive identifies possible duplicate people by combining a same-name match with another matching attribute, such as phone, email, or organization. Pipedrive, September 3, 2026

• Mark one delivery when the evidence points to one message represented twice.
• Keep two events when the prospect sent distinct messages or the thread evidence differs.
• Mark the pair unresolved when the evidence cannot settle it, then exclude it from final conversion reporting until reviewed.