From name and preheader: the two fields that drive opens

Once a message passes authentication and spam filtering, the next decision is made entirely by the recipient looking at three things in their inbox list view: From name, subject line, and the preheader (the snippet of text shown after the subject, pulled from the start of the message body unless you override it). Deliverability work gets a message to this point; these fields decide what happens next.

How clients actually render these fields

• Gmail (mobile and desktop list view): From name, subject, then a grey preview snippet pulled from the message body's first visible text - unless a hidden preheader string is present, in which case that is used instead.
• Outlook / Microsoft 365: similar pattern, From name and subject prominent, preview text pulled from body or preheader beneath.
• Apple Mail (iOS/macOS): shows two to three lines of preview text by default, more generous than Gmail's single-line snippet, which means a weak preheader is more visible as a problem on Apple Mail than on Gmail.

The preheader mechanic

If you do not set a deliberate preheader, most clients fall back to whatever text appears first in the rendered body - frequently "View this email in your browser" or a stray alt-text string from an image, because that happens to be the first text node in the HTML. This is the single most common wasted-space mistake: the highest-visibility real estate in the inbox list view defaulting to boilerplate nobody meant to be the pitch.

The standard fix is a hidden preheader block placed immediately after the opening <body> tag, styled to be invisible in the rendered message but present in the HTML source for clients to read:

<div style="display:none; max-height:0; overflow:hidden; mso-hide:all;">
  Your Q3 deliverability report is ready - three mailboxes need attention.
</div>

The mso-hide:all property additionally hides it in Outlook desktop clients using the Word rendering engine, which otherwise can render display:none content visibly in some versions.

From name: consistency beats cleverness

The From name is the single strongest trust and recognition signal in the list view, ahead of the subject line for most recipients deciding whether to open. The two most common failures:

• Changing the From name between sends. A recipient who has mentally filed "Jane at Example Co" as trustworthy does not necessarily recognise "Example Co Marketing Team" as the same sender, and inconsistency itself reads as suspicious to an experienced inbox user, independent of content.
• A From name that does not match the authenticated domain. A From name claiming to be a well-known brand while the underlying From address is an unrelated domain is exactly the pattern spam filters and savvy recipients are trained to distrust - keep the displayed name and the actual sending domain visibly related.

A before/after comparison

Testing what actually renders

Preview text handling varies enough between clients that what you see in your own ESP's preview pane is not reliable evidence of how it renders elsewhere. Send a live test to accounts on Gmail, Outlook and Apple Mail and check the list view directly on each, not just the opened message - a hidden preheader that renders correctly inside the message body but is not actually being picked up as preview text by a given client is a common and easy-to-miss gap.

Keep a short running log of what each client actually showed for a handful of recent sends - client rendering behaviour changes with app updates, and a preheader technique that worked reliably six months ago can silently stop being picked up after an update to a client's rendering engine, with no error or warning anywhere in your own sending pipeline.

What not to do

Do not leave the preheader unset and let it default to boilerplate - that is wasted prime real estate on every single send. Do not change your From name between campaigns without a specific reason; stability builds recognition the same way a consistent sending pattern builds domain reputation. And do not stuff the preheader with repeated keywords or ALL CAPS urgency language - content filters weight this alongside subject-line signals, and it reads as spam-like to recipients regardless of what the filter does with it.

Where MailPilot fits

MailPilot measures real inbox placement per provider through a seed-inbox network, which tells you whether a message is actually reaching the inbox tab recipients check - the From name and preheader work covered here is what determines whether a message that lands there gets opened, and both matter together: placement without engagement and engagement without placement are each incomplete on their own.