Subject Lines and Preview Text: The First Conversion

Write the subject line to state, specifically and truthfully, what this email contains and why this reader, and write the preview text to extend that statement rather than repeat it - together they are the email's headline and subhead, judged in the inbox in about a second. Specificity beats cleverness: the delivery cut-off with its date, the guide with its topic, the product back in stock by name. Tricks that buy opens by misdirection - false replies, false urgency, a question the email never answers - spend the sender's name, which is the asset every future open depends on. On this bench, the subject line is a promise, and it is kept or the programme pays.

Compare two subjects for the same email: Big news inside, against, The resoleable boots are back, in wide fit, until Sunday. The second filters kindly - the reader who cares opens now, the reader who does not deletes without resentment, and both learn that this sender's subjects tell the truth, which raises the open rate of every later email including the vague ones you will inevitably send. Specificity also survives the inbox's reality: truncated on phones, scanned in a list of thirty, judged against senders with bigger budgets and louder claims. Plain accuracy is the small sender's only durable edge in that list, and it compounds.

The preview snippet is written, not inherited: left alone, most inboxes fill it with the email's first line, which is usually a greeting or a view-in-browser instruction - a wasted sentence at the exact point of decision. Write it deliberately as the subject's continuation: the subject names the thing, the preview gives the term, the date or the second reason. Keep the pair readable when the preview is cut short, never hide the email's real content behind a preview that promises a different one, and check the pair in a real inbox on a phone, because that is where the decision the pair exists for is actually made.

Never fake a reply or forward (Re: in a first contact), never claim an order, delivery or account event that did not happen, never personalise with a name the data cannot support, and never let urgency outrun the facts - the deadline in the subject must be the deadline in the email and on the page it lands on, per email-to-page continuity. Regulators including the FTC treat deceptive headers as deceptive advertising, but the commercial reason suffices: header tricks are a loan against the sender's name at a ruinous rate, repaid from the opens of every future campaign, including the ones that would have saved a slow quarter.

Flow emails - the welcome of the welcome guide, the cart reminder of abandoned cart emails - should be recognisable as a continuing conversation: consistent sender name, subjects that name the flow's content plainly (Your basket, kept for you; The guide you asked for), no novelty for its own sake. Campaigns carry news and may work harder for the open, within the honesty rules. Confusing the two - a welcome email with a shouty campaign header, a service message with a teaser subject - breaks the reader's model of your mail, and a broken model is read as untrustworthiness even when the content is innocent.

Subject line tests at small scale detect only large differences, so run them sparingly and structurally: a specific against a vague line, a question answered in the email against a statement, the product named against the category named - and read the winner on clicks and orders, not opens alone, because a header can win opens and lose everything downstream. Most of the gain at small lists is not in testing but in the standing discipline: every header drafted against this guide, the pair checked on a phone, the promise verified against the email's first screen. Folklore about power words expires monthly; your own log of what your readers opened and acted on does not.

Readers decide by sender first, subject second - which is why the from-name must be stable, human and identical across flows and campaigns: the business name, or a real person's name at the business, used consistently enough to be recognised in a split second. Changing sender names to chase attention (a new persona per campaign) resets recognition to zero each time and mimics the behaviour of senders people have learned to fear. Pair that stability with a reply address that reaches a person, and read the replies: they are the only header research that arrives with its reasoning attached, and the parent bench, email capture and flows, counts them as programme data.