> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/channels/voice/recordings.md).

# 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](/operations-and-safety/compliance.md#retention-policies).

{% hint style="info" %}
For optional post-call transcript verification and quality analysis, see [After the Call](/channels/voice/audio-pipeline.md#after-the-call). For timeline review that aligns speech with agent actions, tool calls, and system events, see [Call Playback Timeline](/intelligence-and-analytics/intelligence/call-intelligence.md#call-playback-timeline).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.concurrence.com/channels/voice/recordings.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.