# Meetings & AI Briefs Turn any recording or call into a clean, faithful brief: a short summary, a list of action items, the decisions that were actually made, and chapter markers you can scan. CoreReflex transcribes the audio for you, reads the transcript, and writes the brief — and (on Pro) can file it against a client, spin the action items into tasks, and trip your automations. This guide covers how to produce a brief from a recording or a pasted transcript, what each part of the brief means, and how briefs connect to your CRM and tasks. --- ## What you get from a meeting Every brief CoreReflex produces has five parts. They are extracted from the transcript and nothing else — see [Faithfulness: nothing invented](#faithfulness-nothing-invented). | Part | What it is | |------|------------| | **Summary** | A short, skimmable recap of the conversation. | | **Action items** | Concrete to-dos, each with an *owner* when the transcript makes the owner clear (otherwise the owner is left blank). | | **Decisions** | The choices that were actually settled in the meeting — not open questions or hypotheticals. | | **Chapters** | Section markers (a title plus a hint of where it starts) so you can jump around a long recording. | | **Follow-ups** | Loose ends and things to circle back on that aren't yet firm action items. | Briefs are deliberately concise: a tight summary, crisp action items, and only the decisions and chapters the recording actually supports. --- ## Two ways to make a brief You can start from a recording you already have in CoreReflex, or paste a transcript you bring with you. ### 1. From a recording (transcribe, then brief + Cut) This is the one-shot path: point CoreReflex at a recording in your workspace and it will transcribe the audio, write the brief, and (by default) open an editable Cut project on the timeline. Use this for Zoom/Meet/Teams exports, screen recordings, podcast takes, or any call audio you've uploaded. **Fastest path (dashboard):** 1. Put the file in **Files** (upload), or pick one already there. 2. Either open the hub card **Import a meeting**, or on a video/audio row use **⋯ → Meeting → brief + Cut**. 3. Review the brief; click **Open in Cut** to edit the recording on the timeline. Where the recording comes from: - **Zoom / Meet / Teams export.** Download the cloud recording (or local record), upload under Files, then run Meeting import. - **Record in the editor.** The Studio's recorder captures your screen and camera (with mic and system audio) and drops the clip straight onto the timeline as a normal asset. See [Editing & mastering](editing-and-mastering.md). - **Capture a browser tab.** The CoreReflex Chrome extension records a tab and uploads it to your workspace. - **Upload or import.** Bring in an existing file, or import one from a shareable link. Once the recording is in your workspace, the brief is generated *from* that recording — CoreReflex transcribes the speech and then summarizes the transcript. If the recording has no audible speech, you'll get a clear "no speech detected" message instead of an empty brief. > **Captions/transcription note.** Transcription runs on CoreReflex's speech-to-text > pipeline. If your workspace hasn't enabled a transcription provider yet, recordings can't > be auto-transcribed — paste the transcript instead (below), or enable captions. The same > transcription that powers briefs also powers the captions/subtitles workflow. ### 2. From a pasted transcript Already have a transcript — from Zoom, Google Meet, an external notetaker, or anywhere else? Paste it in and CoreReflex briefs it directly, no audio required. This is the fastest path and works regardless of where the recording lives. Very long transcripts are handled, with extremely long ones trimmed (the transcript is capped at roughly 100,000 characters) to keep the brief responsive. ### Where to start a brief From your **dashboard** at [corereflex.com/app](https://corereflex.com/app): - **Import a meeting** (hub card) — pick a Files recording → brief + Cut. - **Files → ⋯ → Meeting → brief + Cut** on any video or audio asset. - **Editor Meeting Hub** (inspector) — paste a transcript or summarize the selected timeline clip (brief only; use import for the full Cut package). --- ## Faithfulness: nothing invented Briefs are built to stay true to the recording. The model is instructed to: - **Use only what the transcript says.** It never invents facts, names, numbers, or decisions that weren't in the conversation. - **Only list real decisions.** Open questions and "maybe we should" musings don't become decisions. - **Attribute owners conservatively.** An action item gets an owner only when the transcript makes that owner clear; otherwise the owner is left blank rather than guessed. The brief is generated by Gemini on Google Vertex AI at a low "temperature" (low creativity, high fidelity), with the model asked to return structured JSON, specifically so the output tracks the source instead of embellishing it. If you read something in a brief, it came from the recording. Every brief also carries an inference trace — an internal record of which model and settings produced it — so a brief is attributable rather than a black box. Generation requires your workspace's Vertex AI to be configured; if it isn't, you'll get a clear "not configured" message rather than a hollow brief. --- ## Turn action items into tasks (Pro) A brief is most useful when its action items don't die in a document. On **Pro**, CoreReflex can file the brief and convert its action items into real, trackable tasks in one go. - Choose to **create tasks** when you generate the brief, and each action item becomes an open task in your workspace, sourced from the meeting brief. - If you linked the brief to a contact and/or a campaign, the tasks are linked to the same contact and campaign — so the work shows up where the relationship and the project live. - Action items with no clear owner still become tasks; you just assign them yourself afterward. Tasks created this way live in the shared task list alongside your manual to-dos and approvals. See [Client operations](client-operations.md) for managing tasks, assignees, and due dates. > Task creation, like everything in the client-operations layer, is a Pro feature. On the > free tier the brief is still generated and returned to you — it just isn't filed or turned > into tasks. --- ## Attach a brief to a client (Pro) On Pro, briefs become part of the client record instead of one-off notes. - **Link to a contact.** Generate the brief against a CRM contact and CoreReflex saves the brief *and* writes a `meeting_brief` entry onto that contact's activity timeline, so the next person to open the contact sees the meeting summary in context. - **Link to a campaign.** Tie the brief (and any tasks it spawns) to the campaign the meeting was about. - **Automatic timeline touch.** Filing a brief bumps the contact's "last activity," keeping your pipeline view honest about who you've actually talked to. ### Review past briefs All persisted briefs are kept per workspace and can be listed — either everything in the workspace, or just the briefs for a single contact. This gives you a running record of every meeting summary, action item, decision, and chapter you've captured for a client. ### Briefs and your data rights Because briefs can hold meeting content tied to a person, they're treated as part of that contact's record: - A contact's **GDPR export** bundles all of their meeting briefs (summaries, action items, decisions, chapters, follow-ups) into the export. - **Deleting a contact** hard-deletes their briefs along with the rest of their data — no orphaned meeting notes left behind. See [Client operations](client-operations.md) for the full CRM, export, and deletion model. --- ## Fire automations on a new brief (Pro) When a brief is filed, CoreReflex can trip your workspace automations on the `meeting_briefed` event. Use this to, for example, drop a note on the contact, create a follow-up task, or advance a campaign whenever a meeting is briefed. Automation runs are best-effort: they never block or fail the brief itself. See [Client operations](client-operations.md) for building automations. --- ## A typical flow 1. **Capture the meeting** — record in the Studio, capture a tab with the extension, or upload/import the file. (Or skip straight to step 3 with a transcript you already have.) 2. **Generate the brief** — point CoreReflex at the recording to transcribe-and-brief in one step, or paste a transcript into the Meeting Hub. 3. **Review** — read the summary, scan the action items and decisions, and use chapters to jump around a long recording. 4. **File it (Pro)** — link the brief to the contact and/or campaign, turn on *create tasks* so the action items become trackable work, and let your `meeting_briefed` automations run. 5. **Follow through** — work the tasks from your task list; the brief stays on the contact's timeline as the record of what was said and decided. --- ## Plans at a glance | Capability | Free | Pro | |------------|:----:|:---:| | Generate a brief (summary, action items, decisions, chapters, follow-ups) | Yes | Yes | | Transcribe a recording, then brief it | Yes | Yes | | Brief a pasted transcript | Yes | Yes | | Save the brief to a CRM contact + timeline | — | Yes | | Turn action items into tasks | — | Yes | | List/review past briefs | — | Yes | | Briefs included in GDPR export / contact deletion | — | Yes | | Fire `meeting_briefed` automations | — | Yes | Filing, tasks, and CRM linkage are part of the Pro client-operations layer. The brief itself is always generated and returned to you, on any plan. --- ## Related - [Client operations](client-operations.md) — contacts, tasks, automations, and your data rights. - [Editing & mastering](editing-and-mastering.md) — record in the Studio and work with captions.