Quickstart
Citesvue turns recordings and documents into answers you can check. Transcript citations arrive first; optional visual evidence adds on-screen and frame citations when you need them. This is the whole first run with a recording you already have.
- Updated
- 30 August 2026
- Read
- 6 min
- For
- First-time users, evaluators
What Citesvue is, in one paragraph.
You give it recorded work - meetings, UAT sessions, demos, sales calls - and documents. Core processing indexes speech and documents in their respective workflows, then answers questions and extracts transcript-grounded findings with their source. For eligible video, request visual evidence when a bug needs a verified screen frame; decisions remain grounded in what was said and who said it.
Nothing below requires a payment method. Where a step needs a paid plan (the meeting assistant, pushing to Jira), the step says so.
Seven steps to your first cited answer.
Steps 1 to 6 work on the free plan. Step 7 needs a paid plan.
- STEP 01
Create your workspace
Sign up free with your email and a password. Your account is a workspace: recordings, documents, findings, and teammates all live in it. No card is needed on the free plan.
- STEP 02
Bring in your first session
Two ways in. Upload a recording you already have (drag the file onto the dashboard), or paste a meeting link on a paid plan and the assistant joins the call and records it for you. Uploading works on every plan.
- STEP 03
Let processing run
Citesvue checks the media, transcribes available audio, writes the recap, extracts transcript findings, and makes them searchable. You can leave the page; the activity centre and a browser notification tell you when transcript-first processing is ready.
- STEP 04
Read the recap, then the evidence
The recording page opens with the Recap: a short summary with key outcomes that jump the player to the moment behind them. Transcript and Artifacts are ready at the same time. For video, Analyze visual evidence separately to add Deep Dive, OCR, visual findings, and frame citations.
- STEP 05
Review the findings
The Artifacts tab lists what was extracted: bugs, requirements, decisions, action items, risks, questions, and insights. Transcript findings carry the verbatim quote, speaker, and timestamp. Optional visual evidence can later add screen corroboration without replacing their IDs or review state.
- STEP 06
Ask your first question
Open Q&A and ask in plain language: "What did the customer say about SSO?" Transcript answers cite the quote, speaker, and timestamp immediately. After visual evidence is ready, future answers can also cite on-screen text and frames.
- STEP 07
Send a finding where work happens
On a paid plan, connect Jira, Linear, Notion, or Slack from Settings and push an approved finding with its evidence attached. Delivery is queued and tracked; re-pushing a tracker or Notion item updates it in place instead of filing a duplicate, while Slack posts a fresh message each time.
Step 4. Core processing shows its transcript-first stages as it goes, so a long recording is legible rather than a spinner. You can close the page and come back; visual analysis is requested separately after core is ready.
A UAT session, end to end.
- 1. Upload the 40-minute UAT recording from this morning.
- 2. Processing finishes; the recap lists two decisions and five findings, three of them bugs.
- 3. Open the checkout bug. It carries the tester quote ("it charged twice and only showed one confirmation") and the timestamp 14:23. If screen proof matters, request visual evidence to add the verified frame showing the duplicate pending charge.
- 4. Approve the bug. Ask Q&A: "Which acceptance criteria failed?" - the answer cites the relevant transcript moments. If visual evidence is ready, it can also cite the screen state.
- 5. Push the approved bug to Jira. It lands as a typed Bug with severity, the quote, and a link back to the second it happened.
The developer who picks up that ticket never asks "can you reproduce it?" - the evidence is attached to the claim, not to a 40-minute file.
Three habits for the first week.
- Pick a real recording
A UAT session, a client call, or a demo - something where people spoke. Video is useful when screen proof may matter later, but audio-only recordings receive the full transcript-first experience.
- Know the optional allowance
The free plan includes 2 visual-evidence hours and 50 Evidence Q&A questions per month, with a library of 5 stored recordings. Transcription does not use the visual-evidence allowance.
- Ask questions you know the answer to
The fastest way to build trust in the citations is to ask about a moment you remember and open the evidence. That habit - verify, not believe - is the whole point.
When something does not behave as this guide describes, the troubleshooting guide covers the states you might see and what fixes each one.
Starting out, answered.
- No. The free plan is free forever and needs no card. Paid plans add the meeting assistant, integrations, more optional visual-evidence hours, and longer retention.
- Any meeting, UAT session, demo, or sales call you already have as a video or audio file: MP4, MOV, WebM, MKV, MP3, M4A, or WAV. Video offers optional visual analysis; audio still gets the full transcript-first experience.
- It depends on length and content, but the work runs in the background: you can leave the page, keep working, and the activity centre plus a browser notification announce when the recording is ready.
- The free and Pro plans are single-seat. Team plans start at 3 seats and add shared workspaces with roles, so recordings, findings, and questions are visible to everyone who should see them.
- Citesvue declines instead of guessing. If the evidence is not there, the answer says so, and you know the record is silent on the point rather than being handed a confident invention.