Ask Wispr about your meetings and shared notes

Last updated: November 21, 2026

Available on: Mac and Windows

Ask follow-up questions about a meeting, open the source meeting, send a draft Flow prepares, or ask Flow to update your notes.


Ask a question

Note: The Ask Wispr bar in the Notetaker hub appears after you record a meeting; connecting a calendar alone is not enough. In hub search it is hidden while a folder is selected and you have not typed a question.

  1. Open a meeting note or the Notetaker hub.

  2. Click into the hub Ask bar or the meeting's Ask anything field at the bottom, then type.

  3. Press Enter or Cmd/Ctrl+Enter to send. Shift+Enter adds a line break; Escape leaves the field without sending. Empty or whitespace-only questions send nothing.

Where you ask

Search scope

Open meeting

Its transcript, notes, summary, speakers and earlier chat turns.

Notetaker hub

Your meeting notes more broadly.

In an open meeting, Flow starts from the most recent part of the discussion, so "what did they just say?" works during and after a long meeting; for an earlier part, ask Flow to go back to it.

Flow draws on meeting titles, notes, summaries, transcripts and attendee information. It cites only meetings it read, flags uncertain speaker attribution and says what it could not find; an answer drawn from another meeting identifies and links it in the first line.

Selecting a meeting named in an answer opens that meeting with its chat drawer raised on the chat tab, showing the meeting's own chat; your hub conversation stays as it was. Meetings Flow cannot open show the meeting name as plain text instead of a link. Sources outside Flow — an email, a Slack message, a Notion page, a calendar event or a web page — always appear as a clickable citation chip, including when you ask Flow to open one; click the chip to open the source, and web pages open in your default browser. Chats saved earlier keep the links they were created with.

Note: A chat that is still working keeps going while you move between the hub and the meeting drawer, updates in both places, and can be stopped from either one.


Review and send an action card

When you ask Flow to send or create something, it proposes a draft on a card headed by the action it will take — New email, New message, New page or Update page. You can edit every part of the draft before sending.

  • Email: To and Cc hold recipient chips — type an address and press Enter or comma to add it, Backspace to remove the last one. Subject and the body are editable too.

  • Slack: pick people and channels from the searchable recipient list. Typed text on its own is never used as a recipient.

  • Notion: edit the page title alongside the body.

  • Sending account: Gmail and Slack drafts show From {account} · Switch account, so you can change account before sending.

Use Send (Create page or Add to page for Notion) or press Cmd/Ctrl+Enter. Copy copies the draft, and Open in {app} ↗ opens the draft's destination, or that app's home when there is no direct link yet. Press Esc to leave a field and return to the card; anything you typed is kept. Once the action completes, the card becomes a result — for example Sent to … at 2:14pm — with View in {app}, Copy and View content.

Note: A recipient outside your organization is called out in a notice above the fields, so you can confirm it before sending. Anything else that needs attention — a missing or invalid recipient, an empty subject, page title or body, a Slack group over 8 people, more than one Slack recipient, Use X instead when a person is deactivated or a channel is private, or an action that failed or only partly succeeded — appears as an alert row on the card. A draft replaced by a newer one reads Replaced by a newer draft. If the connector still needs you to sign in, the card shows a banner with Sign in to connect the account, or Skip to carry on without it.

Check what happened to an email

In a meeting chat, ask "did that email go out?" and Flow answers from that chat's own record: sent (with the time in your time zone), waiting for you to press Send, sending, failed, cancelled, replaced by a newer draft, or opened in Gmail for you to send yourself. When a draft did not go out, Flow gives the reason — the reply was stopped, the send failed, you pressed Undo, Gmail refused it, a newer draft replaced it, or it still needs you to press Send. It says it cannot confirm only when the outcome is genuinely unknown, such as after you restart the app or sign out, and suggests checking the app.

A draft cancelled because you stopped the reply stays cancelled for the rest of the session and can no longer be sent; confirming it reports "This action was cancelled". Flow will not re-send something it has already sent: asking it to "send the same to someone else" creates a new draft addressed only to that person, carrying the text you confirmed.


Ask about a day or date range

Ask questions like "what meetings did I have yesterday", "my meetings with alex@acme.com on Monday" or "what's on my calendar today". Flow uses your device's current date, local time and time zone, including daylight-saving changes; weeks run Monday through Sunday. Narrow the question for busy days or long ranges.

  • Meeting and note dates: meetings match calendar start time, or creation time without a linked calendar event — not the last edit; notes use the same local-day boundaries but match when they were modified.

  • Calendar days: include finished events; an event starting at midnight belongs to the new day only.

  • Coverage: answers cover meetings captured in Flow and connected Google Calendar events; other calendar providers may not be included.

  • Attendee searches: recordings without a linked calendar event lack attendee data and cannot match an attendee filter.


Ask about shared notes

Open your recordings from My notes (or Past notes). You can also paste a shared meeting link into Ask Wispr; Flow reads it using your account, not the owner's identity, and cannot read inaccessible, missing or deleted notes. If an emailed link is rejected because it uses a tracking redirect, open it in your browser and paste the final Wispr URL.

Note: Flow sees only what your sharing permissions allow; private notes stay owner-only. Invited viewers need the owner's organization to allow transcript sharing: an invitation cannot override a notes-only policy, and domain/team or anyone-with-link access alone does not grant transcripts. Owners keep access to their own transcripts, and if an admin restores transcript sharing, eligible viewers regain access automatically.

Shared-note chat answers only — it cannot edit the note or title, and New chat is unavailable. Reading a shared note works with Cloud Sync off, but offline reads and Ask Wispr's local shared-note search require Cloud Sync access; that search covers titles, content and owners, not transcripts.

Warning: Shared-note chats are stored only on this device, not in the cloud; older chats can disappear during automatic local-history cleanup. If Flow confirms revoked access while you're signed in and online, the local note and its chats are deleted and the open note closes with "Shared note is unavailable." Temporary network failures do not close the note or delete its chats.

For sign-in, app opening or permission problems, see Open a shared Wispr Flow note.


Ask Flow to edit your notes

Questions never overwrite your notes.

Important: Requested edits target sections, save automatically and are explained in chat. There is no confirmation step.

  1. Open a meeting note and its Ask Wispr chat drawer.

  2. Ask explicitly: "Update my notes with the budget decision."

  3. Review the result in My thoughts.

The summary is separate from your notes: rewriting it requires an explicit request and an existing summary, which cannot be blanked, and summary edits are blocked while a summary is generating or regenerating. Read-only notes cannot be edited, and chat cannot rewrite transcripts.

Edits can fail when target text is missing, repeated or changes during the request. Ask Flow to reread the current text and retry with a unique target.


Manage, rate and copy your chats

  • New chat: clears follow-up context without deleting saved chats; in an open, non-shared meeting it is disabled while the chat loads.

  • Past chats: open history from the empty hub bar or its suggestions row; in a non-shared meeting, use Switch chat, which appears when another chat exists. For older conversations, select Load more in hub history or scroll to the top of a conversation. Meeting-linked history entries open the meeting note, and background replies stay marked new until opened.

  • Stop processing: cancels only the running request in the chat you are viewing; partial text is replaced with "[Request stopped]" and any draft that reply was preparing is cancelled and cannot be sent. Sending another question replaces that chat's pending request; other chats continue.

  • Copy response: available on a completed hub answer; in a meeting drawer, copy and feedback need a completed answer in a saved chat, so pending, stopped, failed and unsaved drawer answers have no actions. Copied text keeps citation labels such as [Planning] and external links; in-app meeting links keep only their labels.

  • Rate an answer: use 👍 or 👎 on a completed answer; the rating is saved as soon as you click. If the rating cannot be saved, your previous rating comes back.

  • Close the drawer: click outside the meeting composer or use the minimize button. Stopping a recording or generating a summary can close it; reopen it immediately, even while the summary is generating.

In the hub chat and the meeting chat drawer, 👎 also opens a popover: pick any of Inaccurate, Incomplete, Off topic, Too slow or Other, add an optional note, then select Send feedback. If sending fails, the popover stays open so you can try again; clicking 👎 again opens an empty popover and does not send your rating twice. The reason popover is not offered in chats on shared notes, or for organization accounts and accounts covered by a HIPAA agreement — there, 👎 stays a single click.

Warning: Deleting a chat removes it everywhere in the app, permanently. In history, open the row's Chat actions (…) menu and select Delete, then confirm "Delete this chat? This cannot be undone." If an open chat is deleted or removed from local history elsewhere, its view resets to a blank chat.


If Flow cannot find an answer

A no-match answer can be final: Flow tells you when it finds nothing for the person, topic or dates you asked about.

  • No matching information: check whether you are asking in a meeting or the hub, then add a meeting title, person or time reference, or broaden the question.

  • Unrecorded calendar event: Flow can report its title and times, but has no recording, transcript or notes to draw on.

  • Missing or one-off meeting: Flow cannot retrieve inaccessible or deleted meetings. A one-off meeting — or one without a linked calendar event — has no recurring series to answer "last time" questions. If an older meeting is missing, wait, then ask again.

  • Shared notes unavailable: check your account and invitation, and follow any cloud-access message; organization-controlled settings require your admin. See data and privacy preferences.

Request or history loading failed

For "Chat request failed. Please try again." or "No response from assistant." in the meeting drawer, send your question again; the latter means the response was empty.

Hub failures include "Could not get a response. Try again.", "Something went wrong. Try again.", "Could not save this message. Try again." and "This response did not complete." Retry the question; retrying does not fix every failure.

For "Could not load chat history.", select Retry in history rather than resending the question.


Still need help?

If requests keep failing after you retry, contact support with the exact message, your platform and device, and the steps that reproduce it.