ChatGPT prompts for sales follow-up, tested on a real call

Updated October 29, 2026.

ChatGPT prompts for sales follow-up: the short version

• The 7 prompts below write B2B sales follow-ups: the recap after a discovery call, the email after a demo, a note your champion forwards to the budget owner, the email that sends what you promised, versions per stakeholder, and follow-ups when the buyer goes quiet.
• They work the same in ChatGPT and in Claude: paste the prompt, add the call transcript or your notes, review the draft, send it from your own inbox.
• Five prompts run on the call transcript; two run on the transcript plus your email thread.
• For prompts on discovery, MEDDPICC and deal risk, see 10 ChatGPT prompts for sales.

Write the sales follow-up from the call transcript: the details that move a deal (the buyer's words, the dates, the owners) are in the call, and the people who decide were often not on it.

On our own sales calls, 35% of buyer teams named someone who was not on the call and needs to see the material: a CFO, a CRO, legal, procurement (Claap call data, April to October 2026).

That changes who the follow-up is for. The person on the call remembers the conversation. The CFO reading the forward only has your email.

A follow-up written from memory, or from three lines of notes, cannot carry what that reader needs. We ran the same follow-up prompt on notes and on a real transcript to show the gap.

The 7 follow-up prompts at a glance

What the call transcript changes: one follow-up prompt, two drafts

We took one real discovery and demo call (names and company replaced) and ran prompt 1 twice in GPT-5.5, an OpenAI model, through the API. Run 1 got the kind of notes a rep writes after a call. Run 2 got the transcript. Same prompt both times.

• From the notes, the model did the honest thing: three [MISSING] tags, no date and no owner, as measured in our test on October 29, 2026. That is a better result than an invented recap, and it is still an email you cannot send.
• From the transcript, the draft opened on the buyer's own sentence about volume limits, listed 7 next steps with an owner or a date, and answered 2 questions asked on the call (our test on October 29, 2026).
• Its [MISSING] tags became useful. They pointed at real gaps: the year of the dates and the rest of the trial users. Those are two things to confirm, where Run 1 asked you to rewrite the whole email.

We also ran prompt 3 on the same transcript. The note for the budget owner came back in 91 words, in the buyer's voice, with one buyer quote and one tag: "[MISSING: cost]" (our test on October 29, 2026). That tag is exactly the question the CFO will ask.

Buyers say it themselves on calls:

• "I need to talk to … C level CRO, CEO and CFO. So maybe, if you could, could you turn it into like a formal offer?" (Sales leader, B2B software company)
• "This is going to probably be a question that is going to be asked from the CFO." (Sales operations lead, software scale-up)
• "Before the end of the month, I need to present a solution to my CRO and to procurement, so it gets approved." (Sales operations lead, cybersecurity software company, translated from French)

The asks themselves were concrete. In the same calls, 33% of buyer teams asked for at least one item after the call: trial access came first at 15%, then pricing or a proposal, security documents and a meeting with another stakeholder at 10% each (Claap call data, same period).

These figures come from Claap's own sales calls and are floors: a buyer who asked without saying it plainly counts as no.

How to get a follow-up draft you can send

• Put the reader in the prompt. "The buyers who were on the call" and "a CFO who was not" need different emails. Say which one you want, because the model writes for whoever you name.
• Ban the opener. "Thanks for your time" tells the buyer nothing. Ask the model to open with the problem they described, in their words. It is the line that shows you listened.
• Ask for owners and dates. A next step without an owner is a wish. Use "with owner and date" in every recap prompt, and the [MISSING] rule for anything the call left open.
• Keep it under 150 words. Put the detail in an attachment or a link to the recording.
• Send it yourself. Review every fact, fix the tone, and send from your own inbox. A model writes the draft; you own what the buyer reads.

Follow-up prompts that run on the call transcript

1. Recap email after a discovery call

This is the prompt we tested. Send the email the same day, while the buyer still remembers the call.

You are an Account Executive writing the follow-up email after
today's call. Below is the transcript.

Write the email to the buyers who were on the call. Rules:
- Open with the one problem they described in their own words, not
  with "thanks for your time".
- Recap only what was agreed: next steps with owners and dates, and
  anything we promised to send.
- If they asked a question we did not fully answer, answer it or say
  when we will.
- Under 150 words, plain text, no buzzwords, one clear ask at the end.
- Use only facts from the transcript. If something is missing, write
  [MISSING: what] instead of inventing it.

Transcript:
"""
[paste the call transcript]
"""

What to expect: a short email built on the buyer's sentence, a dated list of next steps and one or two [MISSING] tags. Fill the tags before you send.

2. Post-demo follow-up tied to their reactions

Use it after a demo. Buyers forget features; they remember the moment something solved their problem.

Below is the transcript of a product demo. Write the follow-up email
to the buyers who attended.

- Pick the 2 or 3 moments where a buyer reacted (a question, "that's
  exactly what we need", a concern). Quote each reaction briefly.
- For each one, one sentence on what it means for their problem.
- List any concern raised during the demo and how we answered it, or
  say we will come back with an answer and when.
- End with the next step agreed on the call.
- Under 170 words. Only facts from the transcript; write
  [MISSING: what] for anything not said.

Transcript:
"""
[paste the demo transcript]
"""

What to expect: an email about their reactions, with a feature tour left out. If the model finds no reaction to quote, the demo probably was a monologue, and that is worth knowing too.

3. Note for the decision-maker who was not on the call

Use it when your contact says "I need to show this to my boss". The note is written for them to forward, in their voice.

Write a short note my champion can forward to the person who signs
off on the budget and was not on today's call. Below is the
transcript.

Rules:
- Written from the champion's point of view, in their words where
  possible ("we", "our team").
- Three parts: the problem we have today (with one line the buyer side
  said), what we tested and what changes, what we need to decide and
  by when.
- Under 120 words. No product jargon, no adjectives like "powerful".
- Only facts from the transcript. Write [MISSING: what] where a fact is
  missing, such as the cost.

Transcript:
"""
[paste the call transcript]
"""

What to expect: three short paragraphs and a [MISSING: cost] tag if price was not discussed. Send the note to your champion with the missing facts filled in, so they forward a finished page.

4. "What you asked for" email

Use it when the call ended with requests: a proposal, a security document, a trial, an answer you did not have.

Below is the transcript of a sales call. List everything the buyer
side asked us to send or answer, and everything we promised.

For each item: what it is, who asked, and the exact words used.

Then write a short email that sends or answers each item in a numbered
list, with [ATTACH: document] where a file goes and [MISSING: answer]
where we still need to find the answer. Under 150 words.

Transcript:
"""
[paste the call transcript]
"""

What to expect: a checklist first, then the email. The checklist is the useful part: compare it with what you remember promising.

5. One follow-up per stakeholder

Use it when several people joined, each with a different stake: a sales director who will use the tool, a finance lead who pays, an IT lead who approves.

Below is the transcript of a call with several people on the buyer
side. For each buyer-side person who spoke:

1. Their role, as far as the transcript says.
2. What they cared about, with one short quote.
3. A follow-up email to them only, under 100 words, about what they
   care about, with the next step that concerns them.

Use only facts from the transcript. Write [MISSING: what] where needed.

Transcript:
"""
[paste the call transcript]
"""

What to expect: two to four short emails that read differently. If two come out the same, send one email to both.

Follow-ups when the buyer goes quiet

6. No-reply follow-up built on what they said

Use it after three to five business days of silence. "Just checking in" adds nothing; something the buyer said on the call gives them a reason to answer.

The buyer has not replied to my last email. Below are the transcript
of our last call and my last email.

Write a follow-up under 80 words that:
- Does not repeat my last email or ask "did you see my email?".
- Picks one thing the buyer said on the call (quote it) and adds one
  useful thing about it: a question, a short example, a resource.
- Ends with one easy question they can answer in a line.

Call transcript:
"""
[paste the call transcript]
"""
My last email:
"""
[paste your last email]
"""

What to expect: a short email that sounds like you thought about their problem since the call. If the quote it picks is minor, ask it to pick the problem the buyer spent the most time on.

7. Restart a stalled deal

Use it when a deal has gone quiet for weeks. The goal is a small next step, so the email offers one.

This deal has stalled. Below are the transcript of the last call and
the email thread since.

1. In 3 bullets: what the buyer wanted, what was agreed, where it
   stopped.
2. Write an email under 100 words that recalls their goal in their
   words, names one thing that changed since (on our side or theirs,
   from the thread only), and offers one small next step that takes
   them 15 minutes or less.
No guilt, no "circling back".

Last call transcript:
"""
[paste the call transcript]
"""
Email thread:
"""
[paste the thread]
"""

What to expect: a three-bullet diagnosis you can reuse in your pipeline review, then a short email. If the diagnosis shows the deal stopped on a missing decision-maker, prompt 3 is the better email.

Before you send: the checks a model will not do for you

• Read every quote and date against the call. A model repeats the transcript's errors, and dates often come without the year, as our test showed.
• Check what may leave the building. A transcript holds personal data and deal details. Paste it only into a ChatGPT or Claude account your company approved.
• Match the tone to the buyer. The draft follows your prompt. A formal buyer and a founder who swore on the call need different openers.

When follow-ups are a daily job, pasting transcripts one by one stops scaling. A quick note: Claap is our product. In Claap, the follow-up email is drafted from the call with a discovery, demo or proposal template, in the rep's own style, and the rep sends it from their own email client. To ask your own question about one meeting, such as "what did we promise to send?", ClaapAgent answers with links to the moment in the call.

When these prompts are the wrong tool

These prompts are wrong if the call was not recorded: from notes alone you get the generic draft shown above, and a short email you write yourself is better. They also do not fit a first cold email, because there is no call to draw from yet; start from what you know about the account.

Skip prompt 5 when only one person spoke on the buyer side. And avoid sending any draft untouched when the deal is large: a wrong figure in a follow-up to a CFO costs more than the ten minutes you saved.

Takeaways

• Write the follow-up from the transcript. Same prompt, same model: notes gave three blanks, the call gave dates, owners and the buyer's words.
• Write for the person who was not on the call. More than a third of buyer teams on our calls named one.
• Open on their problem, list owners and dates, keep it under 150 words.
• Use the [MISSING] rule and fill every tag before sending.
• Send from your own inbox, after reading every fact against the call.

For a fill-in-the-blanks version, see our follow-up email template.