Record & transcribe

Save and reuse Favorites

Turn important transcript moments, notes, questions, references, and actions into reusable cards.

Audience: Users who want the useful parts of records to keep moving into review, AI work, and content creation.

Time: 15 minutes

Level: Intermediate

Scenario

Start with the workflow this guide is designed for before moving into the steps.

As a founder reviewing several calls, I want to save only the useful moments as Favorites so decisions, questions, and source-backed ideas do not disappear inside long transcripts.

You can create a Favorite from a record, organize it on the board, edit the detail note, reuse AI blocks, create content from it, and recover earlier note versions.

Steps

Start from one useful moment

After reviewing a record, save the part that has a clear future use: a decision, question, idea, reference, meeting note, plan, issue, or action.

The Favorite has a reason to exist outside the full transcript.

It is not just a duplicate of the whole record.

Create the Favorite from the record

Use the Favorite action from the record or transcription surface. Vowise creates a card with title, summary, source record, note type, and available tags.

The card appears in Favorites.

The source record can still be opened from the detail page when available.

Organize the board

Use the board columns to separate Ideas, Questions, Issues, References, Meetings, Decisions, Plans, and Actions. Use search, note-type filters, and updated/created sorting when the board grows.

Each card sits in the column that matches its next use.

Manual tags are used only when they will help retrieval.

Edit the detail note

Open a Favorite to edit the title, note type, manual tags, and rich note. The note autosaves, and you can copy or download the saved content when you need to move it elsewhere.

The title says what the card is about.

The note contains the interpretation or next decision, not only raw text.

Use AI blocks deliberately

AI blocks can suggest summaries, viewpoints, arguments, next actions, follow-up questions, improvements, stories, counterpoints, and research references. Insert or drag only the blocks that improve the note.

Inserted blocks are checked against the source.

Regenerate AI blocks after the note changes enough to matter.

Create content when the source is ready

When a Favorite has enough source context and a clear audience, use Create from Favorite to start a draft, then continue reviewing it in the content workflow.

The generated draft keeps the Favorite as its source.

Private details are removed before publishing or sharing.

Choose direct share, publication, or export

Use Share for a first-level text handoff through the current browser or native share surface. Open Publish & export only when you need an unlisted public snapshot or a file. In a short desktop window, scroll inside this panel below Public link to reach Export. Vowise shows only the formats that the current browser or app host proves it can handle; copying text, opening a share sheet, publishing a snapshot, and saving a file are separate results. Electron reports Export saved only after its trusted host confirms the native file write.

Private details and private media references are removed before any outbound action.

Opening or dismissing a share sheet is not treated as proof that another platform received or published the content.

Cancelling the native save dialog is treated as a cancellation, not as a saved export.

You know that later Favorite edits stay private until you explicitly update the public snapshot.

After unpublishing, verify that the public page and publication-scoped media links no longer open.

Recover or remove safely

Use version history when an edit goes wrong. Remove a Favorite only when it no longer needs to be reused; the original record should remain your source of truth when it exists.

A mistaken note edit can be restored.

Removing the Favorite is not treated as deleting the original record.

Details

What belongs in Favorites

Favorites are for reusable pieces of thinking. They sit between raw records and downstream work.

Use Records for the full transcript and original audio context.
Use Favorites for selected ideas, decisions, questions, plans, actions, and reference notes.
Use Capture Library for external web pages, articles, notes, images, and references.
Use Journal when the goal is daily or period review.

Favorite detail anatomy

The detail page is where a card becomes useful. It is not just a preview.

Title, note type, and manual tags help search and board placement.
The rich note is where you write interpretation, edits, and next decisions.
Source record metadata helps you return to the original transcript when available.
Copy, download, and remove actions are for moving or cleaning up a finished card.

AI blocks, AI Chat, and Content Studio

These tools are related, but they do different jobs around the same source.

AI blocks structure the current Favorite into reusable pieces inside the note.
AI Chat is for asking follow-up questions when you still need understanding.
Create from Favorite starts a draft when the card is ready for an audience.
Content Studio manages schedules, topics, images, drafts, and review state across many sources.

Board habits that keep Favorites useful

A useful Favorites board is small enough to scan and structured enough to act on.

Move cards by next use, not by where they came from.
Search before creating a duplicate card.
Keep Actions and Decisions especially clean because they drive follow-up work.
Archive or remove cards that are no longer reusable.

What should you save from a long transcript?

Keep the full Record as the source. Save a Favorite only when one moment has a clear future job: a decision to revisit, an action that needs follow-up, a question, an idea, a plan, or a reference note. Do not copy the whole transcript into a second note. Keep the Favorite focused enough to reuse, keep your interpretation separate from the source wording, and return to the original Record before reusing exact quotes, names, dates, numbers, or commitments.

Keep full conversations and audio context in the Record.
Promote only moments with a clear next use to Favorites.
Verify critical facts against the original recording.

Choose the destination by the job

Sort information into the correct product container to prevent clutter: full transcript in Record, reusable moments in Favorites, external references in Capture Library, personal reflection in Journal, and repeatable structures in Prompt Templates.

Record: keeps complete source and surrounding context together.
Favorite: gives one source-backed moment a clear future job.
Capture Library: keeps external source material separate from voice records.
Journal: keeps reflection and review in the journaling workflow.
Prompt Template: defines how a larger source should be structured.

Keep the source; save the future job

A Favorite is most useful when you can clearly answer: What will I do with this later? If the answer is only 'this transcript exists,' keep it in the Record instead of creating another copy.

Confirmed decisions: revisit product specifications or strategic commitments.
Explicit actions: follow up on deliverables with owners and deadlines.
Unresolved questions: keep questions that still need investigation.
Reusable ideas: save compelling arguments or hypotheses for future writing.
Source-backed references: preserve metrics, benchmarks, or tool mentions.

Separate source wording from your interpretation

A useful Favorite pairs the source moment with your own note, but they should not be confused. Use the source Record when exact wording matters. Use the Favorite note for what you think it means or what to do next. Never promote an unverified AI inference or personal assumption into a settled fact.

Use Record for exact quotes, financial figures, and attributions.
Use Favorite note for meaning, personal synthesis, and next steps.
Keep uncertainty visible when details are inferred rather than explicitly stated.

When not to create another Favorite

Maintaining high retrieval value requires discipline. A smaller, intentional board is easier to reuse than a second inbox filled with transcript fragments.

Do not clip when the entire record remains the useful narrative unit.
Do not create duplicate cards when an existing Favorite already covers the concept.
Do not create cards when you cannot articulate a specific future use.
Do not place external articles or web clippings in Favorites; use Capture Library.
Do not save unverified AI inferences as established facts.

FAQ: Should I save the whole transcript as a Favorite?

Usually no. Keep the full transcript in its Record. A Favorite should exist because one part of that source has a clear future job, such as an action item, decision, or compelling idea.

FAQ: What kinds of transcript moments are worth saving?

Decisions, explicit actions, unanswered questions, reusable ideas, plans, issues, meeting takeaways, and source-backed references are good candidates when you expect to revisit or reuse them.

FAQ: Is a Favorite the source of truth?

No. Use the original Record when exact wording, names, dates, numbers, commitments, or surrounding context matter. A Favorite is a reusable working unit linked to the source when that connection is available.

FAQ: Should an AI-generated action item automatically become a Favorite?

Not without review. Verify whether the transcript actually states the action, owner, and timing. If those details are inferred rather than explicitly agreed, review the transcript snippet before saving.

FAQ: What is the difference between a Favorite and Capture Library?

Use Favorites for selected reusable moments from your voice records and related work. Use Capture Library for external web pages, articles, links, images, notes, and references you want to keep as source materials.

FAQ: What is the difference between a Favorite and AI Memory?

A Favorite is a source-backed unit you intentionally keep for future work. AI Memory is for durable personal context when supported. Temporary transcript details and short-lived tasks should not become permanent memory.