After a session
Updated 25 August 2026 Applies to: Web app · iOS · Android · Windows · Browser extension · MCP server
The transcript is on the session in your account, not in an email. It is written as the room runs, so a session that ended early still has everything said before it ended. Export takes it somewhere else, on every plan, without asking anybody.
Before any of it: what exists today
In development 2026-08-24
The client is being built and no session has run for anybody, so there is no transcript to open yet. Everything below is the finished flow as it is designed to work, published now so that the shape is not a surprise later. The three causes and the export route are written from the design rather than from a session anyone has had.
My transcript is missing or incomplete
Three things produce a transcript that looks short, and only one of them is a defect. Check which it is before you write to us, because the third one we want to hear about immediately and the first two are the system working.
| Why | What happens | What to do |
|---|---|---|
| The session ended early | The transcript stops where the connection did. Everything spoken before that point is there. | Nothing to recover. Start a new session from the same brief. |
| You are looking at the summary | The summary is short by design. It is not the transcript and it is not meant to be read as one. | Open the full transcript rather than the summary. |
| A turn is attributed to the wrong voice | Attribution is written from who held the floor. An overlap at the moment of a handover is where it can slip. | Tell us, with the session date. It is a defect and we want it. |
What to do with it
01
Open the session from your account
Every session you have run is listed there with its date. The transcript is on the session rather than in an email.
What you should see. The full exchange, attributed turn by turn, in text you can select.
02
Read the points you conceded first
The useful part of a session is rarely the part you enjoyed. Find where you changed position and read the turn before it.
What you should see. Your own words, in a form you can quote in the decision record.
03
Check every figure a persona stated
The personas invent numbers. Not often, and it sounds exactly like the rest of the session when they do.
What you should see. A figure you can trace to your own source, or a figure you strike out.
04
Export it if you want it somewhere else
Export is self serve, on every plan, and it does not go through support.
What you should see. A file that opens in something that is not this product.
05
Decide where it lives
A transcript is a record of your unresolved weaknesses, spoken aloud and attributed. Treat it like the document it is.
What you should see. A deliberate decision about who can read it, rather than a default.
Taking it out
Export gives you the transcripts, the summaries, the briefs you wrote and the account history, in formats that open somewhere else. It is included on every plan, and it never goes through a support ticket.
What a session produces, where each piece goes and how long it is kept
If the session is not there at all
Check you are signed in as the account that ran it. A session belongs to the account that opened the room, and an organisation with two accounts is the most common reason a session appears to have vanished.
If it is genuinely gone, say so and give us the date and the rough time. A missing session is a defect rather than a support question and it goes into the changelog when it is fixed.
Still stuck
Write to support@tingvar.com. A person replies within 2 business days, Monday to Friday. Send the session date rather than the transcript.