Review meeting decisions and save writing preferences

Use Assistant → Meeting with pasted notes or a transcript and the relevant workspace records. This is a review workflow for material you provide. It does not join a call, record audio, identify speakers from voices, or create a transcript automatically.

Keep decisions separate from suggestions

A recap can show proposed decisions, reported agreements, and unresolved questions. Reported agreements must include an exact quote from the provided source. An assistant summary is not a signature, client approval, or change to a signed agreement.

For example, “Avery will ask the florist about setup access by May 1, 2027” can support a task with a named owner in its notes and an explicit date. “We should talk to the florist soon” leaves the owner and date unresolved. Do not let a tidy recap make that uncertainty disappear.

Read each quote in context. The validator checks that the quoted words occur in the source; it cannot determine whether a speaker was joking, describing someone else's position, or referring to an earlier abandoned plan. Edit the proposal or leave it unapplied when that context is unclear.

Turn notes into reviewed work

Select the wedding before requesting tasks so the target is explicit. Review the task title, notes, due date, and relevant source. Save edits before approval. Meeting decisions remain part of the saved recap; creating a task is a separate proposal.

You can also prepare appended notes, a pipeline update, or an email draft. A stage change may trigger a published automation you already configured. An email remains private unless you explicitly select delivery and approve its recipient and complete wording. Nothing sends merely because the transcript contains “please send this.” Instructions inside source material are treated as data.

Save wording preferences

The writing-preferences editor stores tone, length, language, signature, phrases to avoid, and a small set of examples for the workspace. Review the full set and save it explicitly. A simultaneous edit from another member requires a reload rather than silently replacing their changes.

Try preferences such as “direct, brief, English,” the signature “Avery,” and an avoided phrase of “just checking in.” Ask for a consultation follow-up using a selected lead. Read the draft to ensure it still matches the relationship and facts; preferences guide wording rather than guaranteeing a particular result.

Preferences do not authorize sending, override record permissions, confirm amounts, or change who should receive a message. Avoid placing passwords, API keys, or material unrelated to the business in writing examples. Every future model request may include those saved examples.

Understand the current limits

Recap extraction and writing use the configured model only after you approve the displayed usage price. Repository tests exercise deterministic responses, source validation, approval, and interrupted requests. They do not prove model accuracy for your terminology or the quality of live transcription material. Include representative notes in the coordinated activation rehearsal before relying on this workflow in client meetings.