“The export button is broken - when I click it, nothing happens and there’s no error.”
Reproduces on Chrome 121 + Safari 17. Same step in dashboard. Audio confirms.
Every answer in Citesvue is composed from retrieved evidence and cites what it retrieved. This guide covers where to ask, how to ask well, how to read a citation, and why a declined answer is a feature.
“The export button is broken - when I click it, nothing happens and there’s no error.”
Reproduces on Chrome 121 + Safari 17. Same step in dashboard. Audio confirms.
Pick the smallest scope that could contain the answer; tighter scope, sharper retrieval.
Ask from the recording page. Best for "what happened in this session" questions: what failed, what was agreed, what did the customer object to.
Ask from the document page. Answers cite the page and section they were read from.
Ask across everything filed in a project - recordings and documents together. One question about a client returns spoken evidence by timestamp and written evidence by page.
Ask across sources you select from the whole workspace, when the answer could be anywhere.
This is what makes an answer verifiable instead of plausible.
The verbatim words the answer rests on, not a paraphrase of them.
Who said it, by name when the speaker is known.
The second it was said. One click seeks the player there.
When the evidence was visible rather than spoken, the citation carries the video frame - an error toast, a form state, a dashboard value.
Document citations name the page and heading they were read from, scanned pages included.
Each answer shows how well supported it is, so a thin answer looks thin.
"What did the customer say about SSO?"
Citation: Priya N. at 22:41 - "we can pilot without SSO, but procurement will block the wider rollout until it is there" - with the frame showing the requirements slide on screen.
Click the citation, hear the sentence, see the slide. If someone later remembers the commitment differently, the dispute takes thirty seconds to settle.
"What did the tester say when checkout failed?" retrieves evidence. "Was the meeting productive?" asks for a judgement the record cannot support.
Use the words people actually said where you can - feature names, error text, clause numbers. Retrieval searches meaning and exact wording together, and exact wording is precise.
Compound questions dilute retrieval. Ask the follow-up as a follow-up; the conversation keeps its context.
The answer is a claim; the citation is the proof. For anything that matters, click through and read or watch the source. That is the workflow the product is built around.
If an answer comes back with no supporting evidence, the page says so and suggests rephrasing or waiting for indexing to finish - see troubleshooting for the full list of states.
Or it could sit in a Drive folder nobody opens again. The difference is whether it has citations attached.