top of page

根据会议记录撰写后续邮件

根据通话录音的文字记录生成一份简洁的会后总结邮件。

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

Suited for:
Source needed:

立即使用此提示!

问问雷米奥

记住一切,却不做任何整理。

remio满足您对知识的所有需求

了解更多功能

从网站、本地文件夹和文件中获取资源。

从您的整个知识库中获取即时、可靠的答案。

您的工作助手,可在台式机、浏览器和移动设备上使用。

无限次免费录音和转录,非机器人操作。

免费开始

一款本地优先的AI助手,具备个人知识管理功能

为了获得更好的人工智能体验,

remio 目前仅支持Windows 10+ (x64)M-Chip Mac

bottom of page