Draft a follow-up email from a meeting transcript
Detalles del prompt
Read transcript of a call, and draft an email that summarizes the key points and action items from:
##Transcript:
{{@Meeting_transcript}}
##Requirements:
‒ The email should be structured clearly, concise and informative, beginning with a brief overview of the meeting's purpose and participants.
‒ Then, detail the main discussions, decisions made, and any agreed-upon action items or follow-up tasks.
‒ The tone should be professional yet approachable, easy to read and understand.
‒ The email should serve as a useful reference for attendees and others who need to be informed about the meeting's outcomes.
Qué hace el prompt
After a recorded call wraps up, turning a long transcript into a concise, well-structured email can eat up 20–30 minutes of your day. This prompt eliminates that task entirely by reading the full meeting transcript and drafting a professional summary email on the spot.
Paste or reference your meeting transcript in remio, and it produces a ready-to-send email that opens with the meeting's purpose and participants, then outlines key discussions, decisions made, and assigned action items. The result is a polished recap that keeps everyone — attendees and stakeholders alike — aligned without anyone re-watching the recording.
Cuándo usarlo
• After a cross-functional project kickoff where multiple teams need a single source of truth on what was agreed.
• Following a client call where your account manager needs to share outcomes with internal stakeholders who weren't present.
• When a sprint planning or retrospective ends and the team needs a written record of commitments and owners.
• After an all-hands or leadership meeting where decisions need to cascade quickly to the wider organization.
• When you're covering for a colleague and need to relay meeting outcomes accurately on their behalf.
Ejemplos de prompts
Input: Read transcript of a call, and draft an email that summarizes the key points and action items from:
##Transcript:
@Product Launch Sync – June 12 with Sarah (PM), Dev (Engineering), and Lisa (Marketing)
remio responds:
Subject: Product Launch Sync – June 12 Summary
Hi team,
Thanks for joining today's sync. The meeting focused on finalizing the launch timeline for the v2.0 release. Sarah confirmed the go-live date is set for July 8, pending completion of the API integration work. Dev committed to delivering the final build by June 28, with a two-day buffer for QA. Lisa shared that the press embargo lifts July 1, and all marketing collateral will be reviewed by June 25.
Action items:
- Dev: Complete API integration and hand off to QA by June 28.
- Lisa: Share final landing page copy with Sarah by June 20.
- Sarah: Send updated launch checklist to all stakeholders by EOD Friday.
Let me know if anything was missed. Thanks!
Tip 1: Include the full, unedited transcript rather than partial notes — remio extracts more accurate action items and participant details when it has the complete conversation.
Tip 2: Specify the intended recipients in your prompt (e.g., "for attendees and the VP of Product") so remio adjusts the level of detail and context accordingly.
Tip 3: If your meeting covered multiple agenda topics, mention them upfront so the summary email uses those as section headers for easier scanning.
Más consejos
remio satisface todas tus necesidades de conocimiento
Descubre más funciones
Captura recursos de sitios web, carpetas locales & archivos.
Obtén respuestas fiables al instante de toda tu base de conocimientos.
Crea un PPTX nativo y editable
con tu experiencia personal.
Grabación y transcripción gratuitas e ilimitadas, sin bots.