Suped

Should I include a "you've received this email because..." message in COVID-19 related emails?

Summary

During periods of crisis, such as the COVID-19 pandemic, marketers often grapple with how to communicate sensitive and timely information to their audiences without appearing intrusive or opportunistic. One common question that arises is whether to include a you've received this email because... message at the beginning of an email. While such a message aims to provide context and reassure recipients, its effectiveness and potential impact on deliverability and recipient perception need careful consideration, especially when audience engagement has been historically low.

What email marketers say

Email marketers often balance the need for transparent communication with the desire to maximize engagement and avoid spam folders. When considering a phrase like you've received this email because... especially in crisis-related emails, marketers tend to prioritize clear, immediate value proposition over explicit disclaimers at the email's outset. The goal is to ensure the message resonates quickly, without triggering spam filters or appearing unnecessary.

Marketer view

Marketer from Email Geeks suggests that marketers often debate the inclusion of a you've received this email because... message, especially for critical updates. They noted that most businesses do not seem to include such a message prominently in their COVID-19 related communications.

17 Mar 2020 - Email Geeks

Marketer view

Marketer from Email Geeks recalls that in the past, there was a rule in SpamAssassin that would assign a negative point value to text similar to you've received this message because. While SpamAssassin isn't as widely used, the sentiment about such phrasing potentially being problematic persists.

17 Mar 2020 - Email Geeks

What the experts say

Email deliverability experts advise marketers to prioritize recipient trust and inbox placement above all else. While providing context for an email's receipt is generally good practice, its placement and phrasing are critical. Experts highlight that aggressive or unnecessary introductory phrases can sometimes be misconstrued by spam filters or disinterest recipients, especially when the message's primary purpose is urgent or informational, as was often the case during the COVID-19 pandemic.

Expert view

Expert from Email Geeks, steve589, emphasizes that while SpamAssassin's influence has waned, the underlying principle of avoiding potentially trigger phrases in email content remains relevant for optimizing deliverability. He questions the necessity of such a disclaimer at the top versus focusing on engaging content.

17 Mar 2020 - Email Geeks

Expert view

Expert from Email Geeks, wise_laura, suggests that email content should be designed to immediately answer What's in it for me? for the recipient. Any introductory text that delays this answer could lead to decreased engagement.

17 Mar 2020 - Email Geeks

What the documentation says

Official email marketing and anti-spam documentation generally focuses on transparency, consent, and providing clear unsubscribe options, rather than dictating specific introductory phrases. The emphasis is on the overall content's compliance and intent, ensuring it does not mislead recipients or appear unsolicited. Documentation suggests that while a clear reason for receiving an email is important, it does not necessarily need to be the leading element of the message, especially if it detracts from critical information.

Technical article

The CAN-SPAM Act Compliance Guide states that emails must include a clear and conspicuous way to opt out of receiving future emails, and the sender's physical postal address, but does not specify where a 'reason for receiving' message should appear.

16 Jan 2023 - FTC

Technical article

RFC 2142, a technical specification for email address conventions, suggests that a 'postmaster' address should be available for inquiries, but does not touch upon content such as 'you've received this email because...' messages.

18 Mar 1997 - IETF RFC 2142

3 resources

Start improving your email deliverability today

Get started