Key takeaways
- A newsletter headline is three separate pieces of text. The subject line earns the open, the preview text decides whether that happens on a phone, and the headings inside the mail decide whether anyone reads past the greeting. Each has a different length limit and a different reader.
- Leaving the preview text blank hands the decision to the mail client. Gmail pulls the first line of your body into that slot, which is usually a greeting or a view-in-browser link.
- Name the specific thing, not the genre. A subject that says what changed beats one that says a newsletter has arrived, and the word newsletter in the subject is the single most common self-inflicted wound.
- You cannot write these by open rate. Opens are an estimate, so judge your lines by clicks, replies and bookings instead.
Most advice about newsletter headlines treats the job as one sentence you have to make catchy. It is three sentences doing three different jobs, read in sequence by a person whose attention shrinks at every step. The subject line is read in an inbox list beside forty other rows. The preview text is read in the same half second, in smaller grey type. The headings inside the mail are read by someone already scrolling for the part that concerns them.
Write the three as one line and two of the three jobs go undone. What follows separates them: what each line has to achieve, how long it survives on a phone, a revision exercise on three client updates, and where the three fields sit in the tool you send from.
The three lines a reader actually sees
| Line | Where it appears | Its job | Practical length |
|---|---|---|---|
Subject line | The inbox row, in bold | Say what this mail is about, specifically | Around 35 to 45 characters survive on a phone in portrait |
LineSubject line Where it appearsThe inbox row, in bold Its jobSay what this mail is about, specifically Practical lengthAround 35 to 45 characters survive on a phone in portrait | |||
Preview text | Directly after or under the subject, in grey | Add the second fact the subject had no room for | Between 35 and 90 characters depending on the client |
LinePreview text Where it appearsDirectly after or under the subject, in grey Its jobAdd the second fact the subject had no room for Practical lengthBetween 35 and 90 characters depending on the client | |||
Headings inside the mail | Above each block of the mail itself | Let a skimmer find the part that affects them | Short enough to read without stopping |
LineHeadings inside the mail Where it appearsAbove each block of the mail itself Its jobLet a skimmer find the part that affects them Practical lengthShort enough to read without stopping | |||
The length figures move with the device, the text size and how the reader holds the phone, so treat them as a range rather than a rule. The reliable check is a test send you open on your own phone, which takes thirty seconds and beats any published character count.
Skipping the middle row is the most common mistake in that table. Leave the preview text field empty and the mail client fills it for you: a five-comment thread in r/GMail traces the behaviour to Google's own documentation, which says the snippet comes from the first line of the email's text unless you specify otherwise. That first line is usually a greeting or a view-in-browser link, so a third of your inbox real estate goes to punctuation. A ten-comment thread in r/Emailmarketing makes the same point from the sender's side: the slot only works if you fill it deliberately.
Write the subject line for the inbox, not the archive
Name the thing, not the genre
The reader already knows the mail is a newsletter. Telling them again costs you the characters you needed for the actual news. A five-comment thread in r/email argues it from the receiving end: the bracketed prefixes senders add out of politeness read as a filing label and invite the reader to file it. A practitioner who analysed a large batch of subject lines across a dozen industries put the word newsletter and generic offer language at the bottom of the list, in a seven-comment thread in r/DigitalMarketing. Neither is a controlled study, but a reader thread and a sender thread agreeing is worth more than one benchmark chart.
So drop the label and use the space for the noun:
- Before:
[Newsletter] October update from Berg & Co. - After:
New rates from 1 December - Why: the first names the format and the sender, both already on screen. The second names the one fact that changes what the reader does.
Put the specific noun inside the first 30 characters
Whatever survives truncation has to carry the meaning alone, so the concrete word goes near the front and the qualifiers behind it. That is the opposite of how most people write a sentence.
- Before:
A few important changes to how we handle appointment cancellations - After:
Cancellations: 24 hours' notice from March - Why: on a phone the second truncates to "Cancellations: 24 hours" and still carries the message. The first truncates to "A few important changes to how we", which describes every other mail in the inbox.
Pick one angle and commit to it
Three angles carry most client updates: news, where something has changed; a number, where the figure is the story; a named benefit, where the reader gets something. Curiosity is a fourth and the one to be careful with, because a subject that hides the topic wins the open and loses the reader on the second line, which costs more than a low open would have.
A ten-comment thread in r/Newsletters circles the same tension for curated sends: lead with the single most interesting item, or stitch several into one intriguing line. Leading with one item wins for client updates, because your reader opens on the strength of who you are, not how clever the line was.
The preview text: the line most people leave empty
Treat the preview text as the second sentence of a two-sentence paragraph. The subject makes a statement, the preview adds the fact that makes it actionable. What it must not do is restate the subject in different words, which is what happens when both fields get written by the same impulse thirty seconds apart.
- Subject:
New rates from 1 December - Preview:
Standard session goes from 90 to 98 euros. Existing packages unaffected. - Why it works: a reader who never opens the mail still leaves the inbox with the number and the reassurance. That is a legitimate outcome for an announcement, and only possible because the two fields say different things.
Length here is less predictable than the subject: some clients show a long snippet, some a short one, some hide it entirely in compact view. Front-load accordingly, so the first six or seven words work alone. Preview text is part of the message body, so filters read it like any other text, a point a nine-comment thread in r/Emailmarketing makes plainly, which rules out stuffing the slot with keywords. Going long is harmless though, since the surplus simply gets cut.
Headings inside the email do a different job again
Once the mail is open, the reader is deciding which part to read, and they do that by scanning headings and buttons. This is where the word headline is most literally correct, and where client updates most often have none at all, because the mail was written as a letter with a greeting and four paragraphs.
Three rules that hold across client updates:
One heading per block, naming that block's subject. An issue covering a rate change, a holiday closure and a new team member needs three headings. The reader affected by one of them should find it without reading the other two.
Don't repeat the subject line as the first heading. The reader has already read it, twice counting the preview. Use the top of the mail for the sentence that follows from it, the same way the preview text did.
Make the last heading the action. What you want the reader to do belongs above the button, phrased as the thing they get. Our guide to newsletter signup calls to action goes deeper on that phrasing, and it transfers straight to buttons inside a mail.
A ten-comment thread in r/internalcomms shows the failure mode: a mail that contains the information, that people receive, and that changes nobody's behaviour. An internal list is captive, so the problem shows up there in its purest form. Client lists fail the same way and unsubscribe about it.
A revision exercise: three client updates, three lines each
Before writing anything new, take a mail you've already sent and rewrite its three lines. Three worked examples.
A capacity note. Original subject: Our diary is filling up for the autumn. True, and it asks nothing. Rewritten: subject Two slots left in October, preview November opens on the 6th, existing clients first., first heading October: two Tuesday mornings. The number moved into the subject and the date into the preview, so the whole decision fits the inbox row. If capacity is a recurring lane for you, our piece on what to send clients and when sorts it from the other kinds of update.
A policy change. Original subject: Important update to our terms. The word important is the sender's opinion, and it survives truncation while the news does not. Rewritten: subject Late cancellations: new 24h rule, preview From 1 March, cancellations inside 24 hours are charged at 50%., first heading What changes on 1 March. If you're drafting the policy alongside the mail, the appointment cancellation policy template has the wording the mail summarises.
An event invitation. Original subject: You're invited to our client breakfast. Rewritten: subject Client breakfast, 14 Oct, 8:30, preview Forty minutes on the new reporting rules. Twelve seats., first heading Thursday 14 October, 8:30 to 9:15. Date and time belong in the subject for anything with a fixed slot, because the reader's first question is whether they are free. Our webinar invite guide covers the body structure, and for one-to-one requests the patterns in our meeting request email piece apply instead.
Notice what none of the rewrites do: get cleverer. They get more specific, which is the only reliable lever on a list of people who already know who you are.
Where these three fields live in your sending tool
Any tool that sends campaigns gives you a subject field. Fewer give preview text its own visible field, which is how it ends up empty. If you're still choosing a sender, our comparison of email marketing tools weighs that category by what it lets you edit.
In the meetergo Newsletter app, the two sit side by side: you choose a template, adjust the blocks, then write subject and preview text as separate inputs while the finished mail previews alongside. Headings are their own block, added by typing a slash in the editor, so the scannable structure gets built rather than improvised out of bold paragraph text. Merge tags for first name, last name, email and company leave a blank rather than a raw placeholder when a contact has no value stored. Because contacts come from the CRM and tags written by forms do the segmentation, the audience for a given set of three lines is a filter rather than an exported list.
Two honest limits. The app is in beta and switched on per workspace, so an admin requests access from the in-app catalogue rather than buying it on a plan. And there is no split testing: you can send yourself a test mail to see how the subject and preview look on your own phone, but you cannot run two subject lines against each other and let the tool pick. That matters less than it sounds, because the metric such a test would optimise is unreliable anyway. The report is candid that opens are an estimate while clicks are dependable, since Apple Mail loads images automatically and other clients block them. Judge your three lines on clicks, replies and booked appointments instead.
Common mistakes
Writing the subject last, in a hurry. It is the part most people see and the part that gets the least time. Write it first, then let the mail deliver what it promised.
Using the preview text to repeat the subject. Two versions of one sentence waste the second slot. With nothing to add, put the date, the number or the deadline there.
Putting a greeting at the top of the body. With no preview text set, the greeting becomes your inbox snippet. Keep it if you like it, but fill the preview field so it isn't doing double duty.
Sending campaigns from the same domain as your invoices. A subdomain such as news.your-company.com keeps the reputation your booking confirmations depend on separate from your marketing. Our guide to business email addresses covers the setup.
Chasing the open rate as the goal. A curiosity subject can lift opens and lower everything after them. What you care about is what the reader does next, and if that next step is a conversation, a personal booking link makes it one click.
Send your next client update from the system that holds the contacts. Free plan, no credit card required.
Booking + video conferencing in one tool.
Booking + video conferencing in one tool.
FAQs
How long should a newsletter subject line be?
Short enough to survive a phone. Roughly 35 to 45 characters holds up across common mobile clients in portrait, and the exact number depends on the device and the reader's text size. Write the version that works at 35, then confirm it with a test send rather than a character counter.
What is preview text and is it the same as a preheader?
The same slot under two names. Preview text is the short line the inbox shows beside or under the subject; preheader is the older term for the block of HTML text that fills it. Set it explicitly and the mail client uses that instead of scraping your first body line.
Should the subject line and the headline inside the email match?
No. The reader has already read the subject by the time the mail opens, so repeating it wastes the most valuable line inside the message. Let the first heading continue the thought, the way a second sentence follows a first.
Do emojis in the subject line help?
They make a row visually distinct, which is a real effect in a crowded inbox, and cost nothing in length. The risk is tonal rather than technical: an emoji on a rate change or a cancellation-policy mail reads as unserious. Keep them for the reading and event lanes.
How do I write subject lines for a multilingual client list?
Per language, not translated once. A subject that fits 40 characters in English often runs to 55 in German, which changes what survives truncation. If you segment by contact language, multilingual booking pages keep the linked page consistent with the mail.
Can I reuse a good subject line?
For a recurring lane, yes, with the variable part carrying the news: the same skeleton with a different number or date reads as a familiar format rather than a repeat. For announcements, no, because the thing that changed is the whole point. Operational mail is a separate case: confirmations and reminder emails want the same predictable subject every time, since the reader is hunting for them rather than deciding about them.
