What Is a Subject Line?

Looking like a message from a person rather than a broadcast. Short, plain, sentence case, no marketing construction, and specific enough that the recipient can tell why it arrived. A subject that could have been sent to anyone reads as though it was, because it was.

Length matters mostly because of truncation. Mobile clients show fewer characters than desktop, and a subject whose meaning sits at the end loses it entirely, so the informative words belong first regardless of how long the line runs.

Anything that manufactures familiarity or urgency. A Re: or Fwd: prefix on a first touch implies a conversation that never happened, and a deceptive subject line is one of the specific things the CAN-SPAM Act prohibits. Capitals, exclamation marks and words like free and guaranteed read as bulk mail to both filters and people.

The other avoidable failure is mechanical. A merge tag that resolves to an empty value or the wrong capitalisation puts the error in the most visible field on the message, so subjects that depend on a contact field need a fallback and a check before the campaign runs.

At a pixel width rather than a character count, which is why no single number is right. A desktop client showing a three-pane layout gives the subject a narrow column, a phone in portrait gives it the full screen width but puts the sender name above it, and the same subject truncates in a different place in each.

What follows the cut is usually the preheader, which most list views append to the subject in lighter text. The reader takes the two as one line, so a subject that runs long does not simply lose its ending, it hands over mid-word to a sentence written for a different purpose. Putting the informative words first is what survives every layout.

The same one, in most sequences. Keeping the subject is what makes the second and third messages read as one continuing approach rather than three unrelated ones, and it lets the recipient see the earlier message directly above when they finally open it. Threading is driven by the In-Reply-To and References headers rather than by the text, but a subject that changes underneath a thread looks like a mistake.

Change it only when the angle genuinely changed, for instance when a later step offers something different rather than repeating the first ask. The version worth avoiding either way is a Re: added to a message nobody replied to, which claims a conversation that never happened and is noticed immediately.

Company name usually helps, because it signals the message was aimed rather than blasted, and the recipient can place it immediately. A first name in the subject often does the opposite: the pattern is common enough in bulk mail that it now reads as automation rather than attention.

This is a genuine test rather than a rule, and it is one of the few subject-line questions worth spending campaign volume on, because the answer differs by audience and the mechanism for measuring it is straightforward.