7 Cold Email Preheader Rules That Earn the Open

What a Cold Email Preheader Actually Does

A cold email preheader is the short line of preview text that appears next to or beneath your subject line in an inbox list, as Mailchimp's help page on preview text describes. It is the second thing a prospect reads, and frequently the one that decides whether they open at all.

Most senders write a subject line, hit send, and let the preview fill itself with whatever the body happens to start with. The problem is invisible in the editor, and it still costs opens.

Its job is narrow: extend the subject line with a reason to open, without repeating it. It helps to write the two as a single sentence broken across two lines.

Where Preview Text Shows Up in the Inbox

Preview text appears after the subject line in the inbox list, in Gmail, Outlook, Apple Mail, and most mobile clients. The client pulls it from the first text in the email body unless you set it yourself.

That default is where things go wrong. If your email opens with a logo image, the client skips to the next text it can find, often the image's alt text or the greeting, and "Hi {{first_name}}," takes the front of the preview where your offer should be.

Set the preheader deliberately and you control both visible lines. Skip it and the client decides for you.

Email Preview Text Length and Truncation by Client

Preview text length is not fixed across clients. Each one cuts the line at a different point, and mobile cuts sooner than desktop.

A practical target is 40 to 90 characters. That survives most desktop inboxes while still leaving mobile clients a meaningful fragment. Past roughly 100 characters you are gambling on where the cut lands.

Treat those numbers as approximations rather than limits you can design against. The actual cutoff moves with window width, font size, how long the subject line is, and whether the client stacks the preview on its own line. Litmus has a guide to how preview text works and recommends staying under 90 characters. What holds across all of them is that a prospect reading on a phone may see only the opening words, so those words have to do the work.

How to Write Cold Email Subject Lines That Pair With the Preheader

Subject lines and preheaders work as a pair, so write them in the same sitting rather than one after the other. The subject gets you the glance. The preheader has to turn that glance into an open.

A rule that holds up: the subject line states the topic, the preheader states the reason. If the subject asks a question, let the preheader gesture at the answer without handing it over.

• Subject: "Your onboarding drop-off" → Preheader: "One idea that cut our setup time in half."
• Subject: "Planning the Q3 rollout" → Preheader: "The one step teams skip, and what it costs."
• Subject: "For the team handling support tickets" → Preheader: "A two-line fix for a growing ticket backlog."

None of those pairs repeat themselves. Each preheader introduces something the subject line did not already say, and that is most of the technique.

For the wider structure these lines sit inside, the four-to-seven email cold sequence structure shows what each email in the sequence is there to do.

Cold Email Preheader Best Practices That Survive a Real Inbox

The preheaders that hold up are written for a cluttered inbox rather than for a slide deck. Seven rules do most of the work:

1. Keep it to roughly 40 to 90 characters.
2. Put the strongest words in the first 40 characters.
3. Extend the subject line instead of echoing it.
4. Cut the greeting. "Hi there" spends your most valuable line on nothing.
5. Give the reader something concrete: a number, a name, an outcome they can picture.
6. Make sure the body delivers whatever the preheader promised, and in the first paragraph, not the fourth.
7. Keep it plain. No emojis, no all caps.

There is one trap specific to cold outreach. A preheader that sounds like a mass send gets treated like one, and "Don't miss out" or "Limited time" is close to an invitation to hit report spam. Write the line the way you would say it to one person.

Before you tune copy, it is worth knowing where your mail lands. Running a test of where your cold email actually lands tells you whether inbox placement is the real problem, because no preheader rescues an email that never arrives.

Email Preheader Examples by Audience and Goal

Different prospects need different hooks. The preheader should match the audience and the goal of that specific email.

Every one of those gives the prospect a reason to open. None of them summarize the email, which is the usual failure mode: a preheader that is accurate, polite, and completely uninteresting.

How to Add Preview Text in Your Sending Tool

You set preview text in one of three places depending on how the email is built, and knowing which case you are in prevents the most common failure, which is writing a preheader the client never shows.

The hidden-preheader technique is the easiest of the three to get wrong. Some clients strip or ignore the hiding styles and render the line to the recipient, which looks broken. And if the hidden text is shorter than the preview space, the client fills the rest of the line from the body, so "Hi Sam," or "View in browser" runs on after your preheader. The usual fix is to pad the end of the hidden line with invisible characters.

One more thing to check: if your email opens with a logo image, some clients show its alt text and the rest fall through to the next text node, which is usually the greeting. That is how Hi {{first_name}} ends up as your preview.

Plain-text cold email has no separate field and no hiding trick. The first line of the body is the preview, so write it as a sentence that stands on its own and earns the open, then start the greeting underneath it. Opening with "Hope this finds you well" or a bare first name means that is what leads the preview.

SEMAOS has a preheader field in both template editors, and it goes out with sequence and broadcast emails. Leave it blank and the inbox shows the first words of the body. A short preheader is fine: SEMAOS pads out the rest of the line so your body text does not run on after it. You can write up to 200 characters, though the 40 to 90 above still applies, and send yourself a test to see how it reads. A one-off email you write in the composer, or load from a Simple template, has no preheader, so its first line is the preview. If you are still working out what the surrounding email should say, our guide to writing the cold email body itself covers the copy that has to deliver on whatever the preheader promised.

Testing Preheaders Without Breaking Your Subject Line Data

Test the preheader on its own or the result tells you nothing. Change the subject and the preheader together and you have no way of knowing which one moved the number. A clean test freezes the subject line and splits the audience on the preheader alone.

Run your current preheader against the new line, split evenly, and read replies alongside opens. Opens on their own will mislead you. Apple Mail's privacy feature and some corporate security scanners load images whether or not a human ever read the message, and privacy features elsewhere block the pixel outright, so the number is noisy in both directions at once.

A split that is too small also proves nothing. Send each variant to a few dozen people and the gap between them is noise wearing a result's clothing. You need a meaningful slice per variant before a difference means anything, and plenty of small lists simply cannot support a clean preheader test.

How long to wait depends on your reply cycle. Cold outreach replies often come in over several days rather than hours, so calling a winner after twenty-four hours just picks whoever checks email fastest. Give both variants the same window, and resist stopping one early because it looks ahead.

If you are testing inside a broadcast, the rules for A/B testing a broadcast without wrecking your sample cover how big a test slice needs to be and how the winner gets sent to the rest. On the sequence side, the cold email metrics that actually matter explain which numbers to trust when opens are noisy.

Set Your First Preheader Test in SEMAOS

Writing a preheader deliberately takes about a minute. Getting any signal from it takes longer, because one test on one send rarely tells you much and the useful pattern only shows up across a dozen of them.

To test a preheader in a SEMAOS broadcast, which needs a paid plan or the trial, put the two lines on two otherwise identical templates, add a second subject line to start the A/B test, tick the option to test different content, pick one template per variant, and type the same subject on both, because a variant's subject replaces the template's. By default the variants split the whole list and you get a report.

Testing on a share first and sending the winner to the rest is an opt-in. With it on, a content test is judged on clicks per delivered email and needs at least 100 delivered per variant and a 2-point lead. Anything short of that sends variant A, and an email with no tracked link has no clicks to compare, so A goes out every time. A preheader's effect shows up in opens first, so read the per-variant open rates on the results page too. Replies are not broken out by variant.

Sequences have no A/B test, so testing one means building two sequences and splitting the contacts yourself. From a connected mailbox, opens are tracked only if you turn them on, clicks also need a custom tracking domain, and replies are detected automatically only on Outlook, so on Gmail you count them by hand.

Pick one broadcast, or one sequence you can run as two, hold the subject line steady, and write two preheaders for it. Then do the same thing on the next send.

FAQ