When you call through Leadline, the call is recorded by default. The recording is a single audio file tied to the lead, with a transcript next to it. The lead gains a Calls tab; each call shows up there with its duration, the outcome, the notes you filed, and a play button.

This is the working walkthrough for what happens to the recording, who can hear it, and how to use it without drowning in audio.

How recording happens

The moment the call connects, the dialer starts capturing audio in the browser. The capture is end-to-end through the WebRTC stream — Leadline doesn’t tap the system audio, it captures the stream directly.

When the call ends (you hang up, the lead hangs up, the dialer auto-files a no-answer), the recording is finalised:

The audio is encoded as a single .webm file (Opus codec).
A transcript is generated server-side using the carrier’s transcription API. The transcript takes 20–60 seconds to arrive after the call ends; the row is editable immediately, the transcript fills in when ready.
The recording + transcript + outcome + notes are written to the lead in one transaction.

The whole sequence feels instant for the row (the lead is editable while you file the next call) and a few seconds slower for the transcript. You don’t wait on the transcript to keep dialing.

Where the audio and transcript live

In a Team workspace, the recording and transcript live in the workspace’s Postgres database, attached to the lead. The audio file is stored as a blob (or in S3, depending on workspace configuration — the choice is on the workspace owner).

In Solo, the recording lives in the extension’s local storage, attached to the lead. Same structure (audio file + transcript + outcome + notes), different location (browser storage instead of Postgres).

Either way, the row carries the call. If you go back to a lead three weeks from now, the calls you made are still there.

Who can see recordings

In a Team workspace:

Owner sees everything, including billing.
Admin sees everything except billing.
Manager sees the leads assigned to the team they manage, including all calls on those leads.
Member sees only their own leads, including the calls they personally made.

A manager can listen to a rep’s calls. A rep can listen to their own calls. Members cannot see other reps’ calls. The role that grants visibility is the role that grants lead visibility.

In Solo, only you see your recordings — there’s no shared workspace to share them into.

How to listen to a recording

Open the lead. Click the Calls tab. Each call is a row in the table. Click the play icon next to a call to open the player.

The player shows:

A waveform of the call.
A scrubber with timestamps.
The transcript next to the waveform, with each speaker’s turns colour-coded.
The outcome and notes you filed.

Click any sentence in the transcript to jump the audio to that moment. This is the most useful feature for coaching: “the lead said X at 1:23, the rep said Y at 1:30” — you can jump to either moment, listen, and write the feedback inline.

You can also download the recording as a .webm file if you want to keep a copy outside the workspace.

What you can do with a recording

The common uses, in order of frequency:

Coaching. A new rep is failing to book the second call. Pull up three of their calls from last week, listen, write feedback. The transcript lets you find the moment without scrubbing audio.
Dispute resolution. “Did the lead actually say they wanted a quote?” Listen, check, write the answer in the lead’s notes. No more arguing about what was said.
Objection library. When a lead says “we already use a competitor,” pull up the previous call where they said that. Write the rebuttal that worked. The library compounds.
Compliance. If a lead claims the rep was rude or made a misleading claim, listen to the call. The recording is the truth.
Self-review. Most reps improve fastest when they listen to themselves. The Calls tab makes this easy — pick three calls from the past month, listen, notice what you did differently on the ones that booked the meeting.

You don’t have to use any of these. The recording is just there, attached to the row.

What this is not

A few honest things:

Not a call centre. Leadline does not provide call queues, hold music, or whisper coaching. The dialer is one agent, one call at a time. If you need call-centre features, use a call-centre product.
Not a transcription service. The transcript is a side-effect of the recording. It is good enough for coaching and notes, not good enough to publish. Treat it as a starting point for your own notes, not as a final document.
Not a retention guarantee. Recordings are kept with the workspace. If the workspace is deleted, the recordings go with it. If you want to keep a copy of a specific call, download it.

Retention

The default retention is: recordings are kept as long as the lead is in the workspace. When the lead is deleted, the recording is deleted with it. The transcript goes with the recording.

Workspace owners can configure shorter retention (e.g. 90 days) for compliance reasons. The configuration is in the workspace settings.

Where to go next

If you have Calling credit and a list, open the list, click Dial queue, place a call. The recording starts automatically.

If you want to read more:

The dialer — the broader workflow that includes recording.
RBAC in practice — who can hear the recording depends on the role.
What we don’t do — for the boundaries, including that we don’t do predictive dialing.

Recordings are not the point. The point is that the row and the call are bound. Recordings are how that binding shows up when you come back to the lead later.