Sales call follow-up email: 12 templates, and the one drafted from the call
Every guide ranking for this search gives you templates with square brackets in them and tells you to fill the brackets from memory. This page gives you templates too, because that is what you came for, and they are first. Then it shows the part the guides skip: the follow-up written from what was actually said on the call, with the deal's next step and its date, drafted by an agent and sent by you. Tulina sells that agent, and its section is marked. The templates owe it nothing.
Everything quoted from another site below was read on 26 October 2026. No reply rate is quoted anywhere on this page, because none of the guides we read names the dataset behind theirs.
What is a good sales follow-up message?
A good sales follow-up message quotes one thing the buyer said, confirms what each side agreed to do, and asks for exactly one thing with a date attached. It is short enough to read on a phone between two meetings, and it is a reply on the thread the buyer already has, not a new subject. The twelve templates below follow that rule, one per moment. Each has a subject line, placeholders in [square brackets], and two lines on why it is shaped the way it is.
| Moment | Template | The one ask |
|---|---|---|
| Discovery call, the buyer named a need | 1 | Who else should see the outline |
| Discovery call, no next step was set | 2 | Accept a proposed date |
| Demo | 3 | A date with the person they named |
| Demo, buyer needs internal buy-in | 4 | Pick one of two slots for their team |
| Pricing call | 5 | Send the thing you need by a day |
| Several people on the call | 6 | Confirm the minutes |
| Buyer asked for something the product does not do | 7 | Keep the agreed review |
| Cold call that turned into a conversation | 8 | Take or decline one slot |
| Voicemail | 9 | Reply with a time |
| No-show | 10 | Pick one of three slots |
| No reply after three working days | 11 | Answer one question |
| The last email | 12 | Nothing |
1. After a discovery call where the buyer named a need
Use it when the buyer said, in their own words, what is broken and by when it has to be fixed.
Subject: [The need, in three words] and the next step
Hi [Name],
Thanks for today. You said the weekly forecast is "[rebuilt by hand
every Thursday]" and that it has to be trusted by [date].
I will send the two-page outline by [day]. Who else on your side should
see it before we talk on [day, time]?
[Your name]
The quoted line proves you listened, which no adjective can. The one question doubles as the stakeholder map: whoever they name is who the deal has to convince.
2. After a discovery call with no clear next step
Use it when the call ended on "let's stay in touch". Propose the date instead of asking for one.
Subject: A date for the next conversation
Hi [Name],
We did not fix a next step today, so here is one: [day] at [time], to
go through [the open question you raised], with [the colleague you
mentioned] if they can make it.
If another slot is better, tell me and I will move it.
[Your name]
A proposed slot gets a yes or a counter-offer; "when would suit you" gets silence. Naming their open question makes the meeting about their problem, not your product.
3. After a demo
Use it when the buyer asked questions during the demo. The follow-up is the list of answers, not a tour of what they saw.
Subject: What you saw, and what you asked for
Hi [Name],
Two things from the demo. You asked whether [the thing they asked]:
yes, and I will send [the short recording / the two settings] by
[day]. You also said "[their words about the pain]", which is what
[feature] was built for.
Does [day] work for the follow-up with [the team or person they named]?
[Your name]
The buyer remembers their own questions better than your slides, so answering them is the recap. One dated ask, aimed at the person they said has to be in the room.
4. After a demo, for the buyer to forward
Use it when the buyer has to sell this internally. Write it for the reader who was not on the call.
Subject: Summary for [colleague's name or team]
Hi [Name],
A version you can forward:
- Problem: [the problem, in their words]
- What we showed: [one line]
- What it would change: [the outcome they named], measured by [the
metric they named]
- Open question: [the one they said their team would ask]
I can join a 20-minute call with [the team] on [day] or [day]. Which is
easier?
[Your name]
A buyer forwards an email that already speaks their language and rewrites one that speaks yours. Two slots, not an open question, so the answer is one word.
5. After a pricing call
Use it when a price, a scope or a term was said out loud. Put it in writing the same day.
Subject: The [plan name] option, as discussed
Hi [Name],
As agreed: [plan] at [price] for [scope], [term], starting [date]. The
one thing you asked me to check, [the question], is [the answer].
If you want this live by [the date they named], I need [the thing you
need from them] by [day]. Is that doable?
[Your name]
The price restated in writing is the record both sides will work from. The deadline is tied to a date the buyer chose, so the urgency is theirs rather than yours.
6. After a call with several people, where each side took an action
Use it when more than one person was on the call and more than one thing was agreed. It reads as the minutes.
Subject: Who does what, by when
Hi [Name], hi [Name],
To confirm what we agreed:
- You share the current process doc by [day].
- We send the pricing outline by [day].
- [Name] asked about [the open question]; I come back on it by [day].
Next call: [day, time]. I have sent the invite.
[Your name]
Three lines, each with an owner and a day, and nothing to decide. A buyer forwards minutes to a colleague; nobody forwards a pitch.
7. After a call where the buyer asked for something the product does not do
Use it when they asked for a capability you do not have. Say so, show where the request went, and keep it separate from the deal's next step.
Subject: Your request for [the capability]
Hi [Name],
You asked for "[their words]". It does not exist today. I have passed it
to the product team with your account and the reason attached, and I
will tell you what comes back by [day].
In the meantime the review we agreed for [date] still stands; nothing
you need from it depends on that feature.
[Your name]
A plain no, dated, beats a vague maybe that comes due on the next call. The last sentence keeps the missing feature from becoming the reason the deal stalls.
8. After a cold call that turned into a conversation
Use it the same morning, after a phone call the buyer did not expect but stayed on.
Subject: [Topic] from our call this morning
Hi [Name],
Thanks for picking up. You said [the one thing they said]. Here is the
[one-pager / the two slides] that cover it, nothing more.
If it is worth 20 minutes, [day] at [time] is open on my side. If not,
no reply needed.
[Your name]
One attachment, one slot, and explicit permission to not answer. The permission is what makes the yes mean something.
9. After leaving a voicemail
Use it within the minute, so the email says what the voicemail said.
Subject: Left you a voicemail about [topic]
Hi [Name],
I left a message a minute ago, so you have it in writing too: [the one
reason you called, in one line].
Reply with a time that suits you, or I will try again on [day] around
[time].
[Your name]
The email is the part they can read without playing anything back. Dating the next attempt makes the second call expected instead of intrusive.
10. After a no-show
Use it the same hour. No apology demanded, none offered.
Subject: Missed you at [time]. Three other slots
Hi [Name],
We had [time] today and did not connect. [Day at time], [day at time]
or [day at time]: reply with one and I will send the invite.
If [the problem you discussed] is no longer a priority, say so and I
will close this out.
[Your name]
Three slots turn rescheduling into a one-word reply. The second paragraph gives them the exit, which is how you learn whether the deal is alive.
11. After no response, three working days later
Use it once the same-day email has gone unanswered. One question, no recap, no "just".
Subject: Re: [the original subject]
Hi [Name],
Have you given up on [the project, in their words]?
[Your name]
Reps in the r/sales thread that ranks first for this search report this line, borrowed from the negotiator Chris Voss, gets answers where a recap does not: it is easy to answer with one word, and "no" is the word people like to say. It stays on the thread, so the context is one scroll up. One rep in the same thread warns it reads as rude in the UK market; if that is where you sell, template 12's softer close does the same job.
12. The last email
Use it after the third unanswered email, or on the day the buyer's own deadline has passed with no word.
Subject: Closing this out
Hi [Name],
I have not heard back since [date], so I will close this on my side and
stop writing.
If [the problem] comes back on the list, reply to this thread and we
pick up where we left off: [the one-line state of the deal].
[Your name]
It states the date, which is the only fact the buyer may not have noticed. The last line gives the thread a resume point, so a reply in three months needs no re-introduction.
How to write a follow-up email after a sales call?
Write a follow-up email after a sales call in four parts: a subject that names the topic, a first line that quotes one thing the buyer said, one ask, and a next step with a date on it. Then send it the same day, as a reply on the thread the call was booked from. The longest of the twelve templates above is 64 words, the shortest 14, and none has a second ask.
The subject line does one job: it tells the buyer, in the inbox list, whether this email contains something or is a nudge. The lines below are drawn from the twelve templates and from what the r/sales thread says gets ignored.
| Subject line | What the buyer reads into it | Use it after |
|---|---|---|
| [Their need] and the next step | There is a step, and it is yours to take | Any call that ended with an action on your side |
| What you saw, and what you asked for | The answers are inside | A demo, or any call with open questions |
| Who does what, by when | Minutes, not a pitch | A call with several people |
| Summary for [Name] | Made to forward | A buyer who has to sell this internally |
| The [plan] option, as discussed | The number is in writing | A pricing call |
| Missed you at [time]. Three other slots | Nothing to apologise for, pick one | A no-show |
| Re: [the original subject] | Same thread, nothing new to open | Any follow-up to a follow-up |
| Closing this out | The last one | Three unanswered emails |
| Just following up, Touching base, Checking in | No content, low effort | Never; every rep in the thread says so |
The first line is where the templates differ from the guides. "Great speaking with you today" tells the buyer nothing they did not know. "You said the forecast is rebuilt by hand every Thursday" tells them you were listening, and it is the sentence they will quote when they forward the email to their manager. Quote, do not paraphrase: the buyer's phrasing is the one their colleagues will recognise.
The one ask is a single question whose answer is one word or one date. Two asks get the easier one answered and the important one forgotten. The dated next step is the part reps most often leave out, and it is the part that turns a thank-you note into a deal moving: "by Thursday", "on the 12th at 10", "before your board meeting". If the call set no date, the follow-up proposes one, as template 2 does.
When should you send a follow-up email after a sales call?
Send the first follow-up the same day, before the next call starts if you can, because that is when the buyer's words and the agreed date are still true and still in your notes. After that, the sequence is short: one question three working days later if nothing came back, one email with something new in it a week later, and a closing email after the third silence or once the buyer's own deadline has passed.
| When | What to send | What not to send |
|---|---|---|
| The same day | The recap with the quoted line and the dated next step (templates 1 to 10) | A thank-you with no next step |
| Three working days with no reply | One question, on the thread (template 11) | The same recap again |
| A week with no reply | Something new: the answer to a question they asked, the colleague's availability, the date their deadline implies | "Any update?" |
| Three unanswered emails, or the day after their own deadline | The closing email (template 12) | A fourth nudge |
| The day after a date the buyer gave ("after the board on the 12th") | The recap of what that date was for, and the next date | Anything on day 3 or day 7 that ignores the date they gave |
The last row of the table is the one the cadence guides get wrong. The guides ranking for this search disagree on the exact days (Crono's, updated July 2026, says day 0, day 2 to 3, day 5 to 7 and day 10 to 14), and the shape is the same in the ones we read: one the same day, then spaced out, then stop. A fixed cadence is the fallback for a buyer who gave you nothing to anchor on. When the buyer said "I will know after the board meeting on the 12th", the next follow-up is on the 13th, and a message on day 3 tells them you were not listening.
What is the 3-3-3 rule in sales?
There is no single 3-3-3 rule in sales: the pages ranking for the question, read on 26 October 2026, give at least three different ones. PuppyDog's answer page says three seconds to grab attention, three minutes to build interest and three touchpoints; two LinkedIn posts ranking beside it make the third three "follow up within three days". Linkbreakers, in December 2025, says three calls, three emails and three social touches over three weeks. Crono's guide, in July 2026, says three emails three days apart over three weeks, then a closing note.
What the three versions share is the only part worth keeping: a bounded number of attempts, spaced out, with an end. Pick the version your team will keep to. In all three countings, the email after a sales call is the first attempt, and it is the one that should carry the quoted line and the date, because the later ones have nothing to refer back to without it.
How do I politely send a follow-up email?
Politely means short, specific and with an exit: one sentence on why you are writing, one question, and a line that makes "no" an acceptable answer. The reps in the r/sales thread that ranks first for this search agree on four rules, and their reasoning is better than most guides'.
- Drop "just". "Just following up" makes the email small before the buyer has read it; "Following up on the outline" does not. One commenter removed the word from every email and call.
- Do not apologise for writing. "Sorry to chase" and "I may have dropped the ball" read as incompetence. Frame the follow-up as planned: "I had a note on my calendar to connect with you today."
- Ask one thing, and make it answerable in a word. "Have you given up on the project?" and "Have you gone in a different direction?" both get replies because they are easy to answer, and because they give the buyer permission to say the uncomfortable thing.
- Give them the out. "If this is no longer a priority, say so and I will close this out" is the thread's version, and the answer, either way, is information a third recap would not get you.
A polite follow-up on a request you are waiting for, for the related search that asks for one:
Subject: Re: [the request]
Hi [Name],
I had a note to come back to you on [the request] today. Is [day]
still realistic on your side, or should I plan for [a later day]?
[Your name]
Planned, specific, and the buyer gets to choose between two dates instead of being asked for one.
What gets you in trouble
These are the failures the top guides describe and the ones they do not, from reading twelve of our own call records for the section below.
- A template that reads as one. A bracket left in, "[Company]" in the subject, or a recap so generic it could follow any call. The buyer can tell, and the email says the opposite of what it is for.
- Recapping the whole call. The buyer was there. Two sentences on what matters to the deal, then the ask.
- Two asks. The easier one gets answered. If you need a date and a document, ask for the date; the document goes in the next email.
- Writing it from memory the next morning. The wrong day, the colleague's name misspelt, the deadline rounded. The buyer notices every one. The fix is the call record, not better memory.
- Letting an assistant draft it from the summary alone. Meeting tools summarise in their own words. In the twelve call records we read on 26 October 2026, two of twelve summaries held a verbatim line from the other side; the rest paraphrase. A paraphrase in quotation marks is a misquote with your name on it. Quote from the transcript, or do not use quotation marks.
- Quoting a reply rate. The guides on this search lean on them: "significantly higher reply rates", "correlate strongly with sales success", or a percentage with no source under it. None we read names the sample, the industry or the year. Ignore them, including any you would be tempted to put in your own deck.
- Sending from a recording nobody agreed to. If the draft comes from a call recording, the recording has to have been consented to where you and the buyer sit. Check your tool's consent setting and your own jurisdiction's rule before the recorder goes on, not after.
- Letting anything send itself. The agent in the next section drafts. A person reads the draft and sends it. An email that leaves with the wrong price or the wrong name cannot be unsent, and the minute saved is not worth it.
How do you draft the follow-up email from the call with Claude or ChatGPT?
With Tulina, Claude or ChatGPT reads the call's notes and transcript, finds the deal the call belongs to, writes the agreed next step and its date on the deal, and leaves the follow-up as a Gmail draft on the existing thread, quoting what the buyer said. A person reads the draft and sends it. What changes is that the email is written from the record while it is fresh, and the CRM is updated in the same pass; what a person still decides is whether to send, and what to change first.
Tulina is an agentic RevOps workflow builder: AI agents that run sales and GTM processes on a schedule or a webhook, across the tools a team already uses, with every step and its cost visible. This process reads the call in Granola, the deal in HubSpot, the thread in Gmail, the product requests in Linear and, only when a deal is at risk, posts to Slack. It runs when a call ends. Paste this into Claude or ChatGPT once those are connected:
Draft the follow-up for the sales call that just ended, from the call
record, and update the deal. Never send anything.
1. Find the call: granola_content(op="list_notes", created_after=
<today>), then granola_content(op="get_note", note_id=<the id>) for
the title, attendees and summary. When you quote the buyer, take the
words from granola_content(op="get_transcript", note_id=<the id>),
never from the summary: a summary paraphrases.
2. Find the deal: hubspot_object(op="search", object_type="contacts",
query=<the attendees' email domain>), then the contacts' deals with
hubspot_object(op="get", object_type="contacts", object_id=<id>,
associations=["deals"]). Read the deal with op="get" on "deals",
properties=["dealname","dealstage","amount","closedate","hs_next_step",
"hubspot_owner_id"], resolve_labels=true. If no deal matches, stop
and tell me; do not create one.
3. From the transcript keep only what moves the deal: what they said
they need, in their words; what they pushed back on; what each side
agreed to do and by when; anything they asked the product to do that
it does not do today.
4. Write the next step and its date on the deal with
hubspot_object(op="update", object_type="deals", object_id=<id>,
properties={"hs_next_step": "<action, owner, date>"}), and one note
with op="add_note" carrying the quotes. Do not change dealstage;
tell me whether the call earned the next one.
5. For each product ask, linear_issue(op="search", query=<the substance
of the request>); comment on the match or create one with
op="create" carrying the quote, the account and the deal amount.
6. Find the last email with the attendees: gmail(op="search",
query="from:<their domain> OR to:<their domain> newer_than:60d").
Write the follow-up with gmail(op="draft", reply_to=<that message
id>, body=...): one quoted line, what we agreed and by when, what I
need from them and by when, one ask. Under 100 words. No pitch.
7. Only if something said on the call contradicts the deal record (a
new objection, a moved date, a next step with no date), post one
line to my manager with slack_post_message(channel=<the team
channel>, text=<the deal, the reason, the quote>). Otherwise post
nothing.
8. Report: the call, the deal it matched, each field changed with its
previous value, the issues touched, and the draft's id.
Four of those operations write: the deal's next step and note, the issue, the draft, and the Slack line, which only goes out when a deal is at risk. The draft is the only one a buyer will ever see, and it waits in your drafts until you send it. The process behind the prompt, with every step and the tools it uses:
The process in Tulina
Follow through on sales calls
Trigger · Event
Sales call ended
A finished call opens the run once its notes are ready, so the follow-through starts before the rep is back at a desk.
GranolaClaude runs the rest autonomously
- 1
AI pulls the deal and its history.
HubSpotHubSpot
The deal, its stage, its contacts and the last email thread come back, matched to the call by company as well as by attendee.
GmailGmail
- 2
AI extracts pains, objections and next steps.
GranolaGranola
What the buyer said they need, what they pushed back on and what each side agreed to do come out of the call notes in the buyer's own words.
- 3
AI judges the deal against your playbook.
The call is read against your own qualification criteria, and whatever is still unknown for the stage, or puts the deal at risk, is named.
- 4
AI tests any offer against your pricing rules.
Anything hinted at on the call, a discount, a term, a delivery date, is read against your pricing rules, and whatever is outside them is named with the quote.
- 5
AI updates the deal, logs the next step.
HubSpotHubSpot
The deal takes its next step with a date, a moved close date and new stakeholders, with every previous value reported.
- 6
AI files product asks with their quotes.
LinearLinear
Each capability the buyer asked for lands on its issue with the quote, the account and the deal amount behind it.
- 7
AI drafts the follow-up, flags the risk.
GmailGmail
The follow-up waits as a draft on the thread, and a deal at risk reaches the owner's manager with the quote that says why.
SlackSlack
What we can say from running the reading half of it ourselves, with the denominator. On 26 October 2026 we read, through the Granola connector, the AI summaries of twelve external calls in our own workspace, 20 to 26 October, one per counterpart, taken from the thirty most recent notes with internal meetings and duplicate recordings left out: prospects, customers, partners, investors and one reference check, no call identified here. Twelve of twelve summaries listed at least one next step. Two of twelve gave that step a calendar day; three more gave a loose deadline ("end of week", "next week", "the week of the 4th"); seven gave no date at all. Two of twelve contained a verbatim line from the other side; the other ten paraphrase. We stopped there and created no draft, because the twelve are real people. The three consequences are built into the prompt above: the summary is enough for the facts and the agreed actions, the transcript is where the quotes are, and the date is the thing the draft most often has to add rather than copy.
The process page carries four examples of the draft it leaves, one per kind of call. They are written from each call's own record, so the quotes, dates and names in them are placeholders for what that call held, which is the difference between them and the twelve templates above: a template is what you start from when you have no record, and the draft is what you get when you do.
For the rest of the deal's life after the call, Prepare for a demo from the last call reads the same records before the next meeting, and Keep the CRM current is the write-back side on its own.
Common questions
- How do you write a follow-up email after a phone call?
- The same way as after a video call, only shorter, because a phone call leaves no shared screen to refer to. One line on what they said, the one thing you promised to send, and one slot for the next conversation, sent within the hour so the call is still fresh on both sides. If you left a voicemail instead of speaking, the email repeats the voicemail's one sentence and names the day you will try again.
- How long should a sales call follow-up email be?
- Short enough to read on a phone without scrolling. The twelve templates on this page run from 14 to 64 words, and none has a second ask. A follow-up grows past that when it recaps the whole call, which the buyer attended, or when it adds a pitch, which the call already was.
- How many times should you follow up after a sales call?
- Four emails at most: the recap the same day, one question after three working days of silence, one email with something new a week later, and a closing email. The guides ranking for this search disagree on the exact days and agree on the shape. A date the buyer gave you overrides the cadence: if they said they would know on the 12th, the next email is on the 13th.
- Should the follow-up be a new email or a reply on the thread?
- A reply on the thread the call was booked from. The buyer has the context one scroll up, your email lands in a conversation they already opened, and a reply to a reply later keeps the whole deal in one place. A new subject is for a new topic, such as a proposal, not for the recap.
- Can AI write the sales call follow-up email for me?
- It can draft it from the call record, and that is the only way it should. An agent with the notes and the transcript quotes what the buyer actually said, writes the agreed next step with its date, and leaves the email as a draft on the thread. Drafted from memory or from a summary alone, it paraphrases and misquotes. A person reads the draft and sends it; nothing sends itself.
- What should the follow-up say when the call ended without a next step?
- It proposes one. A day and a time, the open question that meeting would answer, and an invitation to move it. Asking the buyer when would suit them hands them a task; proposing a slot hands them a yes or a counter-offer, and either moves the deal.