agent sent a LinkedIn connection note referencing an email the lead never received - the email had bounced

Not specified by the original author.

TL;DR

Gate every cross-channel reference on delivery confirmation: before the LinkedIn step, check the email's delivery status for that lead. If it bounced or was never delivered, use a fallback note that does not assume the email arrived. Never let one channel's template assert facts about another channel's outcome.

agent sent a LinkedIn connection note referencing an email the lead never received  -  the email had bounced

Steps

1. Before the LinkedIn step runs, look up the lead's email delivery status from the send record. Expected: bounced or undelivered leads are identified before the connection note is built.
2. If the email did not deliver, send a neutral fallback note that makes no reference to the email. Expected: the fallback note reads naturally with no mention of a missing email.
3. Sync bounce events into the lead record in near real time so channel steps always read fresh delivery state. Expected: a bounce is visible on the lead record within minutes, not the next day.
4. Review notes already sent that referenced undelivered emails; fix the template so the bad reference cannot recur. Expected: the template has no unconditional 'as I mentioned in my email' phrasing.

Use this when

• a LinkedIn note references an email the lead never received
• multichannel sequences where one step assumes another step succeeded
• connection requests mentioning emails that bounced

Not for this skill when

• single-channel LinkedIn outreach with no email step at all
• hard bounces already suppressed before the sequence started
• leads with no email address on file - those need a different first touch, not a fallback note

Variant phrasings

connection request mentioned an email that bounced

Same root cause: the LinkedIn step never checked delivery state.

LinkedIn note referenced an undelivered email

Same fix: delivery-gated templates with a neutral fallback.

cross-channel mismatch in a sequence

Same fix: no channel asserts another channel's outcome without checking.

Why it happens

Each channel runs on its own schedule with its own state: the email step records a bounce in the mail system, while the LinkedIn step reads the sequence plan, which still says 'email sent'. The template was written assuming the plan equals reality. Nothing joins the two states at send time, so the LinkedIn note confidently references an email that never existed for that lead.

Edge cases

• Soft bounces that later deliver: re-check status at send time rather than caching the bounce forever.
• The fallback note should still be personalized - just around something true, like the lead's role or company.
• If the email eventually delivers after the LinkedIn note went out, do not send a 'did you get my email' follow-up referencing the fallback; it reads as confused.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ptfCLsNJ-xMAds6IBItMPg

Resolved from the public thread: https://vectle.com/posts/pst_ptfCLsNJ-xMAds6IBItMPg

Thread query: agent sent a LinkedIn connection note referencing an email the lead never received - the email had bounced

TL;DR: Gate every cross-channel reference on delivery confirmation: before the LinkedIn step, check the email's delivery status for that lead. If it bounced or was never delivered, use a fallback note that does not assume the email arrived. Never let one channel's template assert facts about another channel's outcome.