---
name: follow-up-after-sales-call
description: Turns rough sales or discovery call notes into a short follow-up email with a recap in the buyer's words, agreed points, next steps with owners and dates, and open questions. Use it after a sales, discovery or demo call.
---

# Follow-up email after a sales call

## When to use
Use this skill after a sales, discovery or demo call when the user has rough notes and needs a short follow-up email to send the same day. Do not use it for cold outreach, for re-engaging a buyer who has gone quiet, or for writing a proposal. If the user wants a price or terms stated, remind them that a person with authority must approve those before sending.

## What to ask for
If the user has not given an item, ask for it before writing.
- Sender's name and company.
- Buyer's name, role and company.
- Date of the call.
- The rough call notes, including the buyer's own words about their problem and one specific moment from the call.
- What was agreed, who owns each action and the date for each.
- Questions still open on either side, and who should answer each one.
- Tone, length and sign-off preferences, if any.

## Steps
1. Read the notes and separate three things: the buyer's problem, what was agreed, and what is still open. Ignore private comments about the buyer or the sales strategy.
2. Write one line of thanks that mentions a specific moment from the call.
3. Recap the buyer's problem in two to four sentences. Keep their own phrases where the notes have them, and use quotation marks only for exact words from the notes.
4. State what was agreed in plain sentences.
5. List next steps as short lines with the owner, the action and the date. Use only owners and dates the user supplied.
6. List open questions and say who needs to answer each. If the user did not name who answers, write CONFIRM in place of a name. Do not guess.
7. Close with one calm line inviting the buyer to correct anything misunderstood. Do not add urgency, discounts or pressure.
8. Mark every missing or unclear date, owner or detail as CONFIRM in the email, and list each one after it.

## Output format
Give three parts in this order.
1. A subject line and one alternative.
2. The email in plain text, under 200 words unless the user asks for more.
3. A short list headed Assumptions and gaps.

Use this layout for the email body.

```text
Hi [buyer first name],

Thank you for your time on [day]. [One specific line from the call.]

What I heard: [problem recap in the buyer's words].

What we agreed: [plain sentences].

Next steps:
- [Owner]: [action] by [date]
- [Owner]: [action] by [date]

Still open:
- [question] ([who answers, or CONFIRM])

Please correct anything I have misunderstood.

[Sender name]
```

## Quality check
Before giving the result, check each point.
- Every name, date, amount and owner matches the user's notes.
- Nothing is invented: no prices, features, promises, quotes or owners.
- Any quoted phrase appears in the notes.
- Every next step and open question has an owner from the notes, or is marked CONFIRM.
- No private or strategic comments from the notes appear in the email.
- The tone is calm, with no urgency or pressure, and the email reads easily on a phone.

## Watch-outs
- Do not add commitments the buyer did not agree to, even to sound helpful.
- Do not fill gaps with guesses, including who owns an action or answers a question. Mark them and ask the user.
- Do not state prices, discounts, delivery dates or special terms unless the user supplied them as agreed.
- Remind the user to read the draft against their notes before sending.
- Ask the user to leave out personal data the email does not need, and to use their company's approved AI workspace. Data protection rules such as India's DPDP Act or GDPR may apply, so the user should follow their own company policy.
