Sales follow-up email: templates for after the call, and how to make the write-up send itself (2026)

A sales follow-up email is the message a seller sends after a call or meeting to restate what was discussed, confirm what was decided, and fix the next step — with a date — before the conversation goes cold. It is the part of the sale that happens in writing, and in most pipelines it is where deals quietly stall: the call went well, the email was written two days later from memory, and the next step was "I'll be in touch".

This guide has three parts. What the email needs and five templates for the situations that come up. When to send it and how often. And the part that takes the time — the write-up of the call — which can be produced for you and filed in your CRM on its own, using nothing more than a meeting link and a BCC address.

What a sales follow-up email needs

Four things, in this order. Everything else is optional.

1. What you heard. Two or three lines restating the prospect's situation and problem in their words. This is the line that proves you listened, and it is the one prospects forward internally.
2. What was decided. Anything agreed on the call, one sentence each. "Agreed" and "still open" are different lines.
3. The next step, with a date. A demo on Thursday, a proposal by Friday, a call with their ops lead next week. A next step without a date is a wish.
4. One ask. Confirm the date, send the document, introduce the colleague. One — a follow-up with three asks gets none of them.

Keep it short enough to read on a phone without scrolling. The recording, the deck and the full notes are links, not attachments.

Five sales follow-up email templates

1. After a discovery call

Subject: Recap and next step — [Company] / [Your company]

Hi [Name],

Thanks for the time today. What I took away:

• You're running [process] across [teams], and it breaks when [problem] — roughly [frequency], at a cost of [impact].
• You've tried [what they tried]; it didn't hold because [reason].
• A decision would involve [names/roles], and you'd want it in place by [timeline] because [driver].

Based on that, I think this is something we solve well — specifically [one line].

Next step: a demo on [date, time] with [name] in the room, focused on [the problem]. I'll send the invite now; reply if the time doesn't work.

[Your name]

2. After a demo

Subject: [Product] for [problem] — what we showed and what's next

Hi [Name],

Thanks for having [names] join. The parts that mattered for [problem]:

• [Feature/flow 1] — how it handles [their scenario].
• [Feature/flow 2] — [their question], answered.

Still open: [question they raised] — I'll confirm with [team] by [date].

You mentioned [decision process]. Would a proposal covering [scope] by [date] be the useful next step, or do you want a second session with [role] first?

[Your name]

3. When they've gone quiet

Subject: Re: [previous subject]

Hi [Name],

When we spoke on [date], [problem] was costing you [impact], and you wanted it solved by [timeline]. I haven't heard back since the [demo/proposal] — usually that means priorities moved, or something in what I sent didn't fit.

Either is fine. If it's the second, tell me what didn't fit and I'll adjust; if it's the first, tell me when to check back and I'll leave you alone until then.

[Your name]

4. After "send me some information"

Subject: The information you asked for — and the one question it doesn't answer

Hi [Name],

As promised: [link to the one document that answers their question]. It covers [what].

The one thing it can't answer is how this applies to [their specific situation from the call]. That takes about twenty minutes with [role] — would [date option 1] or [date option 2] work?

[Your name]

5. After a meeting where a decision-maker was missing

Subject: Summary for [missing person's name] — [Company] / [Your company]

Hi [Name],

A short version you can forward to [missing person]:

• The problem: [one line in their words].
• What we'd change: [one line].
• What it costs / saves: [number, if you have one].
• What's been agreed so far: [next step and date].

If it's easier, I can walk [missing person] through it directly — [date option]. Otherwise I'll follow up after [agreed next step].

[Your name]

When to send a sales follow-up email, and how often

The same day. The first follow-up goes out while the call is still fresh on both sides — ideally within the hour. Every day of delay makes the summary vaguer and the prospect's memory of the call fainter.

Then on a schedule, not on a feeling. A rule of thumb that circulates among sales teams is the "2-2-2 rule": follow up after two days, then two weeks, then two months. The numbers are less important than the principle — each follow-up is planned when the previous one is sent, not when you happen to remember.

Each follow-up adds something. A restated question, a relevant document, a new date option. "Just checking in" adds nothing and trains the prospect to ignore the thread.

Stop with a clean exit. After the planned sequence, one final message that leaves the door open ("tell me when to check back") — and then stop. The prospect who comes back six months later comes back to the thread that ended politely.

The part that takes the time: the write-up

Every template above starts with the same block — what you heard. Writing it well takes longer than the rest of the email combined, because it means reconstructing the call from notes taken while also running the call. Skipped write-ups are the reason follow-ups go out two days late and say nothing specific.

If the call runs in InterMIND, the write-up is generated when the session ends: a recap with a title, an overview, key takeaways, sectioned points with timestamps, action items, open questions and topics, emailed to the registered participants. If the conversation produced nothing summarizable, no email is sent at all. The summary can be corrected on the recap page — every edit is a revision with a word-level diff against the AI original — and the corrected text is what the recap message shows afterwards.

The follow-up email then starts from the recap's takeaways and action items instead of from memory. The "what you heard" block is a paste and a trim. One boundary worth knowing: for ad-hoc meetings, only the latest session's recap is kept, mirroring how their chat is deleted after each call; a channel keeps the recap of every past session.

Getting the follow-up into the CRM without logging it by hand

Most CRMs accept email at an inbound address. Put it in the BCC field and the message is logged on the record the CRM matches against the other recipients. The vendors document the mechanics and the conditions:

• HubSpot — the logging address is copied from Settings → Objects → Activities → Email Log & Track. A logged email "will automatically be associated to the recipient's contact record, its primary associated company record, and the five most recent open deal records associated to the contact"; if no contact matches the recipient, one is created. The sender must be a HubSpot user, a connected work email or a configured alias. Two documented limits: "when a recipient is BCCed in an email, the email will not create a new record, and if the recipient exists as a contact, the email will not be logged on their existing record" — matching is on the To/CC recipients, not on BCC'd ones — and the email with headers and attachments cannot exceed 40 MB.
• Pipedrive — Smart Bcc gives the account a universal address, and "each lead and deal in your company's Pipedrive account has its own unique Bcc address." "If the address used to forward an email is linked to a contact person in Pipedrive, the email being forwarded will be linked to that contact person," and if no contact matches, "a new person contact will be created automatically." A documented requirement: "either DKIM or SPF must be correctly configured in your domain settings" for the sync to work. Available on all Pipedrive plans.
• Zoho CRM — the BCC Dropbox "provides a unique email address for each user in your Zoho CRM account." The recipient is matched by a configurable search pattern (Contacts only, Leads only, or Contacts then Leads, with the option to create a record when nothing matches). A documented condition: "only those email address(es) that are added to the verified email address list will be associated to the leads/contacts in Zoho CRM" — the sender has to be pre-verified. Association can take up to 3 minutes; attachments are capped at 10 MB.

Read together, the three describe the same contract: the CRM files the email on the record of a To/CC recipient it recognizes, and it accepts the email only from a sender it trusts — a verified address, an authenticated domain, a connected user.

How the InterMIND recap meets that contract

The recap email is designed to pass both checks:

• Participants stay in the To field. Their addresses are what the CRM matches against, so the write-up lands on the prospect's record, not in an unfiled inbox.
• The CRM address goes in the Recap copy field, on the meeting's row on the Meetings page or in a channel's display settings. Up to 10 confirmed addresses live in your personal address book and can be reused across meetings and channels. Available on every plan.
• Each new address is confirmed by a delivery test. InterMIND sends a test email shaped like a real recap; someone opens it inside the receiving tool and clicks its confirmation link within 1 hour. Until then the address is pending and no copies are sent. The test exists because of the sender-trust condition above: a CRM that accepts mail over SMTP and then silently drops an unverified sender would otherwise look like it was working. If the test never arrives, the fix is to allow noreply@intermind.com as a sender in the receiving tool and pick the address again.

The copy the CRM receives is the same email the participants get: the summary text plus links to the full recap and transcript. Those links still require signing in as a meeting member — the CRM holds the summary, not a door into the meeting.

When the call was in two languages

A follow-up email after an international call has one extra job: it is often the only written record the prospect will have. Two facts about the recap decide how to handle that.

The emailed recap is a single snapshot in the meeting's source language. The recap page it links to serves the summary in the reader's own language — but that page requires sign-in and meeting membership, so it is the path for your team, not for a prospect who joined once from a link. A prospect who joined without an account receives nothing after the call at all; there is no delivery channel for them.

So the follow-up email you write is the prospect's record. Open the recap in your language, write the "what you heard" block from its takeaways, and send it the same day — the prospect's side of the call was in their language, and the email is where the two sides' understanding is reconciled in writing.

FAQ

How do I follow up after a sales call? The same day, in writing, with four things: what you heard (in the prospect's words), what was decided, the next step with a date, and one ask. Then on a planned schedule — each follow-up adds something new and the sequence ends with a clean exit rather than trailing off.

How do I write a follow-up email after a call? Start from the write-up of the call, not from memory: two or three lines restating the prospect's situation and problem, one line per decision, the next step with its date, and a single request. Keep it readable on a phone; link the deck and recording rather than attaching them. The five templates above cover discovery, demo, silence, "send me information", and a missing decision-maker.

What is the 2-2-2 rule in sales? A rule of thumb for follow-up cadence that circulates among sales teams: follow up two days after the last contact, then two weeks later, then two months later. It is a scheduling principle rather than a measured law — the useful part is that each follow-up is planned when the previous one is sent.

How long should a sales follow-up email be? Short enough to read on a phone without scrolling: a greeting, three or four bullet points, one next step, one ask. Detail lives in linked documents. Length is a symptom of a missing write-up — when you know exactly what was said, the email is short.

Can the call summary be sent automatically? If the call runs in InterMIND, yes: when the session ends, a recap with an overview, key takeaways, action items and open questions is emailed to the registered participants, and it can be corrected on the recap page afterwards. A participant who joined without an account does not receive it — the follow-up email you send is their record.

How does the follow-up get into the CRM without logging it manually? By BCC to the CRM's inbound address. HubSpot, Pipedrive and Zoho each document one: the email is filed on the record of a To/CC recipient the CRM recognizes, provided the sender is one it trusts. In InterMIND, the CRM address goes in the meeting's Recap copy field; the address is confirmed once by a test email opened inside the CRM, and from then on every recap of that meeting is filed on the prospect's record automatically.

Try it

• Start a meeting and copy its link — the recap and the Recap copy field are on the meeting's row.
• See what a recap contains — a worked example of the summary, transcript and history.
• Read the discovery call guide — the call these templates follow up on.
• See the book-a-demo flow — the demo the second template follows up on, and how the write-up reaches the CRM.

Sources: vendor documentation — HubSpot, Log email in your CRM with the BCC or forwarding address; Pipedrive, A guide to Smart Bcc emailing; Zoho CRM, BCC Dropbox. Quoted conditions and limits are as stated on those pages. checked September 2026.