Your message is going to be opened. Somebody who knows your name opens what you send, and the subject line doesn’t have to win that. What the line decides is when, and what the reader has already worked out by the time they get there. Nearly everything written about subject lines was measured on marketing campaigns. Ten thousand strangers, an open counted by an invisible image, and a line of text whose job is to overcome the fact that nobody asked for the message. You’re writing to one person who knows your name, and the arithmetic is different enough to change the advice.
That’s a smaller promise than triple your open rate, and it’s the one that pays. A subject line that names the thing, the ask and the size gets opened this morning and answered the same day. “Quick question” gets opened too, eventually, out of politeness, by somebody who decided long ago that it could wait.
- Three things are visible before anybody decides anything, and the subject is one of them. The other two are who it’s from and the first line of the body. Most people spend that third one on “I hope this finds you well.”
- Front-load it. Every mail app shows the beginning of a subject line, and every one cuts the end somewhere different, so the load goes on the left.
- Say what kind of message it is. “Needs a yes by Friday” and “no reply needed” are the two most useful phrases available here, and almost nobody uses either.
- Open rates stopped being a measurable quantity in 2021. Worth knowing before you trust a chart about subject lines, and before you build a habit on one.
This piece is about the line. The messages underneath it have their own shapes. There’s the follow-up email that gets answered and the polite reminder email. There’s how to say no in an email, how to apologize by email, and the short reply that still sounds warm.
What the reader sees before they decide
Open any mail app and look at the list instead of the message. Three pieces of text sit on every row, and the subject is the middle one.
Who it is from. On a phone this is the largest, boldest, leftmost thing on the row. For professional mail it settles most of the question on its own. Chad S. White put it plainly on the Litmus blog in October 2016: “Your sender name, not your subject line, has the biggest impact on whether your emails are opened.” That’s an argument rather than a measurement, and it survives the obvious test. Mail arrives from your accountant, you read the name, and you open it. The subject line barely registers.
The subject. One line, cut to whatever the app has room for. How many characters that is depends on the app and the device. It also depends on the orientation, the font size the reader chose, and whether they’re in a split view. That’s the useful part: you have a direction to load, and you can stop hunting for a character count.
The first line of the body. Most mail apps show a preview of it in gray, next to or under the subject. It’s about as long as the subject line, and almost everybody wastes it. There’s a section on it below, because it’s the cheapest improvement on this whole page.
Here’s the part that changes the job. For one-to-one professional email, the open is close to certain. A client, a colleague, a supplier, somebody you met last week: they’ll open it. What those three fields decide is position in a queue. Your message gets dealt with in the ten minutes they have now, or it moves to the pile they’ll reach after the thing that looked urgent. Put that way, the subject line is a label, and labels are much easier to write than hooks.
Why nobody has a real open rate anymore
This matters before you take any advice with a percentage attached.
An open is an inference rather than an event a mail server reports. The sender embeds an invisible image, and the image being requested counts as evidence that a human looked at the message. That inference broke on purpose. Apple announced Mail Privacy Protection on June 7, 2021, describing it as a feature that “stops senders from using invisible pixels to collect information about the user” and “helps users prevent senders from knowing when they open an email.” Apple’s own documentation is specific about the mechanism. Protect Mail Activity, it says, “downloads remote content in the background by default”, and it does so whether or not the reader engages with the email.
So on every Apple Mail account with the feature on, the pixel fires whether or not anybody read anything. Two consequences follow, and both are practical.
Send through a marketing tool and your open rate since late 2021 is a blend of people and machines. The blend shifts with the mix of mail apps on your list. It’s still useful for spotting a disaster. As a scale for weighing one subject line against another it’s too coarse, and an A/B test scored on opens now measures something other than what you meant. Score on replies, clicks or bookings instead.
Write one-to-one and you never had an open rate anyway. You already have a better one: whether you had to send a second message. That’s a slower signal and a much more honest one. It’s also why the research quoted further down measures responses rather than opens.
The three questions a subject line has to answer
A working subject line answers three things before the reader decides to give you anything. Most answer the first one and stop.
What is this about? In their nouns. You say the engagement, they say the audit. You say the creative, they say the brochure. You say the deliverable, they say the report they promised their board. A subject line in your own vocabulary reads like internal mail from somebody else’s company, and the reader has to translate it before they can file it.
Attach the identifier while you’re there. A number, a date, a name. “Invoice 3318” is findable forever; “invoice” isn’t. “The Halstead kitchen quote” beats “your quote” for the same reason, and both beat “Following up.”
What does it want from me? Almost nobody answers this one, and it’s the question that moves your message up the queue. There are four answers and they’re short:
- a decision: “needs a yes or no”
- an action: “needs your signature”, “two minutes”
- information: “for your records”, “before Thursday’s call”
- nothing at all: “no reply needed”
Add three or four words of that to the end of a subject you already wrote, and you’ve done most of the work available in this piece. “Halstead kitchen quote: needs a yes by Friday.” “October payroll summary: for your records, no reply needed.” The reader now knows the size of the job before opening anything, a thirty-second one or a thirty-minute one. Thirty-second jobs get done on the spot.
How big is it? The first two imply this, and it’s worth being honest about on its own. The reader is protecting their morning, and that’s all they’re doing. A subject line that undersells the size buys one open, then teaches the reader to doubt the next one. “Quick question” on a message that asks somebody to reconcile two spreadsheets is the standard example, and everybody has been on the receiving end of it.
One test covers all three. Could somebody holding fifty messages sort yours correctly from the list alone? If yes, you’re done. Cleverness after that point costs you the second read.
Front-load, then stop counting characters
Every app cuts the line somewhere different, so the reliable move is to put the load at the start and let the tail be the part that goes.
Following up on our conversation last week about the Q4 marketing retainer proposal
Q4 retainer proposal: one question, then I can send it
Same content. Chop both after six words, and the second one still works. Build from the front: the noun that identifies the thread, then the identifier, then the ask. Leave your own name and your company’s name out of it. The sender field already said them, and repeating them spends your best characters on the one fact the reader already has.
On length itself, two independent sources point the same way, and it’s away from where people expect. Backlinko, working with the outreach platform Pitchbox, looked at 12 million outreach emails in a study by Brian Dean last updated April 2019. It found that “subject lines between 36-50 characters get the best response rate”, with “long subject lines outperformed short subject lines by 32.7%”. Mailchimp, working from “the open rate performance of hundreds of millions of emails in Mailchimp”, recommends “no more than 9 words and 60 characters.”
Read both with their limits attached. Backlinko’s corpus is cold outreach to strangers, mostly link-building and PR pitches, which is close to the opposite of writing to a client. Mailchimp’s number comes from bulk campaigns on its own platform, scored on opens, which is the metric the last section cast doubt on. Both are evidence about somebody else’s Tuesday morning rather than a rule for yours.
The direction transfers, because both point the same way, and it’s the opposite of the folk advice. The punchy three-word subject line has nobody’s evidence behind it. Forty to sixty characters is roughly one clear phrase plus the ask, which is what the last section asked you to write anyway. Take that as your working range, and read it as permission to be specific rather than as a target to hit.
The personalization finding is worth separating out, because it means something different in one-to-one mail. Backlinko found that “personalized subject lines got nearly 1/3rd more replies than those without personalization”. In a campaign that’s a merge tag dropping in a first name. Writing to one person, their name in the subject line reads as faintly odd, because the message is addressed to them and they know it. What carries the same weight is a detail only the two of you share: their project name, the date you spoke, the number on their invoice. That’s what personalization stands in for, and you already have it.
The line under it that you are wasting
Look at your own inbox on a phone. Under most subject lines sits a gray fragment of the first line of the body, and on a great many professional emails that fragment reads “Hi Dana, I hope this finds you well. I’m writing to fo…”
You had a second subject line there and you spent it on the weather. The fix is free: make the first sentence of the body the one you’d want read.
Subject: Fieldwork dates, need one of two weeks confirmed
Preview: Either the week of the 14th or the week of the 21st works our end. Whichever you pick, I will…
Subject: Brochure proof v3 attached, approve or mark up by Thursday
Preview: Only page 6 changed since the last one. Everything else is as you approved it on the 3rd.
The reader knows what’s happening in both of those from the list alone, which is exactly the point. A message that can be triaged from the list gets triaged, and a message that has to be opened to be understood gets postponed. Where the whole thing genuinely fits, finish the job in the subject and let the body carry the courtesy. Some people mark that with “(EOM)” for end of message. It’s a good convention inside a team that knows it, and a mildly cryptic one with a client meeting it for the first time.
Two habits to drop here. A greeting-plus-pleasantry stack at the front pushes everything informative past the cut. An apology at the front does something worse: “Sorry to bother you again” as the preview of a payment reminder tells the reader, before they open anything, that the message is optional.
Thirty-one subject lines, written out
Grouped by what you’re actually sending. Each one carries the thing, and most carry the ask.
Writing to somebody for the first time. The sender name is a stranger here, so the subject carries all three jobs alone.
Referred by Ana Villaseñor: bookkeeping for a 12-person studio
Question about your March 4 talk on retention pricing
Quote for the Bellwood roof, as discussed on site Tuesday
Following your RFP: one clarification before we bid
A proposal or an estimate.
Wilcox rebrand: proposal attached, needs a yes or no by the 19th
Two options for the retainer, both under your $6k ceiling
Revised estimate after the scope change, down $1,400
Following up when nothing came back. Reply on the existing thread wherever you can, and you inherit the subject rather than writing one. These are for the times a thread genuinely has to restart. The message that goes underneath them is the follow-up email that gets answered.
Wilcox rebrand: holding the March slot until Thursday
Still need one thing on the Kessler file: the 2025 depreciation schedule
Closing out the Bellwood quote unless you say otherwise
Reminders and dates. The whole shape of these is in the polite reminder email, along with why announcing that a reminder is gentle makes it worse.
Signed W-4 due back the 20th, blank form attached again
Your policy renews the 31st; nothing needed unless you want changes
Three of eight timesheets still open for October
Quote 5512 expires the 30th, and so does the January install slot
Money.
Invoice 3318, $2,400, due Friday the 12th
Invoice 3318 is 30 days past due: approval or a problem?
Deposit received, thank you. Here is what happens next
Scheduling. If the outstanding thing is a time rather than a decision, the repair is scheduling without the email chain.
Thursday 9:30 or Friday 2:00 for the year-end review, either works
Moving Tuesday’s call to the 18th, same time
30 minutes before the 8th to walk through the numbers?
Saying no. The answer belongs in the subject. A refusal the reader has to hunt for gets read as a maybe, and that failure is taken apart in how to say no in an email.
Can’t take the November project, but here is who I would call
No on the sponsorship this year, yes to the spring one
When something has gone wrong. Say what happened in the subject. The instinct is to soften it there and let the body break the news, and that makes things worse every time: the reader opens expecting routine and gets ambushed. The repair itself is how to apologize by email.
The Kessler return went out with the wrong EIN, corrected version attached
We missed Friday’s delivery. New date, and what I am doing about it
Site was down 40 minutes this morning: cause and fix
Nothing needed from you. The most underused category in professional email, and the one that buys the most goodwill. It’s the one kind of message that takes work off somebody’s desk.
Filed this morning, confirmation attached, no reply needed
FYI only: the vendor moved their price list, no change to your quote
Weekly update, 4 lines, nothing needed unless something looks wrong
Threads that come back every month. Consistency is worth more than wit here. Pick a stem, keep it forever, and let the reader’s own search find the run of them.
Payroll, October: approve by the 28th
Hartley Group weekly update, week of Nov 3
Q3 estimates, Rivera Holdings: draft for review
Read down the list and the pattern repeats. The first three or four words identify the thread. Somewhere there’s a number or a date. In about half of them the reader learns what’s wanted before opening anything. Every one of them is plain.
The words that cost you the answer
Every phrase below was written by somebody trying to be brief, polite or urgent, and each one costs something.
“Quick question.” Two problems in three words. It’s a promise about size you have no way of keeping. And it tells the reader the message is small, which is the same as telling them it can wait. Ask the question instead: five words of the actual subject beat a label about it.
“Touching base”, “checking in”, “circling back”, “following up.” All four describe your own behavior. The reader wants the noun that reminds them what this is, and these four sit in its place. The same problem in body copy, and what to write instead, is in the follow-up email that gets answered.
“Update” on its own. An update on what, needing what? Two words that make the reader open the message to find out whether opening the message was worth it.
“URGENT”, “IMPORTANT”, “ACTION REQUIRED” in capitals. Urgency is a fact about a date, so give the date and let the reader draw the conclusion. Capitals read as volume rather than emphasis, and readers describe them afterwards as rude far more often than as urgent. Each use also spends credibility you’ll want later. Mark three things urgent a week, and the week the fourth one really is urgent, the word is spent.
A “Re:” or “Fwd:” on a message that is neither. People do this to borrow the familiarity of a reply. It works exactly once, it reads as a small con the moment it’s spotted, and in commercial email it stops being a matter of taste, which is the next section.
Emoji. Fine in a newsletter, where they’re a design element competing with other newsletters. In one-to-one professional mail they carry an intimacy most business relationships have yet to agree to, and they’re the first thing to render badly on somebody’s older desktop client.
Your own company name at the front. “Meridian Consulting: invoice attached” spends the leftmost characters, the ones certain to be shown, on the fact the sender field already gave away.
“[Your company] x [Their company].” The outreach cliché. It signals a template, and it leaves the contents a mystery.
No subject at all. It looks decisive from your side. It lands as a mistake, a mass mailing, or an implicit claim that the reader should already know. It also erases the message from every future search, including yours.
The whole message crammed in with no body. The short subject that ends the matter is a different thing, and it works. A subject line running to two sentences is unreadable in a list, and the parts that would have made sense of it are the parts that get truncated.
When to rename a thread, and when not to
Mail programs chain messages by hidden headers rather than by the words in the subject field. Press reply and the chain holds, whatever you type in the subject. Compose a fresh message and the chain breaks, however carefully you retype the same words. That mechanism, and the four ways a long thread comes apart, are covered where a signed document gets versioned across weeks, in keeping the SOW conversation on one thread.
The practical guidance from here is short. Edit a subject line on a reply when the thread has genuinely turned into a different conversation. Say so while you do it. Put “Different topic, splitting this off” on the first line, and send a fresh message rather than a reply. The new conversation then gets its own chain and its own searchable name.
Renaming for versions is the one to leave alone. “Proposal”, then “Proposal v2”, then “Proposal v2 final” makes three conversations out of one in some readers’ mail apps, and confusion in the rest. Version the document, and leave the subject as it is.
One more case. Take a thread that’s gone quiet, restart it as a new message, and you get a fresh subject line. Use it, because the old one went quiet.
The one subject line rule that is actually law
Everything above is judgment. This part is law, and it’s short.
Under the CAN-SPAM Act, at 15 U.S.C. § 7704(a)(2), it is unlawful to send a commercial email when the sender has “actual knowledge, or knowledge fairly implied on the basis of objective circumstances, that a subject heading of the message would be likely to mislead a recipient, acting reasonably under the circumstances, about a material fact regarding the contents or subject matter of the message.” The FTC’s own compliance guide states it in one line as requirement number two: “Don’t use deceptive subject lines. The subject line must accurately reflect the content of the message.”
Two things about the scope catch people out, and this is the one contrast in this piece worth the space, because getting it wrong costs money. The Act reaches well past mass mailing. The FTC guide is blunt that it “doesn’t apply just to bulk email”, that “it covers all commercial messages”, and that “there’s no exception for business-to-business email.” The subject line also decides how a message gets classified in the first place. Where a message mixes a promotion with an ordinary transactional note, the guide says that “if a recipient reasonably interpreting the subject line would likely conclude that the message contains an advertisement or promotion for a commercial product or service … the primary purpose of the message is commercial”. That pulls the whole message into the Act’s requirements for a physical postal address and a working opt-out.
On the guide’s own figure, penalties run to “up to $53,088” per separate email in violation (checked September 6, 2026; the FTC revises that number for inflation).
Most of the mail this piece is about sits outside all of this. Telling a client their return is filed is ordinary correspondence. The Act matters the moment you send a newsletter, a promotion or a cold sequence, and it’s why the fake “Re:” is worth more than a raised eyebrow. A subject heading engineered to make a stranger believe there’s an existing conversation is the exact behavior the section describes.
Where a better subject line will not help
Five situations where this is the wrong lever. Worth spotting them before you spend an afternoon rewriting.
They already open everything you send. For most established client relationships this is already true, and the open is won before you type. The subject line’s remaining job is sorting, which the ask does. If the message still sits there unanswered, the request is the thing to look at, and the repair is in the body.
You’re replying. A reply inherits its subject, and that’s usually right, because the reader recognizes the thread. This page is about the message you start. If you’re starting from an empty compose window with a drafting tool, getting a usable draft is a different job, covered in composing an email from scratch.
It’s going to spam. Filters weigh sender authentication, sending history and recipient behavior far more heavily than the words in your subject field. A subject line cannot fix a domain with no authentication records, and the folklore about trigger words sends people editing text while the problem sits in the headers. If mail from your domain is disappearing, that’s a deliverability question rather than a writing one.
The ask is too big. A two-hour task stays a two-hour task, whatever the label. If the thing you want takes real work, the subject line’s honest job is to say so. Then edit the request itself: make it smaller, split it, or ask for the decision rather than the deliverable.
It’s a bulk campaign. Then this is the wrong page, and here’s why rather than just that. Campaign subject lines are written for strangers, tested in pairs across thousands of sends, and scored on a metric the earlier section showed to be unreliable. Curiosity, novelty and a testing habit genuinely earn their keep there. In a message to somebody who knows you, all three go quiet. One thing carries in both directions: say what the message is about, and let the body deliver what the subject promised.
One more, and it sits outside subject lines altogether. If you’re on the third message about the same thing, the missing piece is a conversation rather than a better label. Two minutes on the phone settles it, where a fourth subject line goes round again.
What Point does with the subject field
Point is an email client that runs on the Gmail or Microsoft 365 mailbox you use now, and Point changes both halves of this: the lines you write, and the lines you have to read.
On the writing side, a subject line comes back with the draft. Ask for the message in one sentence. What arrives is phrased the way you phrase things, subject included, drawn from how you’ve named this kind of thread before rather than from a template. The last edit is still yours to make, and it’s usually one word.
What happens to that draft next is a setting you make. The autonomy dial is set separately for each type of action, and it has three positions. Point can suggest only. Point can prepare the reply and hold it for you. Or Point can handle it outright. Every action type arrives on the middle one. The three positions are on the autonomy dial.
On the reading side the change is larger, because a subject line is a compression somebody else wrote, and it’s often wrong. Point leads your feed with what actually needs you today rather than with what arrived last, so the top of the list is decided by the work rather than by the labeling. Every conversation carries a plain summary, so what you see in the list is what the thread is about rather than what somebody typed in the subject field eleven replies ago. Finding it later works the same way. Search reads what you meant rather than matching the words you typed, so the thread somebody called “Quick question” in March is still findable in November by what it was actually about.
Everything Point did is written down in order, and undo reads back from that record. One repair sits outside it: a message already delivered to somebody else’s server cannot be recalled. The fuller account of what a mailbox gains is on the benefits page.
Common questions
What makes an email subject line get opened?
For mail from somebody the reader knows, the open is nearly certain, and the subject line is deciding position in a queue. Three things move it up: the noun the reader would use for the thing, an identifier like a number or a date, and three or four words saying what’s wanted from them. “Halstead kitchen quote: needs a yes by Friday” gets handled this morning. “Quick question” gets handled Thursday. Writing to a stranger, the sender name does most of the work, and the subject line has to be specific and honest enough to be worth a stranger’s ten seconds.
How long should an email subject line be?
Roughly one clear phrase plus the ask, which lands somewhere between 40 and 60 characters. Two independent sources point there. An analysis of 12 million outreach emails found the best response rate on subject lines between 36 and 50 characters, and Mailchimp recommends no more than 9 words and 60 characters. Both come from bulk sending rather than one-to-one mail, so take the direction and leave the number. The direction is worth having, because it contradicts the popular advice: the punchy three-word subject line has nobody’s data behind it. Order matters more than length anyway, because every mail app shows the beginning of the line and each one cuts the end somewhere different.
Does personalizing a subject line still work?
In campaigns, yes, and measurably: the same 12-million-email analysis found personalized subject lines got nearly a third more replies. In a message to one person, their first name in the subject adds nothing, because the message is addressed to them and they know it. What carries the same weight is a detail only the two of you share: their project name, the date you spoke, the invoice number. That’s what personalization was standing in for all along, and in one-to-one mail you already have it.
Should I write “urgent” in a subject line?
Write the date instead. The word earns its place only when a specific person faces a specific consequence on a specific date, and by then the date says it better. “Needs your sign-off before Thursday’s print run” carries more urgency than “URGENT”, and it’s impossible to argue with. Every use of the word spends credibility across everything you send afterwards, and capitals read to most people as volume rather than emphasis.
What subject line should I use for a follow-up email?
Ideally you inherit one, because replying on the existing thread keeps your original quoted underneath, where it does the work of the recap. Where the thread genuinely has to restart, name it after the decision that’s outstanding and the date attached to it: “Wilcox rebrand: holding the March slot until Thursday.” Naming it after the act of following up is the habit to drop. The message that goes underneath is in the follow-up email that gets answered.
Is it ever okay to send an email with no subject line?
Between two people trading twenty messages a day, nobody notices. Anywhere else it costs more than it looks. It reads as a mistake or a mass mailing, it leaves the reader with nothing to sort by, and it removes the message from every future search including your own. If the message is genuinely one line, put that line in the subject and let the field do the work.
Should I change the subject line partway through a thread?
Rarely, and versions are the case to leave alone. “Proposal”, “Proposal v2”, “Proposal v2 final” splits one conversation into three in some mail apps and confuses the rest, so version the document instead. Where the thread has genuinely become a different conversation, start a fresh message with its own subject, and say in the first line that you’re splitting it off. Remember the mechanism: press reply and the chain holds whatever you type in the subject field, compose fresh and the chain breaks however exactly you retype it.
Do emoji in subject lines help?
In a newsletter competing with forty other newsletters in a promotions tab, sometimes. In professional one-to-one mail they carry a familiarity most working relationships have yet to agree to, they render unpredictably on older desktop clients, and on anything touching money or a mistake they read as breezy about somebody else’s problem. If a subject line only works with a smiley on the end, rewrite the subject line.
Can I still trust email open rates?
As a rough signal, yes. As a precise measure, they stopped working in 2021. An open is inferred from an invisible tracking image being loaded, and Apple’s Mail Privacy Protection downloads that content in the background whether or not anybody looked at the message. So open rates still spot something badly wrong, and they’re far too coarse for choosing between two subject lines. Score on replies, clicks or bookings instead, all of which take an actual human.
Is a deceptive subject line against the law?
For commercial email in the US, yes. CAN-SPAM makes it unlawful to send a commercial message with a subject heading likely to mislead a reasonable recipient about a material fact regarding its contents, and the FTC’s guide states the requirement as “the subject line must accurately reflect the content of the message.” It reaches well past bulk sending, and it covers business-to-business email too. A note to a client about their own file is ordinary correspondence. A cold sequence with a fake “Re:” on the front is exactly the behavior the section was written for.
The short version
The subject line is a label. For mail from somebody the reader knows, it decides where the message lands in the queue. Three things move it up: the noun they’d use for the thing, an identifier like a number or a date, and a few words saying what’s wanted from them. Add “needs a yes by Friday” or “no reply needed” to a subject line you’ve already written, and you’ve captured most of the available gain.
Then put the load at the left, because every mail app shows the start of the line and each one cuts the end somewhere different. Use the gray preview underneath. It’s a second subject line, and you’re probably spending it on “I hope this finds you well.” Cut “quick question”, cut “circling back”, cut the capitals, and cut your own company name from the front, since the sender field already said it. Where the message is genuinely commercial, the subject has to be honest as a matter of law rather than of taste.
What you send changes the emphasis. An accounting practice is mostly labeling documents and dates. The identifier is the whole battle there, and consistency across a monthly run beats wit every time. A design studio is chasing approvals, so the ask belongs in the subject, and the ask is nearly always a page number or a yes. A consultancy is naming proposals and stakeholder threads that six people will search through in a year, so the name has to survive being read by somebody who missed the meeting. And a coaching practice is often writing something personal, where the subject line’s job is to be plain rather than efficient. The other trades this was built for sit somewhere among the four.