Draft a Meeting Recap Email with AI
The fastest recap email is the one drafted from your notes while the meeting is still warm: paste the transcript or notes into @vustbot, name the audience, and get a subject line plus a short body — decisions up top, action items with owners below. The bot writes the draft; you paste it into your mail client and hit send.
Recap emails are a memory tax — skip one and next week's meeting reopens every settled question. The draft is mechanical work sitting inside text you already have, which makes it ideal to delegate to a model and keep only the review.
What the AI does in this scenario
- Decisions-first structure recipients can absorb in fifteen seconds
- Action items rendered as name → task → date, hard to ignore
- Audience-aware register: exec-brief terse or team-thread friendly
- Subject line included, so the email is findable in a month
- Draft-only by design — nothing sends until you do
Worked example: draft a meeting recap email with ai
01Input — what you paste
Notes: agreed to move launch from May 12 to May 26. Reason: payment provider cert delayed. Katya reworks announcement timeline by Fri. Legal (Sam) confirms cert ETA Wed. Audience: project channel + two VPs who skipped the call.
02Output — what comes back
Subject: Launch moved to May 26 — recap & owners. Body: "Hi all — quick recap from today's sync. Decision: launch shifts May 12 → May 26 (payment-provider certification delay). Actions: Sam — confirm cert ETA by Wed; Katya — reworked announcement timeline by Fri. Reply here if the new date breaks anything downstream."
How to draft a meeting recap email with ai — step by step
- 1Paste notes plus the audience
Transcript fragment or bullet notes into @vustbot, with one crucial extra: who reads this email. A recap for two VPs who skipped the call reads differently than one for the people who were in the room.
- 2Ask for decisions-first with a subject line
"Recap email: decisions first, then action items with owners and dates, under 120 words, include a subject line." Short enough to be read, structured enough to be searched later.
- 3Verify, paste into your mail client, send
Check names, dates and the decision wording against your notes — then copy the draft into Gmail or Outlook yourself. VUST never sends email on your behalf; the final click stays with you.
AI vs doing it manually
Manually written recaps have one systemic flaw: they get written late or never, because the meeting's over and the next thing is starting. By the time you write it, you're reconstructing. The AI draft flips the economics — thirty seconds of pasting while memory is fresh, and the recap exists. Where the human matters is calibration: the model can't know that "we agreed" was actually "the loudest person asserted". Read the draft once with that lens, fix the one overclaimed line, and send a better recap than the one you'd have written at 6pm.
The prompt to copy
Draft a meeting recap email from these notes. Audience: [WHO GETS IT]. Structure: subject line; one-line context; Decisions (bold the key change); Action items as Name — Task — Date; one closing line inviting corrections. Under 120 words. Use only facts from the notes — no invented dates or owners. Notes: [PASTE NOTES OR TRANSCRIPT]
Frequently asked questions
Does @vustbot send the recap email for me?
No — VUST has no email integration and that's a feature, not a gap. The bot produces a send-ready draft in Telegram; you paste it into your own mail client, so nothing leaves under your name without your eyes on it. The final send is always a human click.
How soon after the meeting should I generate the recap?
Immediately — the paste takes thirty seconds and your notes are at maximum fidelity. The classic failure is drafting at end-of-day from decayed memory. With the draft cost near zero, "recap before I stand up from the meeting" becomes a realistic habit rather than a discipline goal.
What should I check in an AI-drafted recap before sending?
Three things, in order: the decision wording (did the room actually agree, or did one person assert?), every name-to-task mapping, and every date. The template constrains the model to your notes, so errors are usually inherited from ambiguous notes — which the draft usefully exposes.
Related in Meetings
Try it on your real task
The welcome bonus covers a first run — send the prompt above with your own facts and judge the output yourself.
Open @vustbot