Meetings · Afterwards

The meeting,
as text you can search.

Transcription happens while people are talking, not afterwards. Transcripts are held per session as well as per meeting, exportable as text or JSON, and summarised — so a meeting somebody missed is readable in two minutes.

A recording nobody watches is not a record. Text is searchable; an hour of video is not.

The transcript

Per meeting, and per session.

While it happensProduced live rather than as a post-processing job you wait on.
Sessions within a meetingA long meeting has parts, and the transcript reflects that rather than being one undifferentiated block.
Ended explicitlyA session is closed as an act, so what belongs to it is unambiguous.
Using it

Export and summarise.

Text or JSONText for a human, JSON for whatever you want to build on it.
SummariesPer meeting and per session, for the person who was not there.
Recordings

In your own Drive.

Uploaded to your storageUnder your own retention rather than a vendor’s policy.
Batches

For the client-side path.

Batched transcript segmentsA separate route for clients that transcribe locally and post segments up, kept distinct from the server-side bot.
Sessions listedEvery session in a meeting, so a long call is navigable rather than one block.
Nearby

Related capabilities.

Video conferencing · Cloud storage · AI copilot

Miss the meeting, read it in two minutes.

Searchable text, a summary, and the recording in your own Drive.