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

# Call Recordings

When call recording is enabled, the voice runtime can retain the caller and agent audio as separate channels. Separate channels support participant-specific review while allowing the playback API to construct a synchronized stereo stream.

Recording finalization is best-effort. A call can complete successfully even when no recording artifact is available, so clients should check the call's recording-availability field rather than infer availability from call status.

## Channels and Timing

| Channel    | Contents                               | Playback behavior                                             |
| ---------- | -------------------------------------- | ------------------------------------------------------------- |
| **Caller** | Inbound caller audio                   | Served as mono WAV for browser playback                       |
| **Agent**  | Spoken agent audio                     | Served as mono WAV using the sample rate recorded in metadata |
| **Stereo** | Caller on the left, agent on the right | Constructed on request from the two stored channels           |

The two source channels can use different audio formats and sample rates. Recording metadata preserves the actual format, rate, duration, size, direction, and media-start timestamp for the call. The playback service converts or resamples audio when needed; the stored source channels are not assumed to be a prebuilt stereo file.

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

Depending on the API surface used, authenticated clients can retrieve:

* Caller-only and agent-only audio
* A synchronized stereo WAV stream
* Recording metadata
* Aligned waveform peaks for timeline rendering
* Raw channel downloads for supported recording endpoints

Recording endpoints authenticate the requester and resolve the call within the requester's workspace before returning an artifact. Missing calls, unavailable recordings, and unavailable recording services return explicit errors rather than an empty audio response.

## Availability and Retention

Recording availability depends on deployment configuration and successful finalization. Retention requirements should be configured and validated as part of the workspace's data-handling policy; the current runtime does not expose the former multi-tier archive-and-restore workflow described in older documentation.

{% 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.amigo.ai/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.