Updated · 8 min read
Subject line anatomy: the four parts every line that performs shares
Subject-line advice usually fixates on details: emoji or not, length, numbers vs words. The details matter less than the structure. The lines that consistently out-open the inbox share a four-part anatomy that keeps them scannable, specific, credible, and low-stakes to read. Here's the anatomy, the three ways programs distort it, and how to test without fooling yourself.
By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
Picture the inbox at 7:14am
Subject lines don't need to be clever. They need to be scannable, specific, credible, and low-stakes. Clever is a bonus, not a requirement.
Picture the moment your email actually shows up. Tuesday morning, 7:14am, your reader is in bed, thumb on the lock screen, twenty-three new messages stacked between an Uber receipt and their dentist's reminder. They'll read the sender name, two-thirds of a subject line, maybe the start of the preheader — the bit of text that previews after the subject — and decide. Open, archive, or leave for later (which is archive with extra steps).
That's the entire window. Whatever your subject line does, it does it in roughly two seconds against twenty-two other claims on the same attention.
The lines that survive that triage share four components, usually in this order. They're not stylistic preferences — each one is doing structural work.
1. A specific noun.Not "news" or "update" — the actual thing. "Your March invoice". "3 new templates". "The IP warm-up plan" (IP warm-up: the gradual ramp of sending volume that mailbox providers expect from a new sender). Specific nouns create an information scent the reader can scan for. Abstract nouns read as generic, because they are.
2. A reason.Why should this person care, specifically? "Your March invoice is ready" has a reason — it's ready, implying action. "3 new templates we built this week" has a reason — they're new, they're by you. No reason, no open. The noun without the reason is a label on an empty box.
3. Credibility.Implicit or explicit. "Your March invoice" is credible because it's transactional and timely — the reader knows roughly when to expect it. "New features you'll love" reads as sales because the claim is unsupported. "New features that ship this week" is credible because it's dated and specific. The reader has somewhere to put the claim.
4. Low emotional cost.The line shouldn't demand emotional labour to parse. Urgency ("Don't miss out!") is emotional cost. Curiosity loops ("You'll never guess…") are emotional cost. They ask the reader to spend something — anxiety, attention, trust — before the open has earned anything back. Specificity plus credibility beats urgency plus curiosity at almost every tier of engagement.
Where the line actually lands on the screen
The four parts only matter if the reader can see them. Most subject-line drop-off is length-related, not content-related — the line gets cut off before the part doing the work shows up.
30–50chars
Visible subject line width on most mobile clients. Anything longer truncates.
~6words
Sweet spot for mobile-first audiences. Scannable at a glance.
~60chars
Desktop Gmail visible width. Keep the critical words up front.
A 90-character line is truncated in the inbox. The reader sees the first 40–50 characters and decides. If your specific noun sits in the middle of the line, it never gets read — you wrote a line for a screen the reader will never see.
Design for the first 40 characters. Everything past that is bonus text for desktop preview, not where the decision happens. Preheader text — the secondary line of preview text rendered next to or below the subject — is where the second-pass scan earns its keep, and the preheader guide covers the mechanics. The rule: preheader complements the subject, never duplicates it. Repeating the subject wastes the exact real estate where a second argument could live.
The three habits that break a clean line
Most teams know roughly what a good subject line looks like, then ship one of these three patterns anyway because the team brief said "make it pop." All three are subtractive — they cost more open rate than they buy.
Emoji as emphasis.One emoji that visually represents the noun is fine. Two or more read as spammy and, on some mobile clients, break subject-line truncation in unhelpful places. The bar: use an emoji when the noun itself is ambiguous and the emoji disambiguates it ("🎉 Your 100th send"), not as decoration that's trying to do the work the words wouldn't.
Personalisation as gimmick."Justin, check this out" reads as manipulation. The first-name-in-subject pattern is decades old and most users filter it unconsciously — like an ad they no longer see. The open-rate lift has decayed year-on-year since about 2015. If you're going to personalise, personalise something that matters — a specific account detail, a specific outcome, a specific next step — not the name field.
All-caps urgency."LAST CHANCE" and "DON'T MISS" are conversion-negative in every test I've watched. They trip spam filters, they read as low-quality sender, and the users who open anyway are the lowest-converting tier — the ones who'll click anything urgent and buy nothing. Urgency lands when the timing is genuinely scarce ("Ends 5pm Friday"). It doesn't land when the caps key is trying to manufacture it.
Testing subject lines without fooling yourself
Subject-line A/B tests — A/B test: send variant A to half your audience, variant B to the other half, see which performs better — are low-effort to run and high-noise on small audiences. Most teams run them like dice rolls and put the winner in a deck the next morning. Four rules keep the dice honest.
1. Test hypotheses, not variants."Specific noun vs generic noun" is a hypothesis — it produces a finding you can reuse next quarter on a different campaign. "Blue vs green button" is a colour test that happens to use subject lines as the randomiser. The second teaches you nothing generalisable. Write down the hypothesis before you build the test; if you can't, the test isn't one.
2. Measure click, not open. Apple MPP — Mail Privacy Protection, Apple's 2021 feature that pre-fetches emails before the user opens them — inflates opens for Apple Mail users to roughly 100% regardless of whether the human ever saw the message. Clicks still reflect humans doing things. The MPP guide has the mechanism and what to use instead.
3. Power the test for the effect you care about.A 3% relative lift on a 5,000-recipient variant needs around 50,000 conversions to detect reliably. Most teams don't have that volume, which means most subject-line tests are answering a question they can't actually answer — and then someone puts the result in a deck. Either run the test against an effect size your audience can detect, or accept you're running it for the ritual.
4. Kill the novelty effect. New variants can outperform for three to seven days on novelty alone — readers click the unfamiliar one before reverting to baseline. Run the test for at least two full cycles of your natural sending rhythm before reading results. Anything shorter is a vibe, not a finding.
The Orbit Lifecycle Copy Framework skill covers the four-part anatomy in more depth, including the tone-of-voice mapping for each part by channel.
Read to the end
Scroll to the bottom of the guide — we'll tick it on your reading path automatically.
Frequently asked questions
- What makes a good email subject line?
- Four ingredients. Specific (names a thing the reader can visualise, not abstract), short enough to not truncate on mobile (~35-55 chars is safe), carries a concrete hook rather than generic curiosity ("Your Tuesday delivery is out" beats "Update for you"), and flows into the preheader rather than duplicating it. Bad subject lines fail one or more: too long, too vague, no hook, or the preheader restates the subject.
- How long should an email subject line be?
- 35-55 characters is the safe zone for mobile visibility. Gmail desktop shows ~70 characters; iOS Mail cuts around 35-40 depending on portrait/landscape; Apple Watch truncates aggressively at ~20. If the subject line makes sense truncated at 35, it'll work everywhere. Longer subject lines can work on desktop but consistently underperform on mobile, where the majority of opens now happen.
- Do emojis in subject lines help open rate?
- Sometimes. The honest answer: emojis produce ±5-10% open-rate variance depending on audience and context. B2C audiences often respond well to one well-chosen emoji. B2B audiences often react against them — seen as unprofessional. More than two emojis almost always hurts — reads as marketing-template. Test per audience rather than applying a universal rule.
- Should subject lines ask questions?
- Occasionally, not as a default. Questions work as a hook when the question is genuinely interesting and the email answers it ("Why did Gmail clip your last send?"). Questions fail when they're rhetorical or formulaic ("Ready for the weekend?"). The pattern that consistently underperforms: generic question subject lines on promotional sends. The pattern that works: specific, answer-promising questions on curiosity-driven content.
- How do I A/B test subject lines?
- Send each variant to a random 10-20% of the audience, measure open rate on the primary metric, declare the winner, then send the winner to the remaining 60-80%. Most ESPs automate this as a "winner send" feature. Caveats: open rate is contaminated by Apple MPP, so results on audiences with significant Apple share are noisy. Where possible, use click-through rate or downstream conversion as the winner metric rather than opens.
This guide is backed by an Orbit skill
Related guides
Browse allPreheader text: the second subject line most programs ignore
The preheader is the snippet shown next to the subject line in the inbox preview. Treat it like a second subject line and you double your hook. Treat it like an afterthought and it says 'View this email in your browser'. Here's how to write preheaders that actually earn the open.
Personalisation that doesn't feel creepy
There's a line between personalisation that earns trust and personalisation that breaks it. It's not where most people think it is — it's about how you signal what you know, not what you know. Here's the line, how programs cross it without noticing, and the patterns that keep you on the right side.
Emojis in subject lines: when they help, when they hurt
One well-placed emoji lifts open rate a few percent. Three reads as spam and drops it. The honest version of the emoji question is smaller and more specific than the debate suggests — here's the pattern that actually survives testing.
Push notification copy that actually gets tapped
Push is the highest-interrupt channel in the stack. A bad push burns goodwill in under a second; a good one feels like a useful nudge from a friend. This is the copy discipline — specific words, specific structures, specific anti-patterns that reliably get a user to turn your notifications off for good.
Brand voice in lifecycle: how to sound like you, not the generic SaaS CRM voice
Lifecycle emails — the automated sequences that go out on signup, after a purchase, when a cart is abandoned — drift toward a polished, generic SaaS voice because it's the default in every template library. Here's how to actually write in your brand's voice across an entire program.
The email copywriting pyramid: write for the 5-second reader first
Most recipients give an email five seconds before they engage or delete. The email has to land its point at that depth and still reward a longer read. The inverted pyramid — conclusion first, detail after — is how.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 63 lifecycle methodologies, 91 MCP tools, native Braze integration. Free for everyone.