Email Subject Lines: 150+ Examples Sorted by the Job They Do
152 original email subject lines for welcome, onboarding, sale, newsletter, win-back and follow-up emails, each with a character count and why it works.
By Cyril Nie, founder of Spreeflo · All 80 examples written for this page, character counts checked by script on 27 October 2026
Published · Updated
Work email gets read twice: once in the inbox, and again weeks later when someone searches for it.
A good business email subject line names the topic and what you need, in about four to nine words: "Invoice #1042 for October, due 15 November" or "Approval needed: Q1 ad budget by Thursday". Put the key words first, include a number, date or name when you have one, and make sure the email says what the subject promised.
Below are 80 original email subject lines for business, sorted by the work situation they're for. Every example has a character count (spaces and punctuation included). Swap in your own names, numbers and dates. Then the mistakes that get business emails ignored, and how to stop retyping the same ones.
A business or formal email subject line has two jobs. It has to get the email opened today, and it has to be findable next month when someone searches their inbox for "invoice" or "Fernway". Both point the same way: be literal.
A simple formula covers most work email:
[Topic] + [what you need or what's inside] + [a date or number, if there is one]
Topic only: "Proposal" (too vague)
Topic and ask: "Proposal: Decision needed" (better)
Topic, ask and date: "Proposal for Fernway: Decision needed by Friday" (clear, searchable, and the reader knows the stakes)
A colon is useful in work email: it splits the label from the detail. If you use one, capitalize the first word after it, as the Microsoft style guide does for headings (our page on subject line capitalization explains why sentence case suits email).
Say who's being introduced, or who sent you. A name they know gives a stranger a reason to open.
| Subject line | Characters | Use it when |
|---|---|---|
| Intro: Dana Okafor (Fernway) and Sam Lee (Loop Studio) | 54 | A mutual introduction between two people |
| Sam suggested I reach out about your hiring tool | 48 | Cold-ish outreach with a real referral |
| Introducing myself as your new account contact | 46 | Taking over an existing relationship |
| New supplier intro: Fernway Packaging | 37 | Introducing your company to a buyer |
| Great to meet you at Thursday's meetup | 38 | After meeting in person |
| Your new point of contact from 1 December | 41 | A planned handover |
| Intro request: Could you connect me with Ana? | 45 | Asking someone for an introduction |
| Following your talk: A question about pricing pages | 51 | Reaching out after a talk or post |
| Partnership idea: Joint webinar in March | 40 | Pitching a specific collaboration |
| Who handles vendor onboarding at Fernway? | 41 | Finding the right person |
Give the length, the topic, and if you can, a time. Two options are easier to answer than "Can we chat?"
| Subject line | Characters | Use it when |
|---|---|---|
| 30 minutes next week to plan Q1? | 32 | Asking for time with a clear purpose |
| Can we meet Tue or Wed about the renewal? | 41 | Offering two options |
| Request: 20-minute call on the API delay | 40 | A short call about one issue |
| Kickoff call for the website project: Pick a time | 49 | Starting a project |
| Confirmed: Thursday 2pm, Fernway office | 39 | Locking in the details |
| Moving our Friday call to Monday 10am? | 38 | Rescheduling with a proposal |
| Agenda for tomorrow's 3pm review | 32 | Preparing people for a meeting |
| Need 15 minutes before the board deck goes out | 46 | An urgent, time-boxed ask |
| Coffee in Shoreditch on the 12th? | 33 | An informal meeting |
| Cancelling today's call (new time inside) | 41 | Cancelling without leaving a gap |
Put the scope and, where it helps, the price and validity date in the subject. The buyer often forwards your email to someone else, and the subject travels with it.
| Subject line | Characters | Use it when |
|---|---|---|
| Proposal: Website redesign, $8,400, valid to 30 Nov | 51 | Sending a proposal with the key terms |
| Your quote for 500 printed boxes | 32 | Sending a quote |
| Revised proposal with the changes you asked for | 47 | Sending a second version |
| Two options for the Q1 retainer | 31 | Giving the buyer a choice |
| Proposal for Fernway: Decision needed by Friday | 47 | When there's a real deadline |
| Updated quote: Shipping now included | 36 | Flagging what changed |
| Scope, timeline and price for the audit | 39 | Listing what's inside |
| Answers to your 3 questions on the proposal | 43 | Handling objections in writing |
| Signed contract attached, plus next steps | 41 | Closing the deal |
| Proposal expires Friday: Anything you need from me? | 51 | A polite final nudge |
Invoice subject lines should always include the invoice number. It's the thing the person paying will search for, and the thing their accounts team will ask about.
| Subject line | Characters | Use it when |
|---|---|---|
| Invoice #1042 for October, due 15 November | 42 | Sending a new invoice |
| Invoice #1042: Due in 7 days | 28 | A friendly early reminder |
| Reminder: Invoice #1042 is due tomorrow | 39 | The day before |
| Invoice #1042 is 10 days overdue | 32 | First overdue notice |
| Second reminder: Invoice #1042 ($2,150) | 39 | Adding the amount to raise the stakes |
| Final notice before late fees on #1042 | 38 | Last step before your terms kick in |
| Payment received for invoice #1042, thank you | 45 | Confirming payment |
| Your receipt for the November retainer | 38 | Sending a receipt |
| Can we set up a payment plan for #1042? | 39 | Offering flexibility |
| Updated bank details for future payments | 40 | Changing payment details (confirm by phone too) |
A sensible sequence for an invoice nobody's paid: the invoice, a reminder a week before it's due, one the day before, a first overdue notice, a second with the amount, then a final notice that names your late-fee terms. Only mention late fees your contract actually includes.
A note on "Updated bank details": requests to change payment details are a classic invoice scam, so expect careful clients to call to confirm. Say in the email that they should.
A follow-up should point back to something real and make answering easy. A question that takes one word to answer is easier to reply to than "Just checking in". Our sales follow-up email templates have the full emails for these.
| Subject line | Characters | Use it when |
|---|---|---|
| Following up on Tuesday's proposal | 34 | The first follow-up |
| Still interested in the March start date? | 41 | Checking a timeline |
| One question left before we can start | 37 | Unblocking a project |
| Re-sending the contract link (old one expired) | 46 | A practical resend |
| Any update on the purchase order? | 33 | Chasing paperwork |
| Closing the loop on the pricing question | 40 | Wrapping up an open thread |
| Should I hold the April slot for you? | 37 | A soft deadline |
| Last follow-up on the partnership idea | 38 | The final nudge |
| Notes and next steps from today's call | 38 | After a meeting |
| Did the brief reach the right person? | 37 | When you suspect it's stuck |
Lead with the status. People skim updates, so the subject should carry the headline: on track, delayed, done.
| Subject line | Characters | Use it when |
|---|---|---|
| Weekly update: Homepage done, checkout next | 43 | Regular status email |
| Project status: On track for 14 March launch | 44 | Good news with the date |
| Delay on the API work: New date 21 March | 40 | Bad news with the new plan |
| Done: Migration finished, nothing lost | 38 | Announcing completion |
| Heads up: Budget at 80% with 2 weeks left | 41 | Early warning |
| Handover notes for the Fernway account | 38 | Passing work to a colleague |
| Week 6 report: 3 wins, 1 risk | 29 | Scannable summary |
| Launch moved to Monday; here's why | 34 | Explaining a change |
| Decision log from this week's sprint | 36 | Recording what was agreed |
| Out 2 to 6 Dec: Who to contact instead | 38 | Before time off |
Bad news in the subject line feels uncomfortable, but it's kinder than a cheerful subject over a delay. The reader trusts the next update more.
Say what decision you need and by when. If it's a yes or no, say that too.
| Subject line | Characters | Use it when |
|---|---|---|
| Approval needed: Q1 ad budget by Thursday | 41 | Asking for sign-off with a deadline |
| Can you review the draft by 5pm? | 32 | A same-day review |
| Quick yes or no: Renew the hosting plan? | 40 | A one-word decision |
| Need your logo files for the print run | 38 | Asking for assets |
| Sign-off needed on the final designs | 36 | Final approval |
| Request: Access to the analytics account | 40 | Asking for access |
| Decision needed: Ship Friday or wait a week? | 44 | Framing the choice |
| Please fill in the onboarding form (5 min) | 42 | Asking a client for information |
| Missing info for your account setup | 35 | When something's blocking you |
| Feedback by Monday on the pricing page? | 39 | Asking for input with a date |
Ending things well is part of business email too. Be clear in the subject, and save the warmth for the body.
| Subject line | Characters | Use it when |
|---|---|---|
| Thank you for the referral to Fernway | 37 | Thanking someone for a lead |
| Thanks for today, plus my 3 next steps | 38 | Thanks plus commitments |
| We're going with another supplier this time | 43 | Declining a vendor kindly |
| Not a fit now, but here's who might be | 38 | Saying no with a referral |
| Saying no to the March project (and why) | 40 | Declining work |
| Project closed: Final files and invoice | 39 | Ending a project |
| Thanks for 2 years of working together | 38 | Ending a relationship well |
| Welcome aboard: What happens this week | 38 | Starting with a new client |
| Happy to help: The contact you asked for | 40 | Answering a favour |
| Wrapping up: Everything you need in one place | 45 | A final summary email |
Long enough to say the topic and the ask, which for most work email is four to nine words. The published guidance points the same way: Mailchimp recommends no more than 9 words and 60 characters (Mailchimp), and Constant Contact suggests 4 to 7 words or 40 characters or fewer (Constant Contact). Litmus reports that phones show only about 25 to 30 characters of a subject line (Litmus), so the first few words need to carry the meaning.
The 80 examples above run from 28 to 54 characters, with a median of 39, and none is longer than 9 words. Business lines run a little longer than marketing ones because they carry invoice numbers, dates and names, and in work email those details are the point.
Saying nothing. "Quick question", "Hi" and "Checking in" tell the reader nothing and are impossible to find later.
Fake "Re:" and "Fwd:". Google's sender guidelines say not to start a subject with "Re:" or "Fwd:" unless the message is actually a reply or forward (Google). People notice, too.
"URGENT" in capitals. If it's urgent, say why and by when: "Need your sign-off by 3pm for the print deadline". All caps is also a spam-filter signal, though a small one; our capitalization guide has the detail.
Burying the ask. "Some thoughts on the project, plus a request about next week's budget" puts the request where a phone won't show it. Lead with the request.
Changing the topic mid-thread. If a thread about the March launch turns into a conversation about invoices, start a new email with a new subject.
A subject that doesn't match the email. Annoying in a one-off email, and a legal issue in a commercial one: the CAN-SPAM Act requires that a subject line "accurately reflect the content of the message" (FTC).
Include a name when it tells the reader something: whose introduction it is, which client the proposal is for, who referred you. "Sam suggested I reach out" earns an open because Sam is a reason. Adding the reader's own first name to a one-to-one email adds little; they know who they are.
For emails you send to many contacts, names work best through personalisation that has a fallback, so nobody gets "Hi ," in the subject.
See it in Spreeflo: if you send the same kinds of business emails over and over (a proposal follow-up, an invoice reminder, a welcome-aboard note), save them as email templates and let Liquid fill in the details. With the CRM (Starter and up), {{ company.name }}, {{ deal.amount }} and {{ owner.first_name }} work in the subject line as well as the body. Try the email builder, no login →
Most small teams write the same dozen business emails every month. Three things in Spreeflo take the retyping out of it:
Saved email templates with personalisation. For the business emails you send from a campaign or journey, Spreeflo renders Liquid in the subject line, preview text and body, so one template can say "Proposal for {{ company.name }}: Decision needed by Friday" for every client. Use | default: for anything that might be empty, so a missing value doesn't leave a gap in the subject.
CRM context on the contact. On every paid plan, the CRM keeps notes, tasks, deals and every email on one timeline per contact, so before you write "Following up on Tuesday's proposal" you can see exactly what you sent on Tuesday. 1:1 emails from the Spreeflo inbox thread onto that same timeline.
Journeys for the repeatable ones. A change to a deal, such as its stage moving on, can start a journey on Starter (the Object Updated trigger works on the CRM's built-in Deal object), with a next-steps email a few days later and a Create task step that reminds you to call. An invoice reminder can run from a Time trigger on a date attribute, like 7 days before a due date.
We wouldn't automate every business email. A personal reply to a client's question should be written by a person. But the reminders, confirmations and nudges you send the same way each time are a good fit.
Business email subject lines work best as labels. The best ones tell a busy person what this is, what you need, and by when, in words they'll type into a search box three weeks later. Write them that way, and the follow-ups get easier too.
Spreeflo gives small teams email templates with Liquid personalisation, a CRM that keeps every note and email on the contact, and journeys that send the repeat emails for you. Starter, with the CRM included for one seat, starts at $16 a month; Professional adds unlimited seats from $24.
Take the live tour → · See pricing
Name the topic, then what you need, then a date or number if there is one: "Approval needed: Q1 ad budget by Thursday". Keep it to about four to nine words, front-load the important ones, and make sure the email delivers what the subject says.
One that someone could act on without opening the email, and find again by searching. "Invoice #1042 for October, due 15 November" and "Confirmed: Thursday 2pm, Fernway office" are good because they're specific. "Quick question" is not, because it says nothing.
Include a name when it adds information, such as a referrer ("Sam suggested I reach out"), a client ("Proposal for Fernway") or the people in an introduction. The recipient's own first name adds little in a one-to-one email.
About four to nine words. Mailchimp recommends no more than 9 words and 60 characters, and Constant Contact suggests 40 characters or fewer. Phones show fewer characters than desktops, so put the topic and the ask first.
Email subject lines: 150+ examples sorted by the job they do
Sales follow-up emails that get replies: 25 templates for leads, demos and quotes
Promotional email subject lines: 70 for launches, discounts and last chances
Mailchimp: Best practices for email subject lines, read 27 October 2026
Constant Contact: Optimize the subject line in a campaign email, read 27 October 2026
Litmus: Email subject line best practices, read 27 October 2026
Google: Email sender guidelines, read 27 October 2026
FTC: CAN-SPAM Act compliance guide for business, read 27 October 2026
Discover more insights on similar topics
152 original email subject lines for welcome, onboarding, sale, newsletter, win-back and follow-up emails, each with a character count and why it works.
60 original sales email subject lines for inbound deals, sorted by stage: demo requests, trials, proposals and renewals, each with its character count.
70 original promotional email subject lines with pre-headers and character counts: launches, discounts, free shipping, last chance, restocks and carts.