Ask Wispr about your meetings and shared notes
Last updated: November 5, 2026
Available on: Mac and Windows
Ask Wispr finds decisions and commitments in your meetings and shared notes. Ask follow-up questions, open the source meeting, 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.
Open a meeting note or the Notetaker hub.
Click into the hub Ask bar or the meeting's Ask anything field at the bottom, then type. Suggested prompts appear once you click in.
Press Enter or Cmd/Ctrl+Enter to send. Shift+Enter adds a line break; Escape leaves the field without sending. The meeting field has no send button, and empty or whitespace-only questions send nothing.
Where you ask | Search scope |
Open meeting | Its transcript, notes and earlier chat turns. |
Notetaker hub | Your meeting notes more broadly. |
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. Long meetings or complex questions can produce partial answers. Flow can also use web search for public-world questions; it does not know your location, so include one for “near me” questions or answer its clarification request.
Hub answers show clickable meeting sources and inline citations — open a reference to review it in Flow. A citation pointing to a note someone shared with you opens the shared-note reader; Back returns you to the Ask chat. Older references and sources without usable links appear as plain text, and external citations open outside Flow. The meeting chat drawer shows no citation chips, but copied answers keep source labels.
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.
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.
Large ranges: narrow the question for busy days or long ranges.
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. While a shared note is open over an Ask chat, Cmd/Ctrl+K works as it does for your own notes and does not jump back to the Ask composer. 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.
Open a meeting note and its Ask Wispr chat drawer in the desktop app.
Ask explicitly: “Update my notes with the budget decision.”
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 during generation or regeneration. 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 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: opens history from the empty hub bar or its suggestions row. In a non-shared meeting, use Switch chat, which appears when another chat exists.
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 and replaces partial text with “[Request stopped]”. 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, streaming, stopped, failed and unsaved drawer answers have no actions. Copy provides formatted and plain text, falling back to plain text if formatted copying fails; citations keep readable labels such as [Planning], external HTTP/HTTPS sources keep their links, and other links, including in-app meeting links, keep only their labels.
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.
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.
Older meeting 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.