Sales call follow-up emails written to be forwarded

This page is for account executives, SDRs, founders and consultants who have just finished a sales call and need to write the email that keeps the deal moving. It covers discovery calls, demos, pricing conversations, calls that ended without a plan and calls the prospect missed. If you haven't had the call yet, plan it first with the sales call planning template.

What the email has to do

A sales call creates agreement in the moment. The follow-up turns it into something your contact can act on and pass along. A good one does five jobs:

1. Confirms you listened. Two or three things the prospect said, in their words where you can. This is the part they'll check.
2. Fixes the next step. What happens next, who does it and by when. "Let me know your thoughts" isn't a next step.
3. Keeps your promises. Whatever you said you'd send, attached or linked, and nothing else.
4. Answers what you couldn't on the call. The question you said you'd check, answered in a sentence.
5. Survives the forward. Someone who wasn't on the call can read it cold and understand the problem, the proposal and the decision.

Send it within a few hours, and certainly the same day. Your notes are fresh, and a same-day recap shows the prospect how you'll behave as a supplier.

Choose the email by how the call ended

Sales call follow-up email templates

Fill every bracket from your call notes. If you can't fill one, leave the line out rather than inventing it.

Subject: [Topic]: notes from [day]'s call

Hi [first name],

Thanks for the time today. Here's what I heard, so we're working from the same notes:

- [Their problem, in their words: "We rebuild invoices by hand every Friday."]
- [Why it matters now: the trigger or deadline they mentioned]
- [How they'll decide: who's involved and by when]

Next steps:
- Me: [what you'll send or do] by [date]
- You: [what they agreed to do] by [date]
- Together: [the next meeting, date and time], invite sent

Did I miss anything or get anything wrong?

[Your name]

Subject: [Product] demo for [company]: the two things you asked about

Hi [first name],

Thanks for walking through [product] today. You were most interested in [feature 1] for [their use] and [feature 2] for [their use], so here are those two parts of the recording: [link with timestamps].

You asked whether [question]. The answer is [one sentence], and [where it's documented].

Who else would need to see this before you decide? Happy to run a shorter version for them.

[Your name]

Subject: [Company] quote: [amount] for [scope]

Hi [first name],

As promised, the quote is attached. The numbers rest on these assumptions, so you can check them before sharing:

- [Volume or scope you agreed, e.g. 12 people for 10 weeks]
- [Rate or price and what it includes]
- [What isn't included]

You mentioned [decision maker] decides by [date]. Is there anything in here they'll question first?

[Your name]

Subject: [Topic]: one idea after today's call

Hi [first name],

Thanks for today. It sounded like [problem] is real but not urgent until [their trigger or date].

Rather than another call, would it help if I [small, useful step: sent two sample profiles, ran the numbers on your data, shared a checklist] by [date]?

[Your name]

Subject: [Company] and [your company]: summary for [decision maker's name]

Hi [first name],

Here's a summary you can forward to [name], written so it stands on its own.

The problem: [one sentence, with the number they gave you]
What it costs today: [their figure, or the arithmetic you agreed]
What we proposed: [one sentence]
What it would cost: [price and term]
What we need from [company] to start: [one line]
Decision needed by: [date], because [their reason]

Would it help if I joined when you share it, to answer questions?

[Your name]

Subject: [Company] plan to [goal] by [date]

Hi [first name],

Here's the plan we sketched today. Please correct any dates that won't work.

1. [Date]: [step] (owner: [name])
2. [Date]: [step] (owner: [name])
3. [Date]: [decision meeting with whom] (owner: [name])
4. [Date]: [contract signed] (owner: [name])
5. [Date]: [start or go-live] (owner: [name])

The date that matters most is [go-live], because [their reason]. Working back from it, step [number] is the tight one.

[Your name]

Subject: [Day] at [time]: [topic]

Hi [first name],

Thanks for taking my call. As agreed, I've sent an invite for [day] at [time]. I'll come with [the specific thing you promised, e.g. the numbers for a nine-branch agency].

If [another person they mentioned] should join, feel free to forward the invite.

[Your name]

Subject: Missed you today: two new times?

Hi [first name],

Looks like today didn't work out, which happens. Would [day and time] or [day and time] suit better?

If [the topic] has dropped down the list, a one-line reply saying so is fine too.

[Your name]

Subject: Your question about [the objection]

Hi [first name],

You asked [the objection, in their words]. Fair question, and I didn't want to guess.

[The answer in two sentences, with the evidence: a document, a reference you have permission to share, or the numbers.]

Does that settle it, or is there more behind the concern?

[Your name]

For objections you'll hear again, the objection handling guide has tested responses for price, timing and "we already use someone".

Worked example: a discovery recap with the numbers in it

Illustrative example. The companies, people and figures are fictional, to show the method.

The seller: Sam, an account manager at Northgate Staffing (northgatestaffing.example), a staffing agency that supplies warehouse workers. The prospect: Dana, operations director at Corbel Home Goods (corbelhomegoods.example), which runs a distribution center with 60 associates. The decision maker: Luis, Corbel's CFO, who wasn't on the call.

On the call, Dana said Corbel covers its 10-week peak season with overtime: 8 extra hours a week for each of the 60 associates. Their base rate is $20 an hour. Under the Fair Labor Standards Act, covered employees must be paid at least time and a half for hours over 40 in a workweek, so each overtime hour costs at least $30. Sam's quote for temporary associates is a bill rate of $27.50 an hour, which covers the worker's pay, payroll costs and the agency's margin.

The difference is $12,000 over peak, before training time. Dana's bigger concern was fatigue, so the recap leads with that and lets the numbers support it:

Subject: Peak staffing for the distribution center: notes for Luis

Hi Dana,

Thanks for the time today. Here's a summary you can forward to Luis.

What you told me: peak runs 10 weeks, and the current plan is 8 hours of overtime a week for all 60 associates. Two of your shift leads have said the team "can't do that for a second year". Luis decides by the end of the month, mainly on cost.

The numbers, using your $20 base rate: overtime is 480 hours a week at $30, or $144,000 for peak. Twelve temporary associates working the same 480 hours at our $27.50 bill rate comes to $132,000. That's $12,000 less before training time, and your current team goes back to 40-hour weeks.

Next steps:

• Me: two sample candidate profiles and our safety onboarding checklist by Thursday.
• You: the shift pattern for the first three weeks of peak.
• Both: 20 minutes with Luis next week; I've sent two time options.

Did I get anything wrong?

Sam

Why it works: it quotes Dana's real worry in her shift leads' words, shows the arithmetic so Luis can check it, admits what the numbers leave out (training time) and gives every next step an owner. Luis can read it without Dana in the room. If Luis is new to you, research him before the meeting: Bebop builds a playbook for each account with the people involved and what's happening at the company, which helps when the decision maker is someone you haven't met.

Subject lines that get the recap read

Name the topic and, where it helps, the date. Avoid "Following up" and "Checking in", which describe your action, not the content.

Recording, notes and AI notetakers

Many follow-ups are now drafted from call recordings or AI summaries. This is general information, not legal advice.

• Federal law allows one-party consent. It isn't unlawful for a party to a call to record it, or for someone to record with one party's prior consent, unless it's done for a criminal or tortious purpose.
• Some states require everyone's consent. California's Penal Code makes it an offense to record a confidential communication "without the consent of all parties". If anyone on the call could be in an all-party state, say at the start that you're recording and get agreement.
• Check the summary before you send it. AI notes can attribute a remark to the wrong person or turn "maybe next quarter" into a commitment. Recap only what you're sure was said.
• Don't paste the transcript. The prospect was there. They need the decisions, not the minutes.

Mistakes to avoid

• "Per our conversation, attached is our deck." It shows you didn't listen and gives them homework.
• Recapping your pitch instead of their problem. The reader wants to see their situation, not your features.
• A next step with no date. "We'll reconnect soon" means the deal has stalled.
• Attaching everything. Send what you promised. A case study they didn't ask for is a second email.
• Getting a fact wrong. A wrong number or name in the recap undoes the trust the call built.
• Waiting a week. By then the prospect has had three other calls and remembers none of the details.

Checklist before you send

• The subject line names the topic, not "Following up".
• At least two points are the prospect's, in their words where possible.
• Every number has its assumption written next to it.
• Every next step has an owner and a date, and the next meeting invite is already sent.
• You attached only what you promised.
• Someone who wasn't on the call could forward it, read it and act on it.
• There's one question at the end, not three.

Next step: if your recap gets no reply, don't resend it. Use the follow-up email templates for no response, which pick up a quiet deal with something new.