A Prospect Says Your LinkedIn DM Never Arrived: Verify Before Resending

A prospect saying they never received your LinkedIn DM does not establish that the message failed. It establishes a dispute between two views of the same conversation. Treat it like an operations record, not an invitation to send the same note again.

The immediate job is simple: preserve what the sender can see, record what the buyer says they can see, name one person to decide whether a resend is allowed, and close the case after a defined duplicate-watch window. The goal is a clean conversation history, not a guess about LinkedIn delivery mechanics.

That restraint matters. LinkedIn says it does not allow gratuitously repetitive messages, and its community policies prohibit spam, including unwanted or repetitive messages. A resend should be the exception you can explain later, not a default follow-up.

What evidence can establish the message state?

Start with the sender-side thread. Capture the original message text, the timestamp shown in the thread, the recipient profile URL, and any message ID your operating system records. Save the thread state as seen at the time of review. Do not edit the original message, delete it, or replace the record with a summary.

Then record the buyer statement exactly enough to preserve its meaning. "I did not receive it" is different from "I saw it later," "I cannot find the thread," or "Please send it again." Do not convert one statement into another.

Read or notification signals can add context when they are available to the account holder, but they do not prove what happened outside that view. Record them as available evidence, not as a verdict. LinkedIn's User Agreement says the service may change or limit features and does not promise to store or keep showing information shared through the service.

• Original message ID, if your system exposes one.
• Original timestamp and sender-thread state.
• Recipient profile URL and campaign or account context.
• Buyer statement, with the date and channel where it was made.
• Available notification or read evidence, labeled as available evidence.
• Verification owner and the time the record was reviewed.

What belongs on a delivery-dispute reconciliation card?

Use one card per disputed message. The card keeps the original event and any replacement connected, so the team can answer a basic question later: did we resend because we verified a need, or because we lost track of the first message?

This is a comparison of records, not a scoring system. Do not add a confidence percentage or claim that any one signal proves delivery. The card should show what is known, what is reported, who owns the next decision, and when the duplicate watch ends.

When may one controlled resend happen?

A controlled resend is a recommendation for a narrow case: the sender-side review cannot confirm that the original message remains available in the thread, and either the prospect explicitly asks for it again or the account owner approves a resend after reviewing the record.

Use one replacement only. Write it as a replacement, not as a claim that LinkedIn failed. Keep it short, state that you are resending at the prospect's request or after checking the thread, and avoid adding a new pitch, attachment, or second call to action.

Do not resend when the original message is plainly visible and the prospect has not asked for another copy. Do not send multiple versions through different accounts or channels to force an answer. LinkedIn's policies say members should not send unwanted or gratuitously repetitive messages.

• Confirm the original record before touching the thread.
• Get buyer request or named resend authority.
• Send one replacement from the same legitimate conversation context.
• Link the replacement record to the original event.
• Open the duplicate-watch window immediately after the replacement.

How should the replacement message read?

Keep the replacement factual. It should acknowledge the report, identify the message as a resend, and give the prospect a simple way to continue or decline. Do not imply a platform outage, a delivery guarantee, or a technical diagnosis you cannot prove.

For example: "Thanks for flagging this. I am resending the note here in case the first one did not surface for you. If this is not relevant, no need to reply." This preserves the prospect's control and avoids pretending that the original history never happened.

If the message contains sensitive information, do not copy extra personal details into an internal reconciliation card. LinkedIn's community policies prohibit revealing another person's personal or sensitive information. Record only the evidence needed to resolve the outreach event.

How long should the duplicate-message watch stay open?

Set the watch window before sending the replacement. The duration is an internal operating decision, not a LinkedIn rule. Its purpose is to prevent another team member, sequence, or workflow from sending the same person another version while the dispute remains open.

During the window, pause duplicate follow-ups connected to the original event. Watch for a reply that refers to the first message, a reply to the replacement, or evidence that both versions surfaced. Record the observation against the same reconciliation card.

Close the card with one plain outcome: no duplicate observed, duplicate observed, buyer replied, buyer declined, or escalation required. Preserve both message records. The history should explain the decision without asking someone to reconstruct it from memory.

What should happen when the dispute points to a safety concern?

A delivery dispute is usually an outreach operations issue. It becomes a safety issue when the prospect reports suspicious content, impersonation, fraud, harassment, or another concern that should not be handled through a resend.

Stop the resend path in those cases. LinkedIn says members can report inappropriate or unsafe messages directly on the site, and its help guidance covers suspicious messages. Preserve the minimum necessary record, follow the applicable internal escalation route, and do not ask the prospect to repeat sensitive details.