USE CASESalesAdvanced

“Follow-ups built from the notes, not the pleasantries”

In the same GTM article, Krista automates follow-up drafts from Granola or Gong notes after external calls. Drafts only — grounded in what was actually discussed, with concrete next steps.

Grok·0.0·0 saves·21 uses·via @kristaletz

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Followup** and connect Gmail, Google Calendar.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: call drafter.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it on demand; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

Drafts stay grounded in what was actually said on the call, not generic 'great connecting with you' filler, because the bot reads the Granola or Gong notes before writing anything. If the notes are thin, it says so and drafts a short recap instead of manufacturing one — the harder discipline for a tool built to sound confident by default.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Post-call follow-up drafter. You write. I send.

Mission: After any meeting with an attendee outside my company’s domains, read Granola or Gong notes (calendar is the roster). Draft a follow-up in my voice: To, Subject, body, concrete next steps from the call.

Tools: Calendar, Granola, Gong, Gmail (drafts only). Learn my voice from sent mail before the first batch.

What good looks like:
- One draft per external call since the last run. Grounded in the notes — no “great connecting” filler.
- Next steps are things someone actually agreed to, with owners if the notes name them.
- If notes are thin, say so and draft a short recap, not a fake recap.

Never, without asking: send the email, BCC anyone, attach a deck I did not name, or invent a commitment. Never draft follow-ups for internal 1:1s unless I ask.

Stop if there is no transcript and no notes — do not write from the invite title.
Use withGrok

via @kristaletz

Tips

  • ·Reconstructed from @kristaletz's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·adhoc
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Sales →

Fifty local businesses that need a new website

Ben Nash had spent months getting small, mediocre results asking ChatGPT and Gemini to find local businesses that could use a new website. One run with a Grok Bot returned 50 strong leads and a drafted outreach email for each — the leads exactly what he was looking for, the emails a solid first draft to personalize.

Sales·Simple·0 saves
Setup

Roof measured, proposal staged, change orders signed

Same two-day roofing run: it pulled roof measurements for a new inbound lead, built a full proposal/estimate with the contract staged pending his approval, then filled out, drafted, and emailed two change orders via e-signature.

Sales·Advanced·0 saves
Setup

The win-back bot that paid for its own subscription

Liam gave Grok Bot one job: win back churned customers. It found everyone who left in the last 6 months, emailed them, won several back, collected exit feedback, then overnight analysed why they left and built a 5-step plan. The bot covered its own subscription cost. 3.

Sales·Moderate·0 saves
Setup

It closed a $10k sponsorship from my inbox in 4 hours

Alex Finn gave a Grok Bot access to his business inbox and told it to answer and negotiate with legit companies. Within four hours it researched market rates and closed its first sponsorship deal on its own — turning the inbox he hates reading into revenue.

Sales·Moderate·0 saves
Setup