# Follow-up and email: prompt pack

Prompts for after the call: recap emails, CRM notes, tasks and nudges for deals that went quiet. Nothing here sends an email.

Online: https://mcpforgtm.com/toolkit/prompts/follow-up-and-email

For: AEs, SDRs

## How to use a prompt

1. Connect the tools the prompt needs. Each one links to its listing and setup steps.
2. Copy the prompt into Claude, ChatGPT or another assistant, and replace the text in [brackets].
3. Read what comes back. Before you say yes to a change, go through the points under "Before you approve".

## Recap email after a call (Read only)

A short recap with next steps, ready to edit in the chat.

Tools it needs:

- A call recorder with transcripts (any one of): Salesloft, uses "conversations (search, details, recording links)" (https://mcpforgtm.com/tools/salesloft); Granola, uses "meeting transcripts" (https://mcpforgtm.com/tools/granola); Fireflies, uses "transcript search & retrieval" (https://mcpforgtm.com/tools/fireflies); Outreach, uses "Kaia meeting search and transcripts" (https://mcpforgtm.com/tools/outreach)

```text
Use my call recorder to find my most recent call with [company name].

Write a follow-up email to [attendee names]: a two-line thank you and summary, the decisions we made, next steps with owners and dates, and anything I promised to send. Describe their goals in their own words. Keep it under 150 words.

Show me the email here. Don't send or save it. Read only: don't change anything in my tools.
```

Full recipe: Post-call follow-up: recap email, next steps and a CRM update (https://mcpforgtm.com/recipes/post-call-follow-up)

## Save the recap as a Gmail draft (Changes data)

Put the recap in your drafts folder so you can review and send it yourself.

Tools it needs:

- Gmail, to save a draft: Gmail, uses "creates email drafts" (https://mcpforgtm.com/tools/gmail)

```text
Save the recap email we just wrote as a draft in Gmail. To: [email addresses]. Subject: [subject].

Show me the recipients, subject and full text. Show me exactly what you'll change first, and wait for my yes before you change anything. Only create a draft. I'll send it myself.
```

Before you approve: Check the recipients and that every fact and date in the email matches the call. The tool only creates drafts, so nothing goes out until you send it.

Full recipe: Post-call follow-up: recap email, next steps and a CRM update (https://mcpforgtm.com/recipes/post-call-follow-up)

## Emails waiting on my reply (Read only)

Find prospect emails you haven't answered yet.

Tools it needs:

- Your email: Gmail, uses "search_threads" (https://mcpforgtm.com/tools/gmail)
- Your CRM (any one of): HubSpot, uses "CRM search (read only)" (https://mcpforgtm.com/tools/hubspot); Salesforce, uses "SOQL query (soqlQuery) and SOSL search (find)" (https://mcpforgtm.com/tools/salesforce); Pipedrive, uses "persons (contacts)", "deals" (https://mcpforgtm.com/tools/pipedrive); Attio, uses "records search (read only)" (https://mcpforgtm.com/tools/attio)

```text
Find emails from the last [7] days from people outside [my company domain] where I haven't replied yet.

Match each sender to an open deal in my CRM if there is one. Show a table with these columns: date, sender, company, deal and stage, and a one-line summary of what they asked for. Put deals closing soonest at the top. Read only: don't change anything in my tools.
```

Full recipe: Inbox triage: prospect emails waiting on you, matched to open deals with nudge drafts (https://mcpforgtm.com/recipes/inbox-triage-nudges)

## A nudge for a deal that went quiet (Read only)

A short, useful check-in instead of "just following up".

Tools it needs:

- Your CRM (any one of): HubSpot, uses "CRM search (read only)" (https://mcpforgtm.com/tools/hubspot); Salesforce, uses "SOQL query (soqlQuery) and SOSL search (find)" (https://mcpforgtm.com/tools/salesforce); Pipedrive, uses "deals", "activities", "notes" (https://mcpforgtm.com/tools/pipedrive); Attio, uses "records search (read only)" (https://mcpforgtm.com/tools/attio)

```text
Look at the deal [deal name] in my CRM: the last few activities, the notes and the next step.

Write three short check-in emails (under 80 words each) for [contact name]. Each one should give a reason to reply that comes from the record, like an open question or something we offered to send. Don't use "just following up" or "circling back".

Show me the drafts here. Read only: don't change anything in my tools.
```

## Log the call in my CRM (Changes data)

A clean call note on the right record.

Tools it needs:

- A call recorder with transcripts (any one of): Salesloft, uses "conversations (search, details, recording links)" (https://mcpforgtm.com/tools/salesloft); Granola, uses "meeting transcripts" (https://mcpforgtm.com/tools/granola); Fireflies, uses "transcript search & retrieval" (https://mcpforgtm.com/tools/fireflies); Outreach, uses "Kaia meeting search and transcripts" (https://mcpforgtm.com/tools/outreach)
- Your CRM, to save a note (any one of): HubSpot, uses "logs activities (calls, emails, meetings, notes, tasks)" (https://mcpforgtm.com/tools/hubspot); Salesforce, uses "creates, updates and deletes Salesforce records (platform/sobject-all server)" (https://mcpforgtm.com/tools/salesforce); Pipedrive, uses "creates and updates notes" (https://mcpforgtm.com/tools/pipedrive); Attio, uses "creates notes and updates note content" (https://mcpforgtm.com/tools/attio)

```text
Find my most recent call with [company name] in my call recorder. Write a call note with: attendees, what they need, objections, decisions and next steps with dates.

Then save it as a note on the deal [deal name] in my CRM. Show me the record and the note text. Don't delete any records. Show me exactly what you'll change first, and wait for my yes before you change anything.
```

Before you approve: Check that it's the right deal and that the note says only what was said on the call. Watch for anything private, like pricing promises, that shouldn't be on a shared record.

Full recipe: Post-call follow-up: recap email, next steps and a CRM update (https://mcpforgtm.com/recipes/post-call-follow-up)

## Turn next steps into CRM tasks (Changes data)

Each promise from the call becomes a task with a due date.

Tools it needs:

- Your CRM, to create tasks (any one of): HubSpot, uses "logs activities (calls, emails, meetings, notes, tasks)" (https://mcpforgtm.com/tools/hubspot); Salesforce, uses "creates, updates and deletes Salesforce records (platform/sobject-all server)" (https://mcpforgtm.com/tools/salesforce); Pipedrive, uses "creates and updates activities" (https://mcpforgtm.com/tools/pipedrive); Attio, uses "creates, updates and deletes tasks" (https://mcpforgtm.com/tools/attio)

```text
From the next steps we just listed, create a task in my CRM for each one I own. Give each task a clear title, a due date and the related deal [deal name].

Show me the tasks in a table with the title, due date and deal. Don't delete any records. Show me exactly what you'll change first, and wait for my yes before you change anything.
```

Before you approve: Check the due dates, the owner (you) and the related record. Skip tasks that belong to the buyer.

## Add a scheduling link to a follow-up (Changes data)

A one-time booking link for the next meeting.

Tools it needs:

- Calendly, to make a link: Calendly, uses "creates single-use scheduling links" (https://mcpforgtm.com/tools/calendly)

```text
Create a single-use Calendly scheduling link for my event type [event type name] so [contact name] can book our next meeting.

Tell me which event type and duration you'll use. Show me exactly what you'll change first, and wait for my yes before you change anything. Then add the link to the follow-up email we wrote.
```

Before you approve: Check the event type and its length.

Full recipe: Book meetings from replies (https://mcpforgtm.com/recipes/book-meetings-from-replies)

## Win back a lost deal (Read only)

A reason to get back in touch with an account you lost.

Tools it needs:

- Your CRM (any one of): HubSpot, uses "CRM search (read only)" (https://mcpforgtm.com/tools/hubspot); Salesforce, uses "SOQL query (soqlQuery) and SOSL search (find)" (https://mcpforgtm.com/tools/salesforce); Pipedrive, uses "deals", "persons (contacts)" (https://mcpforgtm.com/tools/pipedrive); Attio, uses "records search (read only)" (https://mcpforgtm.com/tools/attio)
- Web research: Perplexity, uses "perplexity_search" (https://mcpforgtm.com/tools/perplexity)

```text
Look up the closed-lost deal at [company name] in my CRM: the lost reason, the close date and who we spoke with.

Search the web for what has changed at the company since then (new leaders, funding, growth, news), with sources. If something addresses the reason we lost, write a short email to [contact name] that names it. If nothing changed, say so. Read only: don't change anything in my tools.
```

Full recipe: Closed-lost deal revival: rank last year's lost deals by what changed since (https://mcpforgtm.com/recipes/closed-lost-revival)

_What each tool can do comes from its StackMCP listing, which links the source for each fact. Vendors change their servers, so if a step doesn't work, check the listing. The prompts are starting points: edit them to fit how your team works._