> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jinn.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Review and correct a meeting

> Listen back, switch between the agents who read the meeting, correct what they wrote, and check it against the transcript.

Open a recording and the whole meeting is on one page: the audio, the
[agents](https://docs.jinn.so/agents/add-an-agent.md) who read it, and what each of them wrote — a **Summary**, the
**Key points** and the **Action items**. All of it can be corrected, and the transcript it was
written from is one click away.

Find a recording under **Projects** → a project → **Recordings**, or on **Home** →
**Recordings** for every project at once.

![A recording page in Jinn: the title and date, the player, the row of agents with Default selected, Default's summary and key points in the editor, and the transcript with timestamps and speakers on the right](https://mintcdn.com/jinn/48W-8QqP6SyFhGB7/images/meetings/recording-general.png?fit=max\&auto=format\&n=48W-8QqP6SyFhGB7\&q=85\&s=946166589f39ba335c76946210b5b321)

A recording: the player, the agents, Default's write-up, and the transcript beside it

## Listen to the meeting

The player sits under the meeting's title and date. Play it from anywhere on the waveform,
change the speed, or turn the sound down.

**Download recording** saves the audio to your computer, named after the meeting. The bin
beside it deletes the audio and keeps everything else — what's deleted and what stays is in
[where your data goes](https://docs.jinn.so/workspace/your-data.md).

Until there's audio to play, the player says what's happening instead:

* **Recording…**, with a running clock — the meeting is still being recorded in the desktop app.
* **Finishing…** — the recording has stopped, and Jinn is putting the audio together on the
  server.
* **This recording couldn't be finished** — Jinn gave up putting the audio together. The
  transcript says so too, with **Try again**; see
  [when transcription fails](https://docs.jinn.so/meetings/check-a-recording.md#when-transcription-fails).
* **No audio yet** — there's no audio on this recording.
* **Audio was deleted** — someone deleted the audio and kept the rest of the meeting.

## Switch between agents

Under the player is a row of the agents who read this meeting, **Default** first: each one's
icon, with its name under it. Click one to see what it wrote. The counter at the end of the row,
**‹ 2 / 3 ›**, steps through them with **Previous agent** and **Next agent**, and the up and down
arrow keys do the same.

![A recording page in Jinn: the player, and under it a row of agents — Default, QA Engineer and Product Manager — with Add agent and the counter 3 / 3](https://mintcdn.com/jinn/48W-8QqP6SyFhGB7/images/meetings/review-a-meeting-agents.png?fit=max\&auto=format\&n=48W-8QqP6SyFhGB7\&q=85\&s=449010bfcc74f71029b1f0930ffad0ab)

The agents who read this meeting, and Add agent

The row also says how each one is doing. An agent still at work has **· reading** after its
name, and one that failed carries a warning mark.

The agent you're looking at is part of the page's address, so a link you send a colleague
opens the meeting on the same agent.

## Add an agent

Every [project](https://docs.jinn.so/projects/manage-projects.md) has a built-in agent called **Default**. As soon as the
transcript is ready, Default reads it and writes its summary without being asked. That's the
one waiting for you when you open a recording you made this morning.

Every other agent reads a meeting only when you ask. Click **Add agent** at the end of the row
and choose one: the agents already on the project come first, under **In this project**, and
the rest of the workspace's agents under **Other workspace agents**. It reads the same
transcript through its own lens, joins the row, and stays there.

So a meeting with one agent in the row, on a project with five, isn't a failure — nobody has
asked the other four yet. A meeting nobody has read at all says **No agents yet**, with
**+ Add agent** under it.

If **Add agent** is greyed out, its tooltip says why: the meeting has no project yet, you need
edit rights to change it, or only project admins can bring in an agent from outside the
project.

To take an agent off a meeting, open **⋯** above its text and choose **Remove agent**. What it
wrote goes for everyone; add the agent again and it reads the meeting afresh.

## Correct what an agent wrote

Nothing an agent wrote is final, and none of it needs keeping as it came. What it wrote is an
ordinary editable text, with the formatting toolbar above it: click anywhere and rewrite a
point, delete one that isn't real — an agent sometimes hears a suggestion as a commitment — or
add what it missed. Tick an action item once it's done.

Your changes are kept as you type, and everyone who opens the meeting sees the corrected
version. **Version history**, under **⋯**, shows the earlier versions if you need one back.

## Regenerate a write-up

**Regenerate**, under **⋯**, throws away what the agent wrote and has it read the transcript
again from scratch. Useful after you've corrected the transcript, or when the agent's
instructions have improved since it last read anything.

> [!WARNING]
>
> It replaces everything, including your corrections. If you've spent ten minutes
> fixing action items, copy them somewhere first — regenerating doesn't merge.

## Check a write-up against the transcript

The transcript is what was said, written out in timed segments, and it's what every agent
reads. Open it from the **Transcript source** tab at the top of the recording.

While it's being made, the segments appear as they're written — during the meeting too —
with **Loading…** at the end until it's done. If it fails, the panel says
**Transcription failed** and why, with **Try again**; see
[what each reason means](https://docs.jinn.so/meetings/check-a-recording.md#when-transcription-fails).

**Correct what was misheard.** Click **Edit segment**, fix the text, and save. Names and numbers
are what transcription gets wrong most often, and they're what an agent depends on — read
*Anya* as *Anna* and the wrong name lands in an action item. The transcript is also what
[search](https://docs.jinn.so/find/search.md) reads, so a corrected word is a findable word. Very long transcripts
open read-only, and Jinn says so rather than letting you type into something that won't save.

An agent doesn't pick up a corrected transcript by itself. Regenerate it when the correction
matters to what it wrote.

**Copy** takes a segment to your clipboard, for quoting what was said exactly.

## Fill a gap in the transcript

When Jinn can't transcribe one stretch of a meeting, it keeps the rest and marks the hole
instead of failing the whole transcript: **No transcript for 12:04–12:36**, with the times of
the missing stretch.

If you can edit the recording, **Try the missing parts again** sits under the transcript once
it's finished. It re-runs only the gaps, so the rest of the transcript and your corrections to
it stay as they are. When the gaps are filled, **Default** reads the transcript again and
writes its write-up afresh. Someone who can only view the recording sees the gaps but not the
button.

## Tag the moments worth finding again

A tag on a passage marks a moment: where the client said what they really wanted, where a
deadline was agreed, where someone raised the risk nobody wrote down. Select the text in the
transcript, choose **Add tag**, then pick a tag or type a new one — **Find or create a tag…**
does both from the same box. You can come back to every moment tagged that way, across all
your meetings.

![The transcript panel in Jinn with a passage highlighted in green and the tag box open: Find or create a tag…, the loyalty program tag switched on, and Add tag](https://mintcdn.com/jinn/48W-8QqP6SyFhGB7/images/meetings/add-tag.png?fit=max\&auto=format\&n=48W-8QqP6SyFhGB7\&q=85\&s=be9ce79643378fbe67af797f7a7e8d8b)

Tagging a passage in the transcript

Everything you tagged in this recording is collected on the recording's **Tags** tab.

These tags sit on passages. The labels you put on the whole recording are a separate thing, on
its **Properties** tab: tagging a passage *pricing* doesn't tag the recording *pricing*, and
the other way round.

## Discuss a passage

Open the **Comments** tab to talk about what an agent wrote without changing it.
Select the words you mean, write in the panel, and click **Comment**: the comment is pinned to
that passage, and anyone can answer it with **Reply**. Where you can only read the text, the
comment goes on it as a whole.

Other people see a new comment the next time they open the tab.

## Take a write-up elsewhere

* **Copy**, above the agent's text, puts the whole of it on your clipboard, ready to paste into a
  message or a ticket.
* **Export** saves it as Markdown, HTML, PDF, Word or an image.

## When an agent hasn't written anything

Three causes, in the order they're likely.

* **The transcript isn't ready.** An agent reads the transcript, so it can't start until
  transcription finishes. The page says **Waiting for the transcript…** while that's true.

* **The recording has no project.** No project means no agents to read it. This is the most
  common cause by a distance. There's a notification about it in your inbox, and choosing a
  project from there starts everything. See [checking on a recording](https://docs.jinn.so/meetings/check-a-recording.md).

* **The agent failed.** The page says **Insight generation failed** and offers **Try again**. If it
  keeps failing, the cause is usually the workspace's AI setup rather than this meeting — see
  [How your AI is powered](https://docs.jinn.so/workspace/ai-and-indexing.md).

## What an agent could and couldn't see

An agent reads the transcript of the recording it's on. It doesn't read your other meetings,
your docs, or what another agent wrote.

That's worth knowing when what it wrote seems thin. Usually the agent isn't wrong — the
conversation was: twenty minutes of scheduling produces twenty minutes' worth of key points.

## Where to go next

> [card] [Put a meeting to work](https://docs.jinn.so/meetings/put-a-meeting-to-work.md)
>
> The five minutes that decide whether a meeting is worth anything later.

> [card] [Add an agent](https://docs.jinn.so/agents/add-an-agent.md)
>
> Start from a ready-made role and make it sound like your team.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.