Home/Use Cases/One-on-one insights
// One-on-one insights

One-on-one insights from every 1:1 and coaching call

One-on-one insights start with capture. MeetStream joins recurring 1:1s on Zoom, Google Meet and Microsoft Teams, then returns per-participant audio, a speaker-labelled transcript and the data behind talk time.

*Get started in minutes*

Overview

What a one-on-one meeting holds

A 1:1 is two voices, a standing invite, and a thread that runs for months. The signal sits in the pattern across the series.

Talk balanceWho held the floorQuestions askedAnd who asked themCommitmentsWhat each person agreedRecurring topicsWeek after weekAttendanceWho moved it, and how oftenQuotesWith a timestamp behind
Six things a coaching product reads out of one recurring meeting.
What you get

Two speakers, two clean streams

A 1:1 has the cleanest attribution of any meeting. Two people, two streams, and a timeline that says who held the floor.

  • Audio per participant
    Talk time and interruptions are counted, not guessed. The per-participant audio entry covers the model.
  • A speaker-labelled transcript
    Every line carries a name and a timestamp, so a coaching note quotes the real sentence.
  • A speaker timeline
    Byte ranges map back to the speaker, so talk time is a sum, not an estimate.
  • Join and leave times
    Who arrived late, who left early, and how long the meeting really ran.
Priya00:41
How did the migration week land for you?
Daniel00:48
Better than the last one. The rollback plan helped.
Priya01:12
Good. What should we take off your plate next?
Daniel01:19
The on-call rota, if someone else can pick it up.
transcript.json · speaker labels · timestamps
How it works

From a meeting link to your product

One request puts a bot in the call. It records and streams while the meeting runs, then a webhook says the artefacts are ready.

*Get started in minutes*

Meeting linkcreate_botone requestBot in the callrecords and streamsWebhookbot.doneYour productnotes and signals
The same five steps on every platform. Only the last box is yours.
Coverage

Put a bot on the recurring series

A 1:1 is a standing invite, so the calendar is the better trigger. Connect it once and coverage follows the series.

Read-only accessNothing written backThe recurring ruleOne, all, or rollingChanges pushedWatch channels andchange notificationsA minute earlyThe bot is already there
Connect Google Calendar or Outlook once, and the series takes care of itself.

The calendar API covers scopes, sync and the connection limit.

In your product

Coach during the 1:1, not a week later

Real-time audio reaches your server about 200 ms behind the room, with the speaker attached to every frame.

  • Live transcript chunks
    Sentence, word or raw chunks arrive at your webhook while the meeting runs.
  • A nudge in the moment
    Flag a monologue, or surface the question a manager forgot to ask.
  • An agent in the room
    A voice agent can answer out loud or post into the chat.
bot.joinedthe 1:1 starts
transcript.chunkwhile they talk
transcript.chunkwhile they talk
bot.donefiles are ready
After the call

What a coaching product does with it

Each 1:1 arrives in structured pieces, so a series becomes a trend.

  1. Connect the calendar, or send one request with the meeting link.
  2. Stream live audio and transcript chunks while the 1:1 runs.
  3. Collect the MP4, per-participant files, transcript and participant data at the end.
  4. Roll it up per pair: talk balance, recurring topics, and commitments carried over.

Media can go straight to your own bucket, and the security page holds the certificate and the audit status.

LIVE PRODUCTMeetStream dashboard listing every meeting bot dispatched, with platform, live status, and duration
Every 1:1, its recording and its transcript, in one place.

Every 1:1 captured, on any host plan.

One request, or one calendar connection, and the series records itself.

*Get started in minutes*

Per-participant audio
Live transcripts
MP4 recordings
Participant events
Calendar sync
FAQ

Got a question? We got the answer.

Common questions about recording recurring 1:1s: who joins, what comes back, and what it costs.

*Get started in minutes*

Can a bot join a recurring 1:1 on its own?

Connect a Google or Outlook calendar once and MeetStream reads the recurring rule from the event. Bots then land on one meeting, all of them, or a rolling window, joining a minute before the start.

How accurate is talk time in a one-on-one?

It is counted from separate per-participant audio, not guessed from a mixed track. On Zoom the streams are fully isolated. On Google Meet and Teams capture is tagged by speaker, which is exact through normal turn-taking.

What comes back after a 1:1?

An MP4 of the call, audio and video per person, a speaker-labelled transcript, and the participant list with join and leave times for both people.

Can I coach while the 1:1 is running?

Yes. Audio streams over a secure WebSocket about 200 ms behind the room, and live transcript chunks reach your webhook while people are still talking.

What happens when a 1:1 is moved?

The join time moves with it. MeetStream listens to Google watch channels and Microsoft change notifications rather than polling, so a reschedule reaches the bot.

Do both people know the bot is there?

Yes. The bot sits in the participant list under the name you choose, and it can post a joining message into the meeting chat.

Where does one-on-one data live?

Thirty days by default, or your own S3 bucket from the first byte. Everything is encrypted in transit and at rest, under ISO 27001 certified practice.

What does it cost to record every 1:1?

$0.35 per bot-hour, plus $0.10 per hour for MeetStream transcription. Every new account starts with $5 of credit.

Record your next 1:1

$5 of free credit, self-serve API keys, and a calendar connection that covers the whole series.