会議の記録からフォローアップメールを作成する
Prompt detail
通話記録を読み、以下の要点とアクションアイテムをまとめたメールを作成します。
##トランスクリプト:
{{@Meeting_transcript}}
##要件:
‒ メールは、会議の目的と参加者の概要から始め、明確かつ簡潔で、情報量の多い構成にしてください。
‒ 次に、主要な議論、決定事項、合意されたアクションアイテムやフォローアップタスクを詳細に記述してください。
‒ プロフェッショナルでありながら親しみやすく、読みやすく理解しやすいトーンにしてください。
‒ メールは、会議の参加者や会議の結果を知る必要がある人にとって、役立つ参考資料となるようにしてください。
What the prompt does
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.
When to use
• 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.
Prompt examples
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.
More tips
レミオは知識に関するあらゆるニーズを満たします
詳しい機能はこちら
ウェブサイト、ローカル フォルダー、ファイルからリソースをキャプチャします。
ナレッジベース全体から、信頼できる回答を即座に取得できます。
デスクトップ、ブラウザ、モバイルで使えるアシスタント。
無制限の無料録音と文字起こし、ボットなし。