Jump to a subject line category<\/p>\n
- \n
- After no response<\/a> (12)<\/li>\n
- Sales follow-up<\/a> (12)<\/li>\n
- Cold email follow-up<\/a> (10)<\/li>\n
- Post-meeting<\/a> (10)<\/li>\n
- Post-interview<\/a> (10)<\/li>\n
- Networking & reconnect<\/a> (10)<\/li>\n
- Post-event<\/a> (10)<\/li>\n
- Re-engagement \/ catch-up<\/a> (10)<\/li>\n
- B2B \/ enterprise<\/a> (8)<\/li>\n
- Internal team \/ project<\/a> (8)<\/li>\n
- 29 classic templates<\/a><\/li>\n
- Timing guide<\/a><\/li>\n<\/ul>\n<\/div>\n\n\n\n
What is a follow-up email?<\/h2>\n\n\n
\n![\"What](\"https:\/\/cdn3.notifyvisitors.com\/blog\/wp-content\/uploads\/2023\/03\/uH2V6kUKGN_What-is-a-follow-up-email.jpg\")
<\/figure>\n<\/div>\n\n\nA follow-up email<\/a> is a second message sent after a meeting, a call, an application or an earlier email that went unanswered. It restarts a conversation that has gone quiet.<\/p>\n\n\n\n
People send them to confirm next steps, chase a decision, share something they promised, or check whether a proposal landed. The subject line does most of the work, because it decides whether the email gets opened at all.<\/p>\n\n\n\n
100+ follow-up email subject lines by use case<\/h2>\n\n\n\n
Every line below stays under 50 characters so it survives mobile truncation. Square brackets mark the bit you replace.<\/p>\n\n\n\n
1. After no response (12 subject lines)<\/h3>\n\n\n\n
The hardest category. “Just checking in” gets ignored because it tells the reader you have nothing new to say. Give them a reason to reply instead.<\/p>\n\n\n\n
- \n
- Bumping this back to the top, [Name]<\/li>\n\n\n\n
- Did this get lost in your inbox?<\/li>\n\n\n\n
- Quick yes or no would help, [Name]<\/li>\n\n\n\n
- Should I close this out?<\/li>\n\n\n\n
- One more try before I drop this<\/li>\n\n\n\n
- [Name], are we still on for [topic]?<\/li>\n\n\n\n
- Is now a bad time to revisit this?<\/li>\n\n\n\n
- Re: [Original subject], any thoughts?<\/li>\n\n\n\n
- Closing the loop on [topic]<\/li>\n\n\n\n
- Three quick options for [Name]<\/li>\n\n\n\n
- Worth another 2 minutes, [Name]?<\/li>\n\n\n\n
- Last nudge on [topic]<\/li>\n<\/ul>\n\n\n\n
2. Sales follow-up (12 subject lines)<\/h3>\n\n\n\n
Sales follow-ups need a reason to exist. “Limited time!” is a reason you invented. “Q3 pricing locks in Friday” is a reason the prospect can check. Use the second kind.<\/p>\n\n\n\n
- \n
- [Name], thoughts on the proposal?<\/li>\n\n\n\n
- Pricing question for [Company]<\/li>\n\n\n\n
- Two paths forward for [Company]<\/li>\n\n\n\n
- Worth a 15-min call on [topic]?<\/li>\n\n\n\n
- [Name], the Q3 quote expires Friday<\/li>\n\n\n\n
- Quick update on [Company]’s setup<\/li>\n\n\n\n
- Saw [trigger event] at [Company]<\/li>\n\n\n\n
- 3 ways we’d reduce [pain point]<\/li>\n\n\n\n
- Should I keep the slot open?<\/li>\n\n\n\n
- [Name], picking this up where we left off<\/li>\n\n\n\n
- Re: [Company] proposal, final version<\/li>\n\n\n\n
- One small update for [Name]<\/li>\n<\/ul>\n\n\n\n
3. Cold email follow-up (10 subject lines)<\/h3>\n\n\n\n
Cold sequences usually run four to six touches. Change the framing on every touch and never send the same subject line twice.<\/p>\n\n\n\n
- \n
- [Name], 30 seconds for [Company]?<\/li>\n\n\n\n
- Idea for [Company]’s [team]<\/li>\n\n\n\n
- Quick question about [pain point]<\/li>\n\n\n\n
- Saw your post on [topic], [Name]<\/li>\n\n\n\n
- [Mutual contact] suggested I reach out<\/li>\n\n\n\n
- Helping [similar company] with [outcome]<\/li>\n\n\n\n
- Worth chatting about [topic], [Name]?<\/li>\n\n\n\n
- Thought you’d find this useful<\/li>\n\n\n\n
- Did you see this, [Name]?<\/li>\n\n\n\n
- One last try, [Name]<\/li>\n<\/ul>\n\n\n\n
4. Post-meeting (10 subject lines)<\/h3>\n\n\n\n
Send these within 24 hours, while the meeting is still fresh. The recipient is half expecting the email, so the subject line only has to say what it contains.<\/p>\n\n\n\n
- \n
- Recap from today’s meeting, [Name]<\/li>\n\n\n\n
- Action items from our chat<\/li>\n\n\n\n
- Great talking with you today<\/li>\n\n\n\n
- Notes + next steps from [date]<\/li>\n\n\n\n
- Following up on this morning’s call<\/li>\n\n\n\n
- 3 takeaways from our session<\/li>\n\n\n\n
- [Name], here’s what we agreed on<\/li>\n\n\n\n
- Quick recap + the doc I promised<\/li>\n\n\n\n
- Notes from our [topic] discussion<\/li>\n\n\n\n
- That was helpful, here’s the summary<\/li>\n<\/ul>\n\n\n\n
5. Post-interview (10 subject lines)<\/h3>\n\n\n\n
Name the role. Hiring managers run several searches at once and a generic thank-you makes them work out who you are.<\/p>\n\n\n\n
- \n
- Thank you for the [role] interview<\/li>\n\n\n\n
- Following up on my [role] interview<\/li>\n\n\n\n
- Great talking about the [role] role<\/li>\n\n\n\n
- One follow-up thought from today<\/li>\n\n\n\n
- Thank you, [Hiring manager]<\/li>\n\n\n\n
- Quick note after our chat about [topic]<\/li>\n\n\n\n
- Re: [role] role, answering your question<\/li>\n\n\n\n
- Excited about the [role] opportunity<\/li>\n\n\n\n
- Following up on our conversation today<\/li>\n\n\n\n
- The [case study] we discussed<\/li>\n<\/ul>\n\n\n\n
6. Networking and reconnect (10 subject lines)<\/h3>\n\n\n\n
Reconnect emails work best when the first message asks for nothing. Warm and specific beats polished.<\/p>\n\n\n\n
- \n
- Long time no chat, [Name]<\/li>\n\n\n\n
- Saw your post on [topic], well said<\/li>\n\n\n\n
- Catching up after [event]<\/li>\n\n\n\n
- How’s life at [Company], [Name]?<\/li>\n\n\n\n
- Thought of you when I read this<\/li>\n\n\n\n
- Coffee in [City] this month?<\/li>\n\n\n\n
- Was just thinking about our [project]<\/li>\n\n\n\n
- Reconnecting after [time period]<\/li>\n\n\n\n
- [Name], congrats on the [milestone]<\/li>\n\n\n\n
- It’s been a while, how are you?<\/li>\n<\/ul>\n\n\n\n
7. Post-event (10 subject lines)<\/h3>\n\n\n\n
Send within 48 hours. After a three-day conference nobody remembers which conversation was yours, so reference something only you two discussed.<\/p>\n\n\n\n
- \n
- Great meeting you at [event], [Name]<\/li>\n\n\n\n
- Following up from [event]<\/li>\n\n\n\n
- The [tool] I mentioned at [event]<\/li>\n\n\n\n
- Loved your [event] talk on [topic]<\/li>\n\n\n\n
- Conference recap + the link I promised<\/li>\n\n\n\n
- [Name], picking up from [event]<\/li>\n\n\n\n
- That chat about [topic] at [event]<\/li>\n\n\n\n
- Saw you speak at [event]<\/li>\n\n\n\n
- Worth a follow-up after [event]?<\/li>\n\n\n\n
- Quick thank-you from [event]<\/li>\n<\/ul>\n\n\n\n
8. Re-engagement and catch-up (10 subject lines)<\/h3>\n\n\n\n
These go to people who went quiet 60 days ago or more. Aim for a reply, not a meeting. Asking for the meeting straight away is what killed the thread the first time.<\/p>\n\n\n\n
- \n
- [Name], it’s been a minute<\/li>\n\n\n\n
- What’s new at [Company], [Name]?<\/li>\n\n\n\n
- Coming back to this, [Name]<\/li>\n\n\n\n
- Picking up where we left off<\/li>\n\n\n\n
- Still on your radar: [topic]<\/li>\n\n\n\n
- Worth revisiting [topic]?<\/li>\n\n\n\n
- Better timing now, [Name]?<\/li>\n\n\n\n
- Q3 update, does this still apply?<\/li>\n\n\n\n
- [Name], something changed since we spoke<\/li>\n\n\n\n
- Reviving this thread, [Name]<\/li>\n<\/ul>\n\n\n\n
9. B2B and enterprise (8 subject lines)<\/h3>\n\n\n\n
Enterprise cycles run three to nine months, so the subject line should read like part of a process someone is managing rather than a one-off ask.<\/p>\n\n\n\n
- \n
- [Company]: Q4 roadmap question<\/li>\n\n\n\n
- Aligning [Company] + [Vendor] for FY26<\/li>\n\n\n\n
- Procurement check-in: [Company]<\/li>\n\n\n\n
- [Name], the SOC 2 doc you needed<\/li>\n\n\n\n
- Deal review: [Company] x [Vendor]<\/li>\n\n\n\n
- Exec-level summary for [Name]<\/li>\n\n\n\n
- Quarterly business review prep<\/li>\n\n\n\n
- [Company]: integration update<\/li>\n<\/ul>\n\n\n\n
10. Internal team and project (8 subject lines)<\/h3>\n\n\n\n
Your colleagues open your emails anyway. These only need to signal priority and deadline.<\/p>\n\n\n\n
- \n
- Bumping: [Project] decision needed<\/li>\n\n\n\n
- Status check: [Project] EOD?<\/li>\n\n\n\n
- Friendly nudge: [Task] still on track?<\/li>\n\n\n\n
- Action needed by Friday: [topic]<\/li>\n\n\n\n
- Quick check-in on [Project]<\/li>\n\n\n\n
- Blocker on [Project], need 5 min<\/li>\n\n\n\n
- Sync prep: agenda for tomorrow<\/li>\n\n\n\n
- EOW status: [Project]<\/li>\n<\/ul>\n\n\n\n
Why some follow-up subject lines get opened<\/h2>\n\n\n\n
Six things separate a subject line that gets a reply from one that gets archived. Pick two of them. Three starts to feel like you are trying too hard, and four reads as manipulation.<\/p>\n\n\n\n
Short beats long. “Worth chatting?” does the same job as “Wanted to circle back to see if you might have time for a brief discussion” and does it in four words. Three to seven words is the range worth aiming at.<\/p>\n\n\n\n
Specific beats vague. “Re: Q3 budget” tells the reader what they are about to open. “Re: our discussion” makes them guess, and people sitting on 50 unread emails do not guess.<\/p>\n\n\n\n
Curiosity works until it doesn’t. “One small update for [Name]” makes someone want to look. “You won’t believe this” makes them look once and ignore you forever after. If the email does not pay off the curiosity, you have spent a customer.<\/p>\n\n\n\n
Personalisation needs company. A first name on its own does very little. A first name attached to something real, their company, their recent post, a deadline they care about, does considerably more.<\/p>\n\n\n\n
Urgency has to be true. “The Q3 quote expires Friday” works because the reader can verify it and will remember if it was a lie. “Limited time only” is a phrase people have learned to read past.<\/p>\n\n\n\n
Borrowed authority helps on cold sends. “[Mutual contact] suggested I reach out” borrows trust you have not earned yet. So does naming a company like the reader’s that you already work with.<\/p>\n\n\n\n
Length and format rules<\/h2>\n\n\n\n
Aim for 30 to 50 characters. Gmail on an iPhone shows around 35, Android around 30, Outlook on desktop about 60. Anything in the 30 to 50 window reads in full almost everywhere.<\/p>\n\n\n\n
Put the important part first. If the subject gets clipped, the opening 30 characters have to carry the meaning on their own, so do not bury the topic at the end.<\/p>\n\n\n\n
Use “Re:” only when you are actually replying to a thread. It signals existing context, which is exactly why it feels dishonest when there is no thread behind it. On a genuine second touch it earns its place.<\/p>\n\n\n\n
When a thread has gone dead, a completely new subject line sometimes outperforms continuing the old one. The original subject is the thing the reader already ignored, so giving them the same words again rarely helps.<\/p>\n\n\n\n
Write in sentence case. “Quick question about pricing” reads like a person. “Quick Question About Pricing” reads like a campaign, which is fine for promotional sends and wrong for follow-ups.<\/p>\n\n\n\n
Skip the capitals and the exclamation marks. “URGENT!!!” is a pattern spam filters were built to catch, and it will find the junk folder even from a clean sending domain.<\/p>\n\n\n\n
When to send a follow-up email<\/h2>\n\n\n\n
Timing matters about as much as wording. Too soon reads as impatient, too late and the reader has forgotten the context.<\/p>\n\n\n\n
\n
- Sales follow-up<\/a> (12)<\/li>\n
![\"Examples](\"https:\/\/cdn3.notifyvisitors.com\/blog\/wp-content\/uploads\/2023\/03\/V3uFMBmSSo_Examples-of-effective-follow-up-email-subject-lines.jpg\")
<\/figure>\n<\/div>\n\n\n![\"Tips](\"https:\/\/cdn3.notifyvisitors.com\/blog\/wp-content\/uploads\/2023\/03\/F4dgZzxacU_Tips-for-writing-effective-follow-up-email-subject-lines.jpg\")
<\/figure>\n<\/div>\n\n\n