What a professional email subject line has to do
A professional email subject line is the one line of your message that every recipient reads. The professional email subject line examples further down all do the same job: they say what the email is about, and what the reader has to do about it, before anyone decides to open it.
That is a narrow job, and most weak subject lines fail it in the same way: they name a topic without naming an action. "Budget" tells the reader nothing. "Q4 budget: two numbers I need from you by Friday" tells them the topic, the ask and the date.
| The subject line carries | What the reader learns | Example fragment |
|---|---|---|
| Topic | Which project, account or thread this belongs to | Q4 budget |
| Action | Whether they read, reply, decide or do nothing | two numbers I need |
| Timing | How soon it matters | by Friday |
| Identity | Who is writing, when the name is not obvious | from the Dublin team |
Purdue OWL's email etiquette guidance puts the same point plainly: include a meaningful subject line, because it clarifies what your message is about and helps the recipient prioritize reading your email.
The rest of this page gives the rules, then more than fifty subject lines written for this page, grouped by the situation you are actually in, and finally the legal line you cannot cross in commercial email.
Seven rules for writing a subject line
These rules hold for a cold email, a status report and a resignation notice alike. The tone changes; the structure does not.
- Front-load the topic. Put the specific noun first, because the first few words are all a busy reader and a narrow phone preview will show.
- Name one action, not three. If the email contains an approval, a question and an invitation, the subject line picks the one that decides whether the reader opens it.
- Be specific enough to search. "Contract" is unfindable in six months. "Contract for {{project}}, signed copy" is findable, by you and by them.
- Say the date when a date exists. A deadline in the subject line saves the reader from opening the email to find out whether it is urgent.
- Write it last. Draft the message, then summarize what you actually asked for. Subject lines written first tend to describe an email you did not end up sending.
- Match the body exactly. A subject line that promises more than the message delivers is a deliverability problem and, in commercial email, a legal one.
- Read it as the recipient. Would you open this if it arrived from a name you did not recognize, on a phone, in a list of forty other messages?
Email tools publish open rates by subject line style, measured on their own users' campaigns. No open rate figures are quoted on this page, because they come from other people's lists and other people's readers. Compare your own subject lines against each other instead.
Email subject line length and what a phone shows
Length is the first practical constraint. Desktop mail clients show more of the line than phones do, and both cut it off at a width that depends on the device, the font size and the window, not on a fixed number you can look up.
Mailchimp's own guidance for its senders is to use no more than nine words and sixty characters in a subject line, and it notes that shorter is often better for recipients reading on mobile devices. That is a sender recommendation from one platform, and it is a sensible ceiling for work email too.
The rule that survives every device is simpler: make the first three or four words carry the message. If the line gets cut in the middle, the reader should still know the topic and roughly what you want.
- Test it on your own phone. Send the draft to yourself, look at the inbox list, and see where the line stops. That takes a minute and beats any character count.
- Put the identifier first. Client name, invoice number or project code before the verb, so a truncated line is still sortable.
- Drop the courtesy opener. "Following up regarding" and "I wanted to reach out about" burn the visible half of the line.
- Do not rely on the tail. A deadline at the end of a long line is the part most likely to disappear.
Four formulas that cover most work email
Almost every professional subject line is one of four shapes. Pick the shape that matches what you need, then fill it with the specifics of your message.
Pattern: {{topic}}: {{what you need}} by {{date}}. Example: "Vendor contract: your signature by Thursday." It works because it sorts, searches and reads in one glance.
Pattern: a short, answerable question. Example: "Are we still presenting on the 14th?" A question invites a one-line answer, which is often all you need.
Pattern: {{project}} update: {{the one change}}. Example: "Migration update: cutover moved to Sunday." The reader learns the news without opening anything.
Pattern: {{the thing you have in common}}, {{your reason}}. Example: "Met at the Austin meetup, the report I promised." The context earns the open.
The fourth shape is where cold outreach lives. Without a shared reference, the subject line has to be specific enough to be worth a stranger's attention, which is a harder problem than the other three.
Professional email subject line examples by situation
The professional email subject line examples below were written for this page. Placeholders in double braces mark what you replace. Each one is labeled with the situation it fits, because the same line that works after a conference reads badly in a first contact.
Use them as starting shapes, not as copy and paste text. A subject line that names your recipient's actual project will always beat a generic line that reads well.
Cold email subject lines for a first contact
| # | Subject line | Use it when |
|---|---|---|
| 1 | Question about {{company}}'s {{process}} | You have a real, specific question, not a pitch |
| 2 | {{firstName}}, idea for the {{initiative}} rollout | You researched something the company announced |
| 3 | {{mutualContact}} suggested I write | A real person referred you and knows you are writing |
| 4 | Your post on {{topic}}, one follow-on question | You actually read what the prospect published |
| 5 | {{company}} + {{yourCompany}}: worth 15 minutes? | Both companies are known to the reader |
| 6 | Notes from {{event}}, plus the number you asked for | You met at an event and promised something |
| 7 | How {{peerRole}} teams handle {{problem}} | The reader holds that role and that problem |
| 8 | Wrong person? Who owns {{topic}} at {{company}}? | You are not sure you found the right contact |
Follow up email subject lines after no response
| # | Subject line | Use it when |
|---|---|---|
| 9 | Re: {{original subject}} | You are genuinely replying inside your own thread |
| 10 | Still useful, or should I close this out? | The conversation stalled and you want a clean answer |
| 11 | {{project}}: one decision still open | A specific item is blocking the work |
| 12 | Checking timing on {{topic}}, not chasing | The reader said "later" and you are honoring it |
| 13 | Last note from me on {{topic}} | This is the final message in a sequence, and you mean it |
| 14 | Short version of my {{month}} email | The first email was long and went unread |
Notice that none of these say "just following up" or "touching base". Both phrases describe your calendar, not the reader's problem, and they make the follow-up look automated even when a person wrote it.
Introduction and networking subject lines
| # | Subject line | Use it when |
|---|---|---|
| 15 | Introduction: {{yourName}}, new {{role}} on {{team}} | You joined and are writing to people you will work with |
| 16 | Intro: {{personA}} and {{personB}} | You are connecting two people who agreed to it |
| 17 | Following up after {{event}}, {{yourName}} | You met briefly and they may not recall the name |
| 18 | Taking over {{account}} from {{colleague}} | A handover the client needs to know about |
| 19 | {{topic}}: would value 20 minutes of your experience | An informational conversation, with nothing to sell |
A first message needs the subject line and the opening sentence to work together. Our guide on how to introduce yourself in an email covers the sentence that follows these lines.
Meeting request email subject lines
| # | Subject line | Use it when |
|---|---|---|
| 20 | Meeting request: {{topic}}, 30 minutes | A plain request where the topic does the work |
| 21 | {{topic}}: Tuesday 10am or Thursday 2pm? | You can offer two concrete times |
| 22 | Agenda for {{date}} {{meetingName}} | Sending the agenda before a confirmed meeting |
| 23 | Moving {{meeting}} to {{newDate}}, does that work? | You need to reschedule and want a fast answer |
| 24 | Can we cut {{meeting}} to 20 minutes? | The agenda shrank and you are giving time back |
Project, approval and deadline subject lines
| # | Subject line | Use it when |
|---|---|---|
| 25 | Approval needed: {{document}} by {{date}} | One named person has to approve one named thing |
| 26 | {{project}} status, week of {{date}} | A recurring update that people should be able to sort |
| 27 | Deadline moved: {{deliverable}} now due {{date}} | The date changed and everyone must see it |
| 28 | {{project}}: two numbers I need from you | A small, countable ask from a specific person |
| 29 | Decision needed by {{date}}: {{optionA}} or {{optionB}} | The reader has to choose between two options |
| 30 | No action needed: {{project}} closed out | Information only, and you want to save them the open |
"No action needed" earns goodwill, because it tells a reader they can archive the message without reading it. Use it honestly, and only when it is true.
Job application email subject lines
| # | Subject line | Use it when |
|---|---|---|
| 31 | Application: {{jobTitle}} ({{reqNumber}}), {{yourName}} | The posting gives a reference number; always use it |
| 32 | {{jobTitle}} application, referred by {{employeeName}} | An employee actually referred you |
| 33 | Thank you, {{jobTitle}} interview on {{date}} | Sent within a day of the interview |
| 34 | Following up on my {{jobTitle}} application | The posted response window has passed |
| 35 | Requested materials: {{portfolio}} for {{jobTitle}} | The recruiter asked you to send something |
Keep the tone plain. A line that sounds like a pitch reads as salesy to a recruiter, and the same instinct hurts in any email to a stranger.
A hiring inbox is sorted, filtered and forwarded. The role title and any requisition number matter more than a clever line, because they decide whether your email reaches the right reviewer at all.
Resignation and notice subject lines
| # | Subject line | Use it when |
|---|---|---|
| 36 | Resignation: {{yourName}}, last day {{date}} | The formal notice to your manager and HR |
| 37 | Notice of resignation, effective {{date}} | A more formal workplace or a written policy |
| 38 | Handover plan for {{role}} before {{date}} | The follow-up email after notice is accepted |
| 39 | Thank you and goodbye from {{yourName}} | The note to colleagues on your last week |
A resignation subject line should be boring on purpose. It goes into a personnel file, so state the fact and the date, keep any feeling for the body of the message, and send it to your manager before anyone else hears it.
Problem, apology and escalation subject lines
| # | Subject line | Use it when |
|---|---|---|
| 40 | {{system}} outage: status and next update at {{time}} | People are waiting and need the next checkpoint |
| 41 | Error in {{report}} sent {{date}}, corrected version | You are fixing something you sent |
| 42 | Apology and fix for {{issue}} | A client was affected and deserves both |
| 43 | Escalating {{ticket}}: blocked since {{date}} | Normal channels have not moved |
| 44 | Invoice {{number}} overdue, payment options inside | A factual collections note, not a threat |
Thank you, confirmation and closing subject lines
| # | Subject line | Use it when |
|---|---|---|
| 45 | Confirmed: {{meeting}} on {{date}} at {{time}} | Locking a time in writing |
| 46 | Received, thank you: {{document}} | Someone sent something and deserves a receipt |
| 47 | Thank you for the introduction to {{person}} | Someone spent their own credibility on you |
| 48 | Summary and next steps from {{date}} call | Immediately after a call, while it is fresh |
| 49 | {{project}} delivered: files, access and support contact | The handover at the end of a piece of work |
Reply, forward and internal thread subject lines
| # | Subject line | Use it when |
|---|---|---|
| 50 | Re: {{subject}} (adding {{colleague}}) | You are bringing a new person into an existing thread |
| 51 | Fwd: {{subject}}, one thing needs your call | Forwarding, with the reason stated in the line |
| 52 | New thread: {{newTopic}} (was: {{oldSubject}}) | The conversation drifted and deserves its own thread |
| 53 | FYI only: {{topic}} | Nothing is expected of the reader |
| 54 | Closing the loop on {{topic}} | An old thread can finally be ended |
Splitting a drifting thread with a new subject line is one of the cheapest favors you can do a busy team. Everything about {{newTopic}} becomes searchable under its own name instead of hiding under an old one.
Cold email subject lines that do not read like marketing
In cold outreach the subject line is competing with every other stranger in the inbox. The instinct is to make it clever. The better move is to make it look like an ordinary work email about a real thing, because that is what it should be.
- Use the specific noun. Name the product, the team, the city or the announcement. A prospect can tell in a second whether you looked anything up.
- Keep it short and lowercase where it fits. A colleague writing about a project does not write in title case with an exclamation mark.
- Do not fake familiarity. "Re:" on a first email, or "as discussed" when nothing was discussed, buys one open and costs the relationship.
- Skip the merge-tag first name alone. A name in the subject line is not personalization when every other sender does the same thing.
- Make the promise small. "Worth 15 minutes?" is a promise you can keep. "Double your pipeline" is not, and the body will not support it.
Research that makes a cold subject line specific
A specific cold email subject line is a research output, not a writing trick. Five minutes on a prospect gives you a noun no other sender has, which is what separates outreach that gets a response from outreach that gets deleted.
- Trigger events. A funding round, a new office, a product launch or a role change gives you a reason to write that the prospect already believes.
- The prospect's own words. A phrase from their careers page, their podcast or their post is stronger personalization than a first name merge tag.
- Technology and tools. What a B2B company runs tells you which problems are plausible, and which ones would not help them at all.
- Peer group. Naming the kind of team rather than the company works when you write to many prospects with one real pattern in common.
- The account, not just the person. Several people at one company read different subject lines, so vary the angle rather than sending the same line to all of them.
Avoid the temptation to turn that research into a long line. Use one finding, put it first, and let the body carry the rest. The subject line proves you looked; the email proves you understood.
The subject line also has to survive the rest of the sending setup. Volume, domain reputation and list quality decide whether a well-written line is ever seen, which is why email warm up and clean data matter before wording does.
For the message underneath the line, our cold email hub covers structure, personalization and the first sentence. The wider sales outreach hub covers the channels around it.
Touch 1: Question about {{company}} and {{process}} Touch 2, inside that thread: Re: Question about {{company}} and {{process}} Touch 3, new thread: How {{peerRole}} teams handle {{problem}} Touch 4, the close: Still useful, or should I close this out?
Touch 2 carries "Re:" although touch 1 was never answered and never sent as a thread. That is the move Google's sender guidelines name directly. Reply inside your own sent thread, or write a new line.
Follow up email subject lines and the thread decision
Every follow-up starts with one choice: reply inside the existing thread, or start a new one. Both are defensible, and the wrong reason is wanting to look like the reader already answered.
| Situation | Reply in thread | New subject line |
|---|---|---|
| Second touch, days later | Yes, the context is the point | Not yet |
| Third or fourth touch | The thread is getting long | Yes, with a new angle |
| A month or more has passed | The reader will not remember it | Yes, and re-establish who you are |
| Something genuinely changed | Only if it continues the old point | Yes, lead with the change |
| A different person at the same company | No, they were never in it | Yes, always |
Google's email sender guidelines are explicit on the one abuse here: do not send messages with subject lines starting with "Re:" or "Fwd:" unless the messages are actual replies or forwards. That applies to sales sequences as much as to newsletters.
Reminders, proposals and interview follow-ups
Different follow-ups need different promises. A reminder should state the deadline, a proposal follow-up should name the value in question, and an interview follow-up should help the recipient place you among a week of candidates.
| # | Subject line | Use it when |
|---|---|---|
| 55 | Reminder: {{deliverable}} due {{date}} | A real deadline is approaching and the recipient owns it |
| 56 | {{proposal}}: questions before you decide? | A proposal has been read but not answered |
| 57 | Following up on our {{date}} conversation | A real conversation happened and you both remember it |
| 58 | {{jobTitle}} interview: the example I mentioned | You promised something during the interview |
| 59 | Next steps on {{project}}, two options | The work can proceed in more than one direction |
When the content of the follow-up matters more than the line, our sales follow-up email templates give the full message, and sales cadence covers how many touches belong in a sequence.
What makes a subject line deceptive under CAN-SPAM
If your email advertises or promotes a product or service, United States law regulates the subject line directly. The Federal Trade Commission's compliance guide states the rule in one sentence: do not use deceptive subject lines, because the subject line must accurately reflect the content of the message.
The guide also notes that CAN-SPAM makes no exception for business-to-business email, and that each separate email in violation is subject to penalties of up to $53,088. A cold sales email is covered by the same rule as a newsletter.
The FTC's own worked example is about a subject line. A message headed "Your Account Statement" that opens with discount offers and puts the shipping update at the end is treated as a commercial message, because a recipient reasonably interpreting the subject line and the opening would conclude it is an advertisement.
| Subject line move | Why it is a problem | Source of the rule |
|---|---|---|
| Promising something the body does not contain | The subject line must accurately reflect the content | FTC CAN-SPAM compliance guide |
| Dressing an ad as an account or invoice notice | Primary purpose is judged partly by the subject line | FTC CAN-SPAM compliance guide |
| Faking a "From" name or reply address | Header information must identify who sent the message | FTC CAN-SPAM compliance guide |
| "Re:" or "Fwd:" on a message that is neither | Subject and headers must not be misleading | Google email sender guidelines |
| Emoji used to imitate graphics or badges | Not allowed when the intent is to deceive or influence | Google email sender guidelines |
The rest of the commercial email checklist sits below the subject line: the FTC guide requires a clear disclosure that the message is an advertisement, a valid physical postal address, and a clear explanation of how to opt out.
Opt-outs are not optional or slow. The guide says the opt-out mechanism must work for at least 30 days after you send, and that you must honor a request within 10 business days. Google additionally requires one-click unsubscribe from senders of more than 5,000 messages a day.
This section summarizes the FTC's published compliance guide and Google's published sender guidelines, both linked in the sources. Rules outside the United States, including consent rules for marketing email, are stricter in places. Check your own obligations before sending.
Words, punctuation and formatting that work against you
Beyond the law, there is the question of how a subject line reads to a filter and to a human who has seen ten thousand marketing emails. Both react to the same signals.
- All capitals. Writing the line in capitals reads as shouting and marks the message as a blast rather than a note from a person.
- Stacked punctuation. Mailchimp's sender guidance recommends no more than three punctuation marks in a subject line; multiple exclamation marks are the usual offender.
- Emoji as decoration. Mailchimp suggests at most one emoji, used to supplement words rather than replace them. In most professional email the right number is zero.
- Manufactured urgency. "Final notice" and "act now" on a message with no real deadline train readers to ignore your real deadlines.
- Money and giveaway words. Free, guaranteed and cash-related wording is heavily used by spam, so it attracts scrutiny that a specific subject line does not.
- The whole message in the line. A subject line that runs to a full sentence with a period usually means the email had no single point.
None of this is a magic word list. Filters weigh sender reputation, engagement and content together, which is why the same phrase can pass from one domain and fail from another. The reliable defense is being a sender people open on purpose.
Preview text is the second half of the line
Most inboxes show a snippet of the message next to or under the subject line. If you do not set it, the client pulls the first text it finds, which is often a greeting, an unsubscribe note or a "view in browser" link.
Treat the two as one unit. The subject line names the topic and the action; the preview text adds the detail that did not fit. "Q4 budget: two numbers by Friday" plus "Headcount and contractor spend, nothing else" is a complete brief before the email is even opened.
In everyday work email you cannot set preview text, so the first line of the body does that job. Starting with "Hi {{firstName}}, hope you are well" spends it on nothing. Our guide to email greetings covers that opening, and how to end an email covers the closing line.
Formal, neutral and casual subject lines
Tone in a subject line is carried by capitalization, length and how direct the ask is. Pick the level that matches the reader, then keep it consistent with the body and the sign-off.
| Register | Looks like | Example | Fits |
|---|---|---|---|
| Formal | Full words, title case, no contractions | Notice of Resignation, Effective {{date}} | HR, legal, government, first contact with a senior stranger |
| Professional neutral | Sentence case, topic and action | Vendor contract: signature needed by Thursday | Most business email, clients, cross-team work |
| Direct internal | Short, lowercase after the first word | Budget numbers by Friday? | Colleagues you write to weekly |
| Warm | Names a person or a shared moment | Great talking at {{event}}, {{firstName}} | Networking, thanks, follow-ups after meeting |
The common mistake is mixing registers: a formal subject line over a breezy message, or a casual line on an email that will be forwarded to a board. When in doubt, write one level more formal than you feel, and let the reader set the pace.
Weak subject lines, rewritten
These rewrites were written for this page. The pattern in every row is the same: replace a category word with the specific thing, and add the action or the date.
| Weak | Why it fails | Rewritten |
|---|---|---|
| Quick question | Says nothing, and is rarely quick | Question about the {{project}} invoice dates |
| Touching base | Describes your calendar, not their problem | {{project}}: one decision still open |
| Update | Unsortable, unsearchable, unopenable | {{project}} status, week of {{date}} |
| Important!!! | Urgency without information | {{system}} outage: next update at {{time}} |
| Hi | No topic at all, reads as a phishing attempt | Introduction: {{yourName}}, new {{role}} on {{team}} |
| Don't miss this exclusive offer | Marketing language on a one-to-one email | {{offer}} for {{company}}, ends {{date}} |
| Following up again | Counts your attempts, not their needs | Still useful, or should I close this out? |
| Meeting | Which meeting, and what about it? | Agenda for {{date}} {{meetingName}} |
How to write an email subject line, step by step
Write the email first
Finish the message, then read your own last paragraph. Whatever you asked for there is what the subject line has to announce.
Name the one action
Decide what the reader has to do: reply, decide, approve, attend, or nothing. If there is more than one, either split the email or pick the one that gets it opened.
Add the specific noun
Replace category words with the real project, client, invoice or document name, so the line is searchable in six months and sortable today.
Put the date in if one exists
A deadline in the subject line saves the reader from opening the message to find out whether it is urgent, and saves you a follow-up.
Cut it to the front half
Move the most important words to the start and delete the opener. Assume everything after the first few words may be cut off on a phone.
Check it against the body
Read the subject line, then the message. If the line promises anything the email does not deliver, change the line, not the email.
Send yourself a test
For anything going to a list or a customer, send it to your own phone and desktop, look at where the line stops, and fix it before it goes out.
How to judge a subject line without open rates
You will not have reliable open rate data for a one-to-one email, and open tracking on marketing email has become unreliable anyway. Judge the line on its own properties instead, before you send it.
For campaign email, compare two of your own subject lines on the same segment, on the same day, and look at replies and clicks rather than opens. Our guide to email marketing campaigns covers the measurement side.
Common email subject line mistakes
- Writing the subject line before the email, so it describes a message you did not send.
- Using a category word like "update" or "question" where a project name belongs.
- Promising a result in the line that the body never supports.
- Adding "Re:" or "Fwd:" to a message that is neither, which both Google and the FTC treat as misleading.
- Putting the deadline at the end, where the phone cuts it off.
- Sending three asks under one line, so two of them get lost.
- Keeping a thread alive under a subject line that stopped describing it months ago.
- Using urgency words on routine email, so real urgency stops registering.
- Leaving a merge tag unfilled, which announces the email as bulk before anyone opens it.
- Forgetting that a resignation or complaint subject line will be read by people you did not write it for.
A subject line kit you can copy
The kit below was written for this page. It is the shape rather than the wording: fill each placeholder with the specific noun, action and date from your own message, and delete the lines you do not need. Full messages sit in our sales templates library.
Ask, with a date: {{project}}: {{what you need}} by {{date}} Decision between two options: Decision needed by {{date}}: {{optionA}} or {{optionB}} Recurring status: {{project}} status, week of {{date}} Information only: No action needed: {{topic}} First contact with a stranger: Question about {{company}} and {{process}} Follow-up that closes the loop: Still useful, or should I close this out?
You fill the placeholders with category words, so "{{project}}" becomes "update" and "{{what you need}}" becomes "your input". The shape is fine; the specifics are what get the email opened. Also check that the body delivers exactly what the line promised.
Frequently asked questions
What are good professional email subject line examples?
Good professional email subject line examples name a topic, an action and a date: "Q4 budget: two numbers I need by Friday", "Approval needed: vendor contract by Thursday", or "Agenda for the March 14 review". Each one tells the reader what to do before they open it.
How long should an email subject line be?
Short enough that the first few words carry the message, because phones and desktop clients cut the line at different widths. Mailchimp advises its senders to use no more than nine words and sixty characters, and notes that shorter is often better on mobile.
How do you write a subject line for a professional email?
Write the email first, then name the one action it asks for, add the specific project or document name, include the date if one exists, and move the important words to the front. Finally, check that the body delivers what the line promised.
What is a good subject line for a cold email?
One that looks like ordinary work email about a real thing: "Question about {{company}} and {{process}}" or "How {{role}} teams handle {{problem}}". Name something specific you actually looked up. Avoid fake familiarity such as "Re:" or "as discussed" on a first contact.
What is a good follow up email subject line?
Either a genuine reply inside your own thread, or a new line with a new angle: "{{project}}: one decision still open" or "Still useful, or should I close this out?". Avoid "just following up", which describes your calendar rather than the reader's problem.
What subject line should I use for a job application?
Use the exact role title and any requisition number from the posting, plus your name: "Application: {{job title}} ({{req number}}), {{your name}}". Hiring inboxes are filtered and forwarded, so the identifiers matter far more than clever wording.
What is a good subject line for a resignation email?
State the fact and the date: "Resignation: {{your name}}, last day {{date}}" or "Notice of resignation, effective {{date}}". It goes into a personnel file, so keep it plain, keep any feeling for the body, and send it to your manager first.
What is a good subject line for a meeting request?
Name the topic and the length, or offer the times directly: "Meeting request: pricing review, 30 minutes" or "Pricing review: Tuesday 10am or Thursday 2pm?". Offering two concrete times usually gets an answer faster than asking for availability.
What makes a subject line deceptive under CAN-SPAM?
The FTC's compliance guide says the subject line must accurately reflect the content of the message. Dressing an advertisement as an account notice, or promising something the body does not contain, is deceptive. The law makes no exception for business-to-business email.
Can you use "Re:" in a subject line if it is not a reply?
No. Google's email sender guidelines say not to send messages with subject lines starting with "Re:" or "Fwd:" unless they are actual replies or forwards, and the FTC treats misleading subject lines as a CAN-SPAM violation in commercial email.
Should you use emojis in a professional email subject line?
In most work email, no. Mailchimp advises at most one emoji, used to supplement words rather than replace them, and Google prohibits emoji used to imitate graphic elements in order to deceive. For clients, HR and first contacts, use none.
How many characters of a subject line show on a phone?
It depends on the device, the font size and the mail app, so no single number is reliable. Send the draft to your own phone and look at the inbox list. Write so the line still makes sense if it is cut in half.
Why do my subject lines get ignored?
Usually because they name a category instead of a thing: "update", "quick question", "touching base". Replace the category word with the real project, client or document name, add the action, and put a date in when one exists.
What is preview text and does it matter?
Preview text is the snippet an inbox shows next to the subject line. If you do not set it, the client pulls whatever text comes first, often a greeting or an unsubscribe note. Treat the subject line and the preview as one message.
- Federal Trade Commission, CAN-SPAM Act: A Compliance Guide for Business, for deceptive subject lines, header information, the postal address, opt-out timing, the B2B scope and the penalty amount, checked Sep 23, 2026.
- Google Workspace Admin Help, Email sender guidelines, for misleading subject lines and headers, the "Re:" and "Fwd:" rule, emoji used to deceive and one-click unsubscribe, checked Sep 23, 2026.
- Mailchimp Help Center, Best Practices for Email Subject Lines, for the word and character ceiling, mobile length, punctuation and emoji guidance, checked Sep 23, 2026.
- Purdue OWL, Email Etiquette, for the role of a meaningful subject line, checked Sep 23, 2026.
- Jeluvi entries this guide builds on: how to introduce yourself in an email, how to end an email, email greetings, cold email, sales cadence.
- All 59 subject lines, the rewrite table and the kit were written for this page. No open rate figures are quoted, from any vendor or any study.