Recordings and retention
What a call's recording holds, how to turn it off per character, how long it's kept, and how to listen to it or delete it.
Calls are recorded so you can listen to them later: both voices, the person's and the character's. You can turn recording off per character, and delete any recording at any time.
What is recorded
- Both voices, in one stereo WAV per call: the person on the left, the AI on the right, at 16 kHz (about 3.84 MB a minute).
- Never the face's video.
- A meeting's recording has the meeting's mixed sound on the left. A meeting can turn recording off or on for itself (
recordwhen you send it); when it's on, the character's first line and a message in the meeting's chat tell everyone the meeting's audio is being recorded. The company that runs our meeting bots keeps no recording of its own. - Nothing is recorded for a call that never connected.
The website widget's call page tells the visitor, under the Call button, that the call is recorded.
Turn it off for a character
Each character has a record switch, on unless you turn it off. Off, nothing is recorded for its calls, and their recording shows off.
{ "record": false }How long it's kept
Each organization keeps its recordings for 30 days by default; older ones are deleted automatically, hourly. Ask us if your organization needs another period (1 to 3,650 days).
On a call
Get a call carries the recording's state:
{ "status": "ready", "seconds": 94, "bytes": 3609600, "deleted_unix": null }Listening to recordings in the dashboard's Conversations page is coming soon. Today, ask for a link through the API.
status | What it means |
|---|---|
pending | The call is on, or just ended and the file is being finished (a few seconds) |
ready | You can listen to it |
none | Nothing was said: the call never connected |
off | The character's record switch was off |
deleted | It was deleted, by you or by the retention period |
When a recording is final, your server hears a recording.ready webhook, once per call. It carries the call's ids, source, env, metadata, the length and size, never a link: links expire, so ask for one when you need it.
Listen
Ask for a link each time someone presses play. Through the API:
| Method | Path | Answer |
|---|---|---|
GET | /v1/calls/{id}/recording | { url, expires_unix, seconds, bytes }: a link to listen, good for 15 minutes |
DELETE | /v1/calls/{id}/recording | { ok, call_id }: the files are deleted and links stop at once |
The link needs no sign-in: it is the permission, so share it only with people who may listen. It serves the WAV with byte ranges, so a player can seek. Nothing in it can be guessed or changed, and it stops working after 15 minutes, or at once when the recording is deleted (404).
Delete
Deleting removes the files at once, and every link stops. Deleting again, or deleting a call without a recording, answers the same.
| Status | Code | Why |
|---|---|---|
| 404 | no_recording | none, off or deleted |
| 409 | recording_not_ready | Still being recorded or finished: try again in a few seconds |
| 409 | call_running | The call hasn't ended yet |
| 503 | recording_unavailable | Recordings can't be reached right now: try again |
More in Recordings for developers.