Post-call follow-up email from rough sales call notes
Turns messy notes from a sales or client call into a follow-up email that recaps what you heard, lists commitments on both sides and proposes one next step, plus a private list of your open items.
Prompt in Sales by AISkillHub Library
What it does
The follow-up email after a call is where deals quietly stall: commitments get lost, the recap is vague, or the rep promises something nobody confirmed. This prompt turns your raw notes into a clear email that the buyer can forward internally, and a separate private list of what you personally committed to.
**Use it when** you have just finished a discovery, demo or check-in call and have notes in any state: bullet fragments, a transcript excerpt, or shorthand.
**What you get** - A specific subject line. - A recap in the buyer's words of their situation and priorities, framed as "here's what I heard, correct me if wrong". - Commitments on both sides, with owners, and dates where the notes include them. - One proposed next step with a concrete time frame. - A private "open items" list for you, including anything you said you would check.
**What it will not do** - It will not confirm capabilities, integrations, prices or timelines that your notes show as unconfirmed. "I'll check if we support X" stays a check, not a yes. - It will not add dates that were not agreed. It leaves `[needs: date]` markers for you to fill. - It will not include internal notes (like "seems price sensitive") in the customer-facing email.
**Example** From notes on a call with an operations head and an IT lead (14 warehouses, mis-pick problems, SSO and WMS questions, a 20 Nov budget review), the prompt produces a recap email with three bullet points, three commitments, one meeting request and two open items. The full example is in the second file.
How to use it
## How to use
1. Open `prompts/post-call-follow-up-email.md` and copy everything below the title line. 2. Replace each `{{variable}}` with your own content. Paste long material (notes, transcripts, tables) directly in place of the variable; keep the surrounding tags so the model can tell inputs apart. 3. Start a new chat in ChatGPT, Claude or Gemini and paste the filled prompt as your first message. 4. Read the output against the quality checks at the end of the prompt before you use or send it.
## Variables
- `{{call_notes}}`: your raw notes or transcript excerpt from the call. - `{{our_company}}`: your company or product name. - `{{sender}}`: your name and role. - `{{attachments}}`: anything you are attaching, or `none`. - `{{tone}}`: e.g. `friendly, concise`, `formal`.
If you do not have a value for an optional variable, write `none` rather than deleting it, so the prompt still reads correctly.
## Example
`prompts/post-call-follow-up-email.example.md` shows the prompt with every variable filled and a trimmed sample of the output, so you can see the expected shape before you run it on real material.
## Reusing it
To reuse it often, save the prompt (with the variables left in) as the instructions of a Claude Project, a custom GPT or a Gemini Gem, then paste only the inputs in each new chat.
Files
Save each file at the path shown, relative to your project root.