Skip to content
AdvancedProductivity· about 1 hour to set up, then a draft after every call

Follow-up emails after calls: Grok Bot learns how you write, drafts each one, and sends only after you approve

First have Grok Bot read the follow-ups you've already sent and save how you write in a voice.md file. After each call it drafts from the transcript and deal context, pings you in Slack, and sends only after you explicitly approve.

Start step 1 ↓

The problem

Every sales call needs a follow-up email. Early discovery calls and late-stage calls need different emails, writing them yourself takes time, and an AI on its own doesn't sound like you.

AI tools used

Tap a tool to see what it is and which other cases use it

What to prepare

  • Your sent follow-ups and call transcripts

How to do it

  1. 1

    Teach it how you already write

    You only do this once. Have it read your past follow-ups and work out how they differ by stage.

    Prompt

    Replace the 2 ✎ dashed parts with your own details, then copy.

    Read the call follow-up emails I sent in the last 3 months (sample, replace with yours). Match them to companies and deal stages in my CRM (sample, replace with yours), and work out how emails after discovery calls differ from later-stage ones, the openings and closings I use, and phrases I never use. Save it as voice.md and read it before writing any email. Show me first and save it only after I confirm.
  2. 2

    Draft after every call

    Each new call transcript gets a draft. It saves the draft and pings you in Slack, and never sends on its own.

    Prompt
  3. 3

    Tell it what you changed, and save it

    Have it add the reason for each edit to voice.md. The author says the drafts get better the longer you use it.

  4. 4

    Stuck on the instructions? Use the author's skill

    The author turned this approach into a public skill that asks what context your bot is missing, what it should do each time and where you stay involved. His call follow-up prompt is included as an example.

    Open the author's skill ↗

Done?

Was this helpful?

See the Advanced learning path →