Replaying a Contact Recording (Verification and Re-recording)

Introduction: In Voice (IVR) flows, callers can leave spoken responses. The Play a Contact Recording action lets you replay that audio back to the caller—useful for confirmation, quality checks, and allowing callers to re-record if they’re not satisfied.

Replay caller recordings for verification (and allow re-recording)

If you just need the essentials, follow this quick path:

  1. Collect a recording with Wait for Audio and save a clear result name
  2. Replay it using Play a Contact Recording and reference @results.<recording_name>
  3. Add a confirmation menu (confirm vs re-record) and route accordingly

This pattern helps callers confirm what they said and reduces low-quality or accidental recordings.

Step-by-Step Process

1
Collect a voice recording from the caller (Wait for Audio)

Goal: Capture a spoken response and store it for later use in the flow.

  1. Open an existing Voice (IVR) flow (or create a new one).
  2. Add a Wait for Audio split action.
  3. Configure the prompt message that asks the caller to speak.
  4. Assign a clear Result name (example: recording).

[CAPTURE: IVR flow editor showing a “Wait for Audio” action with a result name defined.]

💡
Tip: The result name matters because you’ll reference it later as @results.recording. Use short, consistent names (recording, voicemail, feedback_audio).

2
Replay it using “Play a Contact Recording”

Goal: Play back the caller’s recorded audio during the same IVR session.

  1. Immediately after the Wait for Audio step, add a new node.
  2. From the action list, select Play a Contact Recording.
  3. In the recording field, enter the variable that stores the recording (example: @results.recording).
  4. Save the action.

[CAPTURE: Play a Contact Recording action with a flow variable entered as the audio source.]

⚙️
Technical Detail: Only recordings collected by a Wait for Audio action can be replayed. Messaging flows do not support voice recordings.

3
Confirm or re-record (recommended branching pattern)

Goal: Decide what happens after playback (confirm, redo, escalate, or end).

Common options include:

  • Ask the caller to confirm the recording.
  • Give the caller the option to re-record their message.
  • Forward the call to an agent for review (when appropriate).
  • End the call with a short confirmation message.

[CAPTURE: Flow branch showing playback followed by an IVR menu with “Confirm” and “Re-record” options.]

💡
Tip: Combine Play a Contact Recording with Wait for Menu Selection so callers can press a key to confirm or redo their recording.

Common Issues & Quick Fixes

The recording does not play back

Cause: The referenced variable does not exist, or it was not created by a Wait for Audio action.

Fix:

  • Ensure a Wait for Audio action runs before the playback step.
  • Confirm the result name matches exactly (including spelling): @results.<result_name>.
I can’t select a recording to play

Cause: The flow does not contain any Wait for Audio steps.

Fix:

  • Add a Wait for Audio action earlier in the flow.
  • Assign a result name so the recording can be referenced later.
Callers hear silence instead of their recording

Cause: The caller did not leave a recording, or the recording step was skipped by the flow logic.

Fix:

  • Verify your routing always passes through Wait for Audio before playback.
  • Replay only after a successful recording path (avoid jumping directly to playback from other branches).
I want the caller to re-record their message

Cause: The flow does not loop back to the recording step after playback.

Fix:

  • After replaying the recording, add Wait for Menu Selection with choices like “1 = Confirm” and “2 = Re-record”.
  • Route “Re-record” back to the original Wait for Audio step.