Meeting Recap

AI summary, transcript, and recording after every transcribed meeting — members-only, editable, displayed in your language.

Meeting Recap

After a meeting ends, InterMIND produces a recap — a single page with everything the session left behind:

  • Summary — an AI-generated summary of the discussion
  • Transcript — the full speaker-by-speaker transcript
  • Recording — the video recording, when the session was recorded

The recap is displayed in your language: whatever language the meeting was held in, the summary is translated for you on demand. A worked example is on the AI Meeting Recap feature page.

Where to Find It

  • Email — every signed-in participant of the session receives the recap link by email once processing completes; a guest who joined without an account has no mailbox on file and gets no letter
  • Chat — in channels, a recap document message is posted to the channel chat; click it to open the recap
  • Inbox — after an ad-hoc meeting (a link without a channel) the same recap document lands in each participant's personal Inbox under Chats, so the recaps of your ad-hoc calls stay in one place; the recap email's footer points there
  • Calendar — the calendar event created for a meeting includes the recap link, so it works from day one
  • Recap copy (BCC) — the host can add extra addresses that receive a copy of the recap email, e.g. a CRM inbound address (see below)

The recap link (…/r/…) is permanent — the same link serves every session of the meeting.

  • Meeting recap: what you get after the call — summary, transcript, recording, in your language

    1:04

  • AI meeting notes without a bot: summary, action items and transcript after every call (2026)

    1:24

Who Can Open It

Recaps are members-only: opening the link requires signing in, and access is limited to the host, the people who participated, and members of the host's team. Forwarding the link to anyone else does not grant access.

A guest who joined by link gets nothing after the call unless they keep the meeting from the exit screen: that creates a free account and opens this one session's recap — summary, transcript and recording — in the guest's language, nothing else of the meeting. A guest who instead asks the host to add them appears on the host's recap page with a one-click invite; once added, the guest is a member and opens recaps like any other member.

Editing the Summary

Meeting members can correct the AI summary directly on the recap page:

  1. Open the recap and click Edit under the summary
  2. Fix the text and save

Every edit creates a new revision. Version history shows the AI original and each edit as a word-level diff, with author and timestamp. The recap message title in chat updates to match the edited summary.

Open tasks of the organization. In an organization with team status pages on, every task and promise a recap records joins the organization's task chain from the day pages were switched on. When a recap is written, the open items the host may read (an admin: the whole organization; a member: the sessions they hosted or attended since joining, plus anything assigned to them) are judged against what was said in this session: an item someone reported as finished is marked done; an item that was discussed but not finished is marked not done, with the reason in the words of the meeting; an item nobody brought up stays open, untouched. These verdicts are not part of the recap — the recap holds only the tasks born in this meeting, as task boxes. The organization's open tasks, with their verdicts and the recap each one rests on, live on the team's status page and in the assistant (read_team_page), so one meeting's summary is never a list of everything the organization owes. A session with anyone from outside the organization in it, a guest by link included, judges nothing: the chain is the organization's internal state, and that session's recap reaches the outsider too; its own tasks still join the chain. A member's own verdict on a task beats the model's, and the model never overturns it. At the start of the next session Mia names the open items and their owners, so they are spoken about rather than forgotten. Recaps written before 2026-10-20 may still carry a Carried over section; it reads as before.

Alpha previewTeam status pages

Rating the Summary

Under the summary you'll see "Was this summary useful?" with thumbs up/down. A thumbs-down offers a quick reason — wrong numbers, missed key points, wrong focus, or made things up. Ratings help improve summary quality.

Recap Archive

  • Channels keep the recap of every past session — open the recap page and switch between sessions
  • Ad-hoc meetings keep only the latest session's recap, mirroring how their chat history is purged after each call

Deleting a Recap

The meeting host can delete a session's recap artifacts — summary, transcript, recording, and their translations. Deletion is permanent; the recap is not regenerated.

Recap Copy (BCC to Your CRM)

The host can have every recap of a meeting or channel also sent — as a hidden BCC — to extra addresses, typically a CRM or tracker inbound email (e.g. Pipedrive Smart BCC).

Where to set it up (host only):

  • Meetings page — expand your meeting's row and fill the Recap copy: field
  • Channel chat — display-settings menu (gear icon) → Recap copy

Each new address must confirm delivery first: InterMIND sends a test email shaped like a real recap, and someone has to open it inside the receiving tool and click its confirmation link within 1 hour. Until then the address is marked pending and no copies are sent. If the window passes, pick the address again in the field for a fresh test. If the test email doesn't arrive, allow noreply@intermind.com as a sender in the receiving tool.

Details:

  • Confirmed addresses are saved to your personal address book (up to 10) and can be reused across your meetings and channels
  • The copy is the same email participants get: the summary text, plus links to the full recap and transcript — those links still require signing in as a meeting member
  • Available on every plan

Requirements

A recap is produced from the meeting's transcription — see Transcription for how transcripts are captured. When an ad-hoc meeting ends without a recap — nothing was transcribed, too little was said to summarize, or the summary could not be written — a short note from Mia in each participant's Inbox says which, with the transcript link when there is one; no email is sent.

Related guides