The meeting recording-consent notice: how it's posted and how admins control it

Last updated: November 13, 2026

Available on: Mac, Windows

Wispr Flow can post a recording-consent notice in your meeting chat or add one to the calendar event. Always get consent when transcribing others.

Note: Posting the notice in meeting chat requires a Business plan plus the organization or member opt-in below. It isn't available on Pro team plans or to organizations that haven't opted in.


Who controls the notice

Organization setting

Notice default

Control

Required for everyone, or never set

Locked on

Members can't change the switch or message.

Managed individually

Off until the member changes the switch

The member controls the switch and message.

No organization

On

You control the switch and message.

Members see the consent chat rows in Settings → Notetaker.


Change your notice

Edit the message box, then click outside it to save. Leading and trailing spaces are removed, and longer notices — including older and organization-set text — are shortened to 450 characters without an error. Blank text, or text matching the default, uses the default. Reset to default appears only after a custom message is saved. The English default begins “Hi everyone — quick note that I'm using Wispr Notetaker…”; changing Flow's language changes the default offered in chat and in the manual dialog.

Note: The switch and your custom message apply to the device you set them on and survive a restart of Wispr Flow, but reset when you sign out.


Set the notice for one meeting

  1. Hover an upcoming meeting in the Notetaker hub and click the … button to the left of Join.

  2. Choose Off, Notice only, or Include link under Calendar. The choice applies immediately to that meeting only; Change default settings opens the matching Notetaker setting.

The choice isn't shown when it can't be changed — for Outlook calendars, when you aren't the organizer, or once the meeting has started — and the … button disappears after a meeting ends. If turning the notice on requires calendar access Flow doesn't have, you're prompted to reconnect your calendar.

The event description reads “[Name] is taking notes with Wispr Flow Notetaker.” It adds “Notes will be shared with…” only when auto-share would send the notes to someone besides you — guests who are tentative or haven't replied still count — and leaves that sentence out if you're the only person auto-share would reach. With Include link, it also says the notes will appear in the event after the meeting.

Note: A notice already in the event is rewritten when you change a sharing setting or this meeting's notice choice — not when guests are added, removed, or change their reply.


How automatic posting works

Automatic posting is not guaranteed. Other apps, including Discord, and in-person meetings require manual consent. When you start recording, Flow looks for your meeting for up to 60 seconds, so you're still covered if you're admitted from a waiting room; if no meeting is found in that minute, recording continues and Flow asks you to post the notice yourself. The notice is posted once, as a single message, and is sent only when the chat box holds exactly that notice — anything you've already typed is left alone.

In Zoom, the notice posts while someone is screen sharing and follows chat into its separate Meeting chat window. In the Windows Zoom app it also posts whether the chat panel is closed, docked or popped out, when the toolbar is hidden, and when the meeting window is minimized, full screen or behind another app — Zoom is briefly brought forward and your previous window returns to how you left it. On Windows, Google Meet calls opened from a Google Calendar event are recognised even though the tab is named after the event.

Note: On Mac, browser meetings require Google Chrome with the meeting as the window's active tab; background meetings use the manual prompt. Flow uses the same Accessibility permission as dictation, so no additional “Automation” permission prompt appears during your meeting. On Windows, a meeting sitting in a background tab can't be found, and Flow shows the manual Obtain consent prompt instead.

When colleagues record the same meeting

When several colleagues from your company record the same meeting, only one notice is posted, however each recording was started, as long as the chat clearly matches that person's calendar event for the meeting happening now. Resuming a recording reuses that earlier match, so nothing is posted twice.

Waiting participants give a teammate's notice up to 60 seconds to land before posting their own; if a teammate's attempt fails, another participant posts within a few seconds. For meetings you join through Wispr Join, the manual prompt is skipped if a colleague already posted the notice for the same calendar event. When the match isn't clear — including after Wispr Flow restarts or once the calendar event has ended — a notice is always posted, so a meeting never ends up without one. Duplicates are still possible for Zoom meetings joined in the desktop app without a link, Teams and Slack huddles, and meetings that aren't on your calendar.

Accounts that aren't part of a company always post their own notice.

Zoom and Teams in the browser (Mac)

The notice can be posted into the Zoom web client on zoom.us and ZoomGov (zoomgov.com, including agency subdomains), and into Teams on teams.microsoft.com (work or school) and teams.live.com (personal). When Flow knows the meeting's address, it posts only to a tab on that same host, so a page that merely links to the meeting is never used.

Otherwise Flow posts only if exactly one Zoom or ZoomGov tab is open, or exactly one Teams tab across both Teams hosts; with two matching tabs, it asks you to send the notice yourself. Lookalike domains and Zoom's “Join meeting” and launcher pages are never used — Flow waits for the real Zoom call in the desktop app or live web client, and asks you to send the notice yourself if that call doesn't appear.

Mac clipboard protection

Flow uses your clipboard only if it cannot insert the notice directly. It keeps the notice from being archived by clipboard and password managers, then restores your clipboard; an empty clipboard stays empty and readable images are restored.

Unreadable clipboard content — file contents, PDFs, rich text with attachments, sound, unreadable images — prevents this fallback. Flow preserves that content and asks you to send the notice yourself instead.

Waiting rooms, stopping, and switching meetings

In a Google Meet waiting room or Microsoft Teams pre-join or green room, the notice is held until you're admitted. If the wait expires, Flow asks you to send it yourself rather than posting later.

Stopping recording calls off that recording's unfinished send without showing a prompt; if cancellation cannot complete, the notice may have landed. A recording you start at the same time keeps its own notice, posting it automatically or showing the manual prompt as usual.

If you use Switch meeting while recording, the notice goes to the meeting you joined — never to the one you just left. If you leave a call, Flow still recognises that meeting for about 95 seconds. Rejoining the same call, starting an ad-hoc note in the call you're already in, or sitting in a call without recording all post the notice as usual.


Send the notice yourself

Flow asks you to post the notice when:

  • Chat is unavailable: The host restricts chat, Flow cannot open or focus it, text cannot be entered, or sending cannot be confirmed. Flow never overwrites a message you're already typing, including an unsent Zoom chat draft.

  • The meeting is unclear: The app is not running, no matching meeting tab or window is open, only a Zoom join page is open, or multiple Zoom windows and chat boxes, multiple Zoom or ZoomGov browser tabs, two Teams browser tabs, or multiple Slack windows make the destination unclear.

  • Posting fails: The call ends before posting, posting takes too long, or an unknown problem occurs.

  • You change meetings: You leave a Zoom or Teams desktop client or a Slack huddle, or you start an ad-hoc new note.

The Get consent to transcribe card appears just above the recording bar. To post the notice:

  1. Click Copy consent message.

  2. Paste it into the meeting chat.

  3. Send the message.

  4. Click Done to dismiss the card.

You can ask participants for permission to transcribe instead — use this option if copying fails with “Couldn't copy the message”.

Warning: Quit and discard meeting opens “Discard this meeting?” Confirming permanently deletes this meeting's recording, notes and transcript. Nothing is saved to Wispr, and this cannot be undone.

If Accessibility access is off on Mac

The card says accessibility settings are missing and adds Open System Settings. Send the notice yourself or ask participants for permission, then restore automatic posting:

  1. Click Open System Settings to go to Privacy & Security → Accessibility.

  2. Grant Wispr Flow access.

  3. Restart Notetaker.