Workflows · Follow up on meetings
Meeting summary
One meeting's decisions, actions with owners, quotes with the speaker and time, and open questions.
Have your agent do it
Have a summary written after every meeting, from its cleaned transcript. Fill in the parts in [square brackets], then paste this to your agent.
Summarise [the meeting] into the [name of your shared Space] Space from its sanitized transcript: decisions, actions with owners, quotes that matter and open questions. Use the template at https://avalandra.com/help/template-files/meeting-summary. Name it with the meeting's short name, the word "summary" and the meeting date, and nothing longer.Whenever a meeting in the [name of your shared Space] Space has a cleaned transcript and no summary yet, summarise it: decisions, actions with owners, quotes that matter and open questions. Use the template at https://avalandra.com/help/template-files/meeting-summary, named with the meeting"s short name, the word "summary" and the meeting date. Check [every hour during working hours, or continuously while you"re running]. Never write two summaries for one meeting; update the existing one.When to use it
- People need what a meeting decided without reading the transcript.
- You follow up after every meeting.
What to name it
[Meeting] summary [date], such as “Client call summary 4 Nov”. Keep it that short; agents otherwise tend to write long, descriptive titles.
What it looks like
DocumentClient call summary 4 Nov
Used in
Related templates
- Cleaned transcriptThe full transcript of a meeting, word for word with speakers and times, with private discussion replaced by a placeholder.
- Update for a clientA short update for someone outside the team, covering what's done, what's next and what you need from them.
- Catch-upWhat changed while someone was away, with decisions and their reasons, what's done, and what's waiting on them.
For agents
- Fetch the template from
https://avalandra.com/help/template-files/meeting-summary. - Keep its
<style>blocks and class names. Replace every piece of sample content with content from the record, and never carry over its names, Spaces, documents or dates. - Title the document
[Meeting] summary [date], filled in, such as “Client call summary 4 Nov”. No longer, descriptive titles, and no title or label repeated inside the document: Avalandra shows the name above it. - Delete sections with nothing in them, and link every claim to its source with web_url.
- Create it with
ava document create(kind html, source_format html, and a parent_id for the folder), then readwarningsin the response for anything the renderer removed. - If the prompt still contains [square brackets], ask the person what goes there.