A Sales Meeting Follow-Up Prompt That Recaps, Updates the CRM, and Drafts the Email

Ask any rep what happens after a good sales call, and the honest answer is: four tools and twenty minutes. Notes get retyped into a recap. The recap gets mined for action items. Someone updates the Salesforce opportunity — usually at 6pm, usually from memory. Then the follow-up email, written from scratch. A sales meeting follow-up prompt collapses that relay into one pass: paste the notes, get the recap, the dated action items, the CRM update, and the draft email back together.

Most pages that rank for this query stop at the email or the summary. That's the gap. The job isn't "write a nice recap." The job is close the loop before the next meeting starts, without copy-pasting the same facts across four apps.

What the ranking pages miss

The better guides here are genuinely useful and still incomplete. aiforsalesmanagers.com ships five prompts that turn call notes into follow-ups across email, WhatsApp, and LinkedIn, plus a sample output — a solid ~2,800-word walkthrough — but it stops at "attach outputs in CRM" with no field-level write-back and no model-by-model behavior (aiforsalesmanagers.com). Allego's sales guide gives a clean post-call summarization prompt ("Paste Call Transcript. Summarize the key pain points and agreed-upon next steps"), but it's one step in a broader ChatGPT-for-sales overview that pushes toward its own conversation-intelligence demo (allego.com).

So the recap is covered. The email is covered. Nobody locks the four outputs to one contract, and nobody tells you that GPT-4o and Claude behave differently when you ask for a CRM field block. That's what a reusable prompt should own.

What one pass returns

The point of the prompt is a fixed shape from messy input. One run gives you:

• A structured recap — decisions made, open questions, current deal context
• A dated action-item list — every commitment with an owner and a due date
• A CRM update block — stage, next step, close date, and a one-line context note
• A draft follow-up email that references specifics from the call
• A team digest line short enough to drop in Slack

The recap is the source of truth; everything downstream reads from it. Update one fact in the recap and the action items, the CRM block, and the email all inherit it. That single-source design is what stops the four copies of the same call from drifting apart.

Anatomy of the prompt

Four inputs, four artifacts, and the output contract sits last so it survives a long notes paste. Models weight the most recent tokens, so a contract at the top gets buried under whatever you dumped in the middle.

Variables
  {{meeting_notes}}   → raw notes or transcript, however messy
  {{opportunity_id}}  → the Salesforce record to update (or leave blank)
  {{current_stage}}   → where the deal sits now
  {{next_meeting}}    → the next scheduled touch, if any

Prompt
  Role: an account executive closing the loop after a live call.
  Task: from {{meeting_notes}}, produce a recap, action items,
        a CRM update, and a draft email — in that order.
  Constraints: use only facts present in {{meeting_notes}};
               tag [MISSING] for any owner or date not stated;
               never invent a price, commitment, or close date.

Output contract (last lines of the prompt)
  ## Recap
  - Decisions:
  - Open questions:
  - Deal context:

  ## Action items
  | Item | Owner | Due | Blocker |

  ## CRM update  (opportunity {{opportunity_id}})
  Stage / Next step / Close date / Context note

  ## Draft email
  Subject: <under 8 words>
  <body, references two specifics from the call>

The [MISSING] tag is the quiet win. If an action item comes back with no owner or no date, the meeting left something undefined — better to see that now than three weeks later when the SOW stalls and nobody remembers who owned it.

Step-by-step usage

1. Paste the notes raw

Don't clean them up. Fragments, a quoted line from the buyer, "worried about the migration window" — drop all of it into {{meeting_notes}}. Tidying is the prompt's job, not yours.

2. Name the record

Fill {{opportunity_id}} with the Salesforce record and {{current_stage}} with where the deal sits. If you're running plain ChatGPT with no connection, the CRM block comes back as text you paste into the opportunity by hand.

3. Run it and read the recap first

Claude honors the four ## headings cleanly and keeps the sections separate. GPT-4o tends to fold the action items back into the recap prose, so restate "keep each ## section standalone" on the final line and it holds. Gemini pads the email past a natural length unless you repeat the cap near the end.

4. Scan for [MISSING] before anything else

This is the deal-hygiene check. Every [MISSING] is an open loop from the call. Resolve them before you send the email, not after.

5. Approve the CRM block and the email

The draft should need a one-line touch, not a rewrite. If you're rewriting the whole email, the notes were thin or the deal context variable was vague.

Prompt-craft patterns worth stealing

One recap, four readers. The recap serves the buyer (email), you (action items), the CRM (field update), and the team (digest). Forcing everything to read from a single recap block is what keeps the four copies consistent. Change the recap, and the rest re-derives.

Treat ## Recap as the single source of truth. The action items,
CRM update, and email must not contradict it or add facts to it.

A CRM block, not a CRM paragraph. Ask for prose and you get prose you then have to parse into fields. Ask for Stage / Next step / Close date / Context note and you get something that maps one-to-one onto Salesforce fields. That structure is what makes a connected agent able to write it back without guessing which sentence is the "next step."

Two specifics, or it reads like a template. The email instruction forces at least two concrete references from the call — a name, a number, a worry the buyer voiced. That's the line between a personal follow-up and the generic AI-assisted note every prospect now recognizes. And no, pasting a six-line persona doesn't fix a generic email; two real specifics do.

One honest caveat: this prompt is only as good as your notes. Thin notes give you a thin recap and a polite, empty email. If you're not capturing decisions and next steps live, fix the note-taking before you blame the prompt.

Variables you'll set

Getting started

1. Paste your raw notes into {{meeting_notes}} right after the call ends.
2. Name the opportunity in {{opportunity_id}} if you want a CRM-shaped block.
3. Run the prompt and read the recap before the email.
4. Clear every [MISSING] tag in the action items.
5. Approve the CRM update and send the one-line-edited email.
6. Keep the same prompt for the next call so every deal reads like one voice.
7. When you connect Salesforce and Gmail to an agent, the same contract writes the fields and drafts the email directly.

If the email itself is your only bottleneck, the lighter sales follow-up email prompt covers just that artifact. And once a deal is qualified, a MEDDPICC qualification prompt scores where it actually stands before you commit a close date. Browse the rest of the prompt packs when you're ready to wire the whole post-call loop.