Skip to main content
Version: 0.9.18

Choose what a call recording retains

Use app recording settings to retain the outputs you need—for example, a transcript without audio. Storage destination and retention are separate administrative tasks.

Availability: Work in the team that owns the app. Publishing requires a Team Admin, a platform administrator, or a Member whose team permits Members to publish apps. Team/subscription checks can also prevent publication. If you can edit a draft but cannot publish it, ask your Team Admin to review the change. The team's recording destination must be configured before a recording can be stored.

Select the outputs​

Open the app's Flow Designer and choose Settings in the editor toolbar. In App Settings, find the Recording artefacts section. Its caption explains that an empty selection disables recording. Accept incoming calls in App availability controls whether the app accepts calls; it is separate from recording.

  1. Choose the outputs (marker 1). For transcript-only storage, choose Full call transcript and remove all audio selections.

    Marker 1: Recording artefacts with Full call transcript selected.

  2. Set the frequency (marker 2). Set Record every N calls to 1 when verifying every test call. This field appears when at least one artefact is selected.

    Marker 2: Record every N calls set to 1, meaning every call.

  3. Save the draft, review the change, and Publish the version through your team's normal approval process. Saving a draft alone does not apply these app settings to the published flow.

The images use synthetic data from 0.9.17-patch2. The illustrated artefact and frequency labels and values remain applicable to 0.9.18. Version 0.9.18 separates app availability from recording and expands the helper text to explain that 1 records every call and N records every Nth call only when artefacts are selected; these newer captions are not shown in the historical crops.

SelectionIntended retained output
Full call transcriptCall transcript and context, including captured keypad events where applicable
STT transcriptCaller speech-turn transcript
TTS transcriptBot speech-turn transcript
Full call audio with denoise processing (if applicable)Call mix using processed caller audio, when available
Full call audioCall mix using caller audio before preprocessing
STT audio per turnIndividual caller speech excerpts
TTS audio per turnIndividual bot speech excerpts

Selections control which outputs are requested. They do not guarantee that the corresponding audio/turn data exists or that processing/upload succeeds. If your integration needs per-turn audio references, select the matching STT/TTS transcript as well as that turn's audio.

From 0.9.18, a call without a captured caller speech turn has no transcript-stt-input.json object, even when STT transcript is selected. The full call transcript is a separate output. See the recording output reference for the conditions under which each object is written.

Verify after publication​

Make an approved test call after the new version is published. When it finishes, inspect the conversation and allow recording processing to complete. For transcript-only storage, the absence of an audio player is expected; ask the storage operator to confirm the selected transcript object if you need to verify S3 retention.

If an expected output is absent, follow Diagnose recording storage and processing. That procedure separates unpublished settings, frequency selection, missing source data, upload failures and playback lookup.

To interpret call-transcript.json, including its call fields, source stages and dtmfEvents, use the recording output reference.

Turn recording off​

Clear all Recording artefacts, then save and publish the change. The UI also resets the recording frequency to 1 when the selection is cleared. This stops requesting new recording outputs for the app; it does not delete existing recordings, conversation records or diagnostic logs.

Apply changes before the calls you want to verify. Do not assume a settings change rewrites an already-running call's prepared configuration.

Keep the ownership boundaries clear​

  • A Team Admin configures the shared destination using Team recording storage.
  • An AWS/storage operator verifies bucket access, lifecycle and existing-data handling. A Delphi role does not grant AWS access.
  • Runtime storage-protection controls can suppress retained content independently of the selected outputs. Recordings and storage connects the related responsibilities; selecting an artefact is not a promise that protected content will be retained.