Call Recordings

Workspace-scoped caller, agent, and merged stereo recordings with time-limited download links and best-effort availability.

When call recording is enabled, the voice runtime can retain caller and agent audio as separate WAV files and create a merged stereo WAV during finalization. Playback uses those stored artifacts.

Recording finalization is best-effort. A call can complete successfully even when a recording is missing or incomplete. A successful request for download links does not prove that the files exist; the client must handle the result of fetching each link.

Channels and Timing

Channel	Contents	Playback behavior
Caller	Inbound caller audio	Stored as a mono WAV
Agent	Spoken agent audio	Stored as a mono WAV
Stereo	Caller on the left, agent on the right	Created during finalization and stored for playback

Current voice recordings store the mono channels as 8 kHz mu-law WAV and the merged stereo file as decoded PCM WAV. Each file carries its codec and sample rate in the WAV header. Clients should read that header, including when handling older recordings, rather than assuming that every WAV contains PCM audio.

The runtime aligns outbound audio with the inbound timeline during capture. This shared timing origin lets playback views align transcripts, agent speech, tool activity, and other call events without treating each channel as an independent recording.

Playback and Review

The Platform API authenticates the requester, verifies workspace access, and returns time-limited links for the caller, agent, and stereo files in that workspace. It does not check file existence before issuing those links. A missing artifact fails when the link is fetched.

Treat download links as temporary access to sensitive audio: share them only with authorized recipients and request fresh links after expiry. The current recording interface does not provide the former separate metadata, waveform, or on-demand stereo-transcoding endpoints. A playback client derives file metadata and waveforms from the downloaded audio.

Availability and Retention

Recording availability depends on deployment configuration and successful finalization. Older calls may lack the merged stereo artifact even when individual channels exist. Retention requirements should be configured and validated as part of the workspace's data-handling policy; stored retention settings are advisory and do not by themselves enforce deletion. See Retention Policies.

For terminal intelligence, recording-based review, and the retired transcript-verification path, see After the Call. For timeline review that aligns speech with agent actions, tool calls, and system events, see Call Playback Timeline.