Sales Follow-Up Email Templates
Ten follow-ups for the moments B2B reps actually face, from the first unanswered email to the deal that went quiet, each with when to send it and why it is written that way.
The templates
- Templates
- 10
- Updated
- November 19, 2026
- Section
- Outreach & Sequencing
A first email is easy to miss, and a good meeting is easy to forget once the buyer is back in their week. What keeps a deal moving is the follow-up, and the follow-up is where reps fall back on "just checking in": an email that asks the buyer to do the work of remembering why they should care.
The templates below are written for specific moments, not for a sequence slot. Each one carries something the last email didn't (a recap, a new reason, a direct question, an easy way to say no), and each asks for one thing. Replace every {{field}} with something true about this buyer before you send it; a template sent with its blanks filled generically reads exactly like one.
How to use these templates
- One ask per email. A reply, a time, a yes or no. Two asks get neither.
- Make it readable on a phone. If it needs scrolling, cut it.
- Reply in the same thread when you are following up on the same ask, so the context is one scroll away. Start a new thread when the angle changes.
- Never put "Re:" on an email that isn't a reply. Buyers notice, and it spends trust you'll need later.
- Say something new every time. If you have nothing new to add, the next email is the one that closes the loop.
- Make "no" easy. A clear no lets you stop, update the CRM and spend the time on someone who is buying.
Following up on cold outreach
The first follow-up to a cold email has one job: put the original ask back in front of the buyer without repeating it at length. The second has to earn its place with something the first didn't have.
Subject Re: {{original_subject}}
Hi {{first_name}},
Bringing this back to the top of your inbox. The short version: {{one-line reason you wrote, tied to something specific at their company}}.
If it isn't on your plate this quarter, a one-word "no" genuinely helps, and I'll close the loop.
{{your_name}}
Why it works: It sits under the original email, so it doesn't restate it. It is short enough to answer from a phone, and it gives the buyer a polite way out, which is often what gets a reply at all.
Subject {{company}} and {{topic}}
Hi {{first_name}},
One more thought since my last note. I saw {{specific trigger: a new hire, a launch, a job post, a funding round}}, and teams at that point often have to work out {{the problem it creates}}.
{{One sentence on how you help, or a link to something useful even if they never buy}}.
Worth 20 minutes to compare notes, or should I check back later in the year?
{{your_name}}
Why it works: A new thread with a new angle reads as a new reason, not a reminder. The trigger shows you looked; the either-or question at the end is easy to answer either way. Job changes make good triggers, as our guide to job change signals explains.
Following up after a call, demo or proposal
Once you have spoken, the follow-up stops being about attention and starts being about momentum. The best ones are written to be forwarded: the person you met is rarely the only one who decides.
Subject Recap and next steps from today
Hi {{first_name}},
Thanks for the time today. Here's what I heard, so you can correct anything I got wrong:
• Where things stand: {{current process or tool}}
• What isn't working: {{the problem, in their words}}
• What a good outcome looks like: {{their success criteria}}
• Who else weighs in: {{stakeholders they named}}
Next step we agreed: {{action}} on {{date}} (invite sent). Before then I'll {{your commitment}}; could you {{their commitment}}?
{{your_name}}
Why it works: A recap in the buyer's own words proves you listened and gives them something accurate to pass on. Naming both sides' commitments turns "let's reconnect" into a plan.
Subject {{company}} demo: summary to share
Hi {{first_name}},
Thanks for walking through {{product}} with us today. Here's a three-line summary in case it's useful to forward:
1. {{Their problem}}, which today costs the team {{the cost they described, in their words}}.
2. What we showed: {{the one or two parts of the product that answer it}}.
3. What happens next: {{the agreed step, e.g. a trial, a technical review, a pricing conversation}}.
You asked about {{open question}}; {{answer, or when you'll have it}}.
{{your_name}}
Why it works: Your champion has to explain the demo to people who weren't in it. Writing that explanation for them, short and in their terms, is the most useful thing a demo follow-up can do. Answering the open question shows the call was heard.
Subject Re: {{proposal_name}}: questions so far?
Hi {{first_name}},
Checking in on the proposal I sent on {{date}}. Proposals tend to raise questions the document doesn't answer, often about {{likely concern: rollout effort, contract terms, security review}}.
Would it help to walk {{finance, procurement or another stakeholder}} through it on a short call? I can do {{two specific times}}.
If priorities have shifted, tell me and I'll adjust the timeline rather than keep nudging.
{{your_name}}
Why it works: It names the likely objection instead of asking whether they "had a chance to look". Offering to brief the person who signs off makes the next step concrete, and the last line keeps the forecast honest.
Subject Missed you today: new time?
Hi {{first_name}},
Looks like we missed each other at {{time}}. No problem, calendars move.
Here's my link to pick a new time: {{scheduling_link}}. Or reply with a day that works and I'll send the invite.
If the timing is off altogether, say so and I'll follow up in {{month}} instead.
{{your_name}}
Why it works: No guilt, no "per my last email". Two easy ways to rebook and a third option that still gets you an answer.
Following up on event and inbound leads
A lead who came to you has already told you something. The follow-up should show you know what it was. Speed matters here more than anywhere else; see inbound lead response time for why.
Subject Following up from {{event_name}}
Hi {{first_name}},
Good to {{meet you / see you}} at {{event_name}}. You mentioned {{something specific they said, or the session they attended}}, and it stuck with me.
{{One relevant resource, idea or answer to a question they asked}}.
If it's useful to dig in, I'm free {{two times}}. Otherwise, hope the rest of {{the quarter}} goes well.
{{your_name}}
Why it works: The specific reference is what separates this from the badge-scan blast every attendee receives. It gives before it asks, and the ask is optional.
Subject Your {{trial / request}} at {{your_company}}
Hi {{first_name}},
You {{signed up for / asked about}} {{product}} on {{day}}. People who do that are usually trying to {{common job to be done}}. Is that what you're after, or something else?
If it helps, I can {{set up the trial for your use case / show the part you asked about}} in 15 minutes: {{scheduling_link}}.
{{your_name}}
Why it works: It asks what they came for before pitching anything, and the answer tells you how to qualify them. More on turning sign-ups into pipeline in converting free-trial signups with outbound sequences.
Re-engaging a quiet deal, and closing the loop
Silence after real interest usually means something changed on the buyer's side. Ask what, directly. And when there is nothing left to say, say so: the last email is a follow-up too.
Subject {{project_name}}: still a priority?
Hi {{first_name}},
We last spoke on {{date}} about {{project}}, and things have gone quiet, which usually means something changed. Is it one of these?
1. Budget or timing moved
2. Someone new needs to weigh in
3. A review (security, legal, procurement) is under way
4. The problem dropped down the list
Reply with a number and I'll respond accordingly. Even a "4" helps me stop guessing.
{{your_name}}
Why it works: A reply costs the buyer a single keystroke, and each answer points to a different next move. Our guide to opportunity stall detection covers how to read each blocker and what to do about it.
Subject Closing the loop
Hi {{first_name}},
I haven't heard back, so I'll assume {{the problem}} isn't a priority right now and stop reaching out.
If that changes, reply to this email any time. It comes straight to me.
Thanks,
{{your_name}}
Why it works: It is honest about what is happening and leaves the door open without guilt. It sometimes draws the reply the others didn't; if not, you can stop working the account with a clear conscience.
How long to wait between follow-ups
There is no single right gap, and any template that promises one is guessing about your buyers. Work from what the buyer told you and what your own data shows:
- After a conversation, follow the buyer's timeline. If they said they'd decide after the board meeting, follow up after the board meeting, not on day three.
- For cold outreach, space touches out and change channel rather than sending the same email closer together. Multichannel sequence design shows how to sequence email, phone and LinkedIn.
- Let engagement decide the next step. A reply, a click or a visit to your pricing page should change what comes next; sequence branching logic covers how to set that up.
- Measure replies by step, not just by sequence. If a step rarely draws a reply, cut it or rewrite it. Compare against sequence performance benchmarks for your segment.
Keep follow-ups out of spam
Follow-ups multiply the volume you send from a domain, so they are where deliverability problems show up first. Authenticate the sending domain with SPF, DKIM and DMARC, keep spam complaints low, give people an easy way to opt out, and stop sending to addresses that bounce.
For the details, read Google and Yahoo's bulk sender requirements for sales email, separate domain architecture for high-volume sales email and email warm-up strategies for new sending domains.
Questions
How many follow-up emails should I send?
Enough to say something new each time, and no more. Stop at a clear "no" or an unsubscribe, and end with an email that closes the loop. Your own reply data by step is the best guide to where the sequence stops paying off.
Should a follow-up reply in the same thread or start a new one?
Reply in the thread when you are following up on the same ask, so the buyer has the context. Start a new thread with a new subject when the angle changes, and never add "Re:" to an email that isn't a reply.
What subject line should a follow-up email use?
Short and specific to the buyer or the conversation: a recap, a project name, the event you met at. Test subject lines on replies rather than opens; cold email subject line testing explains why.
Should I follow up on LinkedIn as well as email?
Often, yes: a second channel reaches people who don't live in their inbox. Make the LinkedIn touch stand on its own rather than repeating the email; see LinkedIn connection message examples.
Can AI write or send follow-ups for me?
It can draft them and, for some tasks such as booking a meeting, send them. Where the hand-off to a human sits matters more than the drafting; AI follow-up agents that book meetings compares the approaches.