How to write email subject lines and preheaders
The inbox envelope has three fields, not one: sender, subject, preheader. How to write them together, what your template breaks, and how to test on a small list.
A marketing lead sees the company newsletter on a phone for the first time, in a customer's screenshot. Three lines sit in the inbox list: a generic info address as the sender, a subject cut off halfway, and beneath it in pale gray, View this email in your browser. Two days went into the copy, an agency built the artwork, the list is clean. Yet of the three lines the reader judges, two came from a template default. The email is not going unopened. It is going unconsidered.
Subject line and preheader form a surface that deserves as much design as the body. This article covers the three fields of the inbox envelope, why the sender name outworks the subject, where a subject line actually gets truncated, how to use the preheader as the second half of a sentence, which rules flip by email type, why transactional subjects should be boring, when personalization backfires, what open rate now measures, and how to test on a small list.
How many fields make up the inbox envelope?
Most teams treat the subject line as a problem on its own. What the reader sees is a three-field block: sender name, subject, preheader. On mobile these stack, and the decision is made looking at all three at once. Leaving one blank hands a third of that judgment not to a competitor but to your template.
They do different jobs. The sender name answers do I know you, the subject answers what is this about, the preheader answers is it worth opening now. Have all three answer the same question and you waste space; have none answer it and the message slides down the list. Campaign structure more broadly sits in the fundamentals of email marketing; here the focus stays on those three lines.
The sender name does more work than the subject
In a crowded inbox the first filter is not the subject, it is the sender. Readers scan down the list picking out names they recognize and skipping the rest in bulk. One change there can outperform ten subject line experiments: a person's name plus the brand, instead of a department mailbox.
Consistency is the catch. Teams that change the sender name every campaign dismantle the recognition they are building, and weaken the way clients group messages from one source. Pick a name and keep it for months. In one-to-one sales email the sender is already a person, so the win sits in the subject and the first line instead. Ready-made structures live in sales email templates.
Where does a subject line actually get cut?
There is no single character limit. The cut-off shifts with device, app, font size and whether the phone is upright or sideways. You write for a wide desktop pane and a narrow mobile one, and the mobile one decides. So the useful rule is not counting characters but moving the distinguishing word to the front.
The distinguishing word is whatever separates this email from the forty around it. In October newsletter: the new reporting screen, that word sits at the end and disappears on a phone. New reporting screen: October newsletter carries the same information with the right half visible. Putting the brand name first is the same mistake in costume, since the brand already sits in the sender field.
Cutting a sentence in half to manufacture curiosity works exactly once. The second time the reader has learned there was nothing behind the break, and by the third they stop opening. A curiosity gap is borrowed attention, and it charges interest.
The preheader is the second half of the sentence
The preheader is the short text a client shows next to or under the subject. Its most productive use is to continue the subject rather than repeat it: the subject names the topic, the preheader names the payoff. Read together they should sound like one sentence — subject, New reporting screen; preheader, Cuts three steps off month-end close, two-minute summary inside.
The preheader gets truncated too, so the meaningful part has to fit in roughly the first forty characters. Anything after that is not lost, just never seen. Treat it as two pieces rather than one sentence: a visible hook and the completion behind it.
What happens if you leave the preheader unset?
The client does not leave the space empty. It pulls the first text in the HTML body, which in most templates is the View in browser link, sometimes an image's alt text, sometimes an unfilled personalization tag. The result undoes the impression of competence in one line, and it slips past every team that previews on desktop.
The subtler failure appears when the preheader is short. The client keeps filling the space with whatever text comes next in the body, so the reader sees something like Cuts three steps off month-end close Web version Unsubscribe. The fix is to close the field with invisible padding characters after your text. A trivial-looking detail that rescues one of the three lines the reader sees on every send.
Which rules flip depending on the email type?
Most subject line advice was written for one format, the marketing newsletter. Different message types going to the same list follow contradictory rules. The distinction below fits in a table and is the one most often skipped.
| Email type | Job of the subject line | Job of the preheader |
|---|---|---|
| Newsletter or campaign | Name the single topic inside | Say why it matters today |
| Product or feature news | State plainly what changed | Say who it affects |
| Transactional (order, invoice) | Be findable by search months later | Restate the next step |
| One-to-one sales email | Read as if written by a person | Continue the opening line |
| Reactivation | Acknowledge the time that passed | Make leaving easy |
That last row looks wrong at first glance. Making it easy to unsubscribe in a reactivation preheader shrinks the list short term and protects deliverability: an uninterested reader leaving quietly beats the same reader marking you as spam. Deciding which group gets which message is where customer segmentation pays for itself.
Why boring is correct in transactional email
For order confirmations, invoice notices and appointment reminders, the subject line's job is not to earn an open; these get opened anyway. Its real job is to be findable in an inbox three months from now. So a transactional subject should be predictable and search-friendly rather than creative: the action, the reference number, a date when relevant.
Dressing a transactional message in marketing language does two kinds of damage. It breaks retrieval, so searching an invoice number returns nothing. And it blurs the category: a notification that looks promotional trains the recipient to treat the next one the same way. Structuring these as a flow sits in automated order status updates.
The same logic governs automated sequences at the start of a relationship. A welcome subject should match exactly what the user expects at that moment; if they expect their account to be set up, say so. Creativity in the first step of a welcome email sequence serves confusion, not open rate.
When does personalization backfire?
Putting a first name in the subject was standard advice for years. Two things now argue for restraint. Technical: an unfilled tag appears across the whole list at once, and one merge failure cheapens the entire send. Perceptual: a name in the subject increasingly reads as evidence of a mass mailing, not a personal one.
Situation beats name. A subject that refers to something the reader did feels far more personal than one that spells their name: an unfinished checkout, a document they downloaded, a session they attended. We walk through building those triggered sends in drip campaigns.
There is one more limit. Personalization in the subject makes a promise the body has to pay. If the subject points at the reader's situation and the body serves the same text everyone got, opens go up and trust goes down. Most teams never see that trade, because the only side they measure is the open.
What does open rate measure now?
Most subject line testing runs on open rate, and that measurement has been badly muddied. Some clients prefetch images on the user's behalf for privacy reasons, recording an open even when the message was never seen. Genuine interest and automatic prefetching now sit inside one number.
If you cannot write the subject line, the problem is not the subject line; that email has nothing to say.
The practical consequence: treat open rate as a trend measured against your own history, never as an absolute score. For decisions, clicks, replies and the concrete action taken afterward are far more trustworthy. Reading that data on the sales side is covered in tracking email opens and clicks.
Here is the part that surprises people. The subject line's contribution to landing in spam is much smaller than the folklore suggests. Rather than memorizing banned words, look at sender authentication, domain reputation and reader engagement, which is where the outcome is actually decided; we cover those in deliverability and email authentication.
How do you test subject lines on a small list?
The classic answer is an A/B test, and on most small and midsize lists it misleads. Across a few hundred recipients the gap between two subject lines is usually noise, and the team turns that noise into a rule it applies to the next campaign. When testing is and is not meaningful is laid out in A/B testing.
On small lists, keeping a log beats running isolated tests. Record every subject line with a few tags: type, length, question or statement, number or no number, and how it related to the preheader. Three months later that table shows a pattern no single test could produce: what your list specifically responds to.
Test structure, not vocabulary. Question against statement, short against long, number against no number, benefit against curiosity. Word-level experiments manufacture noise; structural ones produce a habit you can reuse. For one-to-one email that expects an answer, reply rate is the cleanest measure available, and we take it apart in email reply rate.
The sixty seconds before you send
The subject line should be written last, after the email's single ask is settled. Reverse that order and it becomes a slogan with no relationship to the body. The short check below gathers what belongs in the final minute.
- Sender name: Recognizable, identical to the last three sends, showing a person alongside the brand?
- First words: Do the first three words of the subject, read alone, tell the reader the topic?
- Preheader: Written by hand, and does it continue the subject instead of repeating it?
- Field overflow: Does body text leak in after your preheader, and did you close the field with padding?
- Merge tags: What appears for records with empty fields, and is a fallback value defined?
- Mobile check: Was the test send reviewed in a phone inbox list, not a desktop preview pane?
- One ask: Is the action implied by the subject the same as the single action in the body?
Once that list lives inside your template, writing subject lines stops being a creative crisis and becomes repeatable work. There is still room for a good line; it is just no longer mandatory.
To see whether a subject line and preheader earned anything, send data has to sit beside the customer record. Rocketly keeps email sends, open and click data, segments and open deals on one screen; open a free account to build your own sending flow.