Skip to main content

Call Recordings

Call recordings let your team listen back to phone and browser voice calls inside the same chat view where you already read transcripts. When Call recording is turned on for the workspace, Gravity Rail stores the call audio securely and surfaces a waveform player on each eligible voice chat.

Transcripts are always saved for voice calls, whether or not audio recording is enabled. Recording adds the original audio on top of that transcript — useful for quality review, dispute resolution, and coaching — but it also means the audio can contain protected health information (PHI). Treat recordings with the same care as any other patient data in Gravity Rail.

Before You Can Play a Recording​

RequirementDetails
Workspace settingPhone numbers → Defaults → Call recording must be on. The setting is off by default and applies workspace-wide (not per phone number).
ChannelThe chat must contain a phone or browser voice interaction. Browser voice may appear in a Web Chat that has had a realtime interaction. SMS, email, and text-only web Chats do not get call recordings.
Call completed with audioThe call must have finished and the capture pipeline must have stored audio. Very short or failed calls may have a transcript but no playable file.
AccessYou need permission to open the chat (chats:read). Manager-only chats stay private to their owner.

See Phone defaults for how to turn recording on.

Listen to a Recording​

  1. Open Chats and select a phone call or a Chat with a browser voice interaction.
  2. The Call Recording player sits above the transcript. It is open by default and shows the call's waveform. If no waveform preview is available yet, it starts folded: click the Call Recording heading to open it. Clicking the heading again folds it away without stopping playback.
  3. Press Play. The audio is fetched only now — opening the Chat reads just the waveform preview. Click or drag on the waveform to jump to any point in the call.

The whole transcript stays on screen while the audio plays. The message being spoken is highlighted, and the highlight moves on as the call plays. Click a message while the recording is playing to jump the audio to it. Pause or move back on the waveform if you need to re-hear a specific exchange.

What You Will See​

UI elementMeaning
Call Recording heading above the transcriptThe workspace setting is on and this Chat had a voice call.
Waveform + play controlNormal playback.
Waveform preview unavailableThe preview is not ready (for example, a call that just ended). Play still works.
Preparing the recording…The audio is being fetched, or the call is still in progress.
No recording availableNo audio was stored for this chat (setting was off, call too short, capture error, or retention).
This recording is available but cannot be played.Audio was kept for this chat, but Gravity Rail cannot build a playable file from it (for example, the chat's calls are too long to play here). Trying again will not change this — contact support with the chat ID.
Unable to load this recording.The recording could not be loaded right now (a temporary service or network problem). Try again in a moment.

Phone voicemail messages are separate — they appear under Phone Numbers → Voicemails, not in this chat player.

PHI and Compliance​

Recorded call audio is PHI when the conversation includes patient or member health information. Gravity Rail protects it in several ways:

  • Encryption at rest — audio is stored in encrypted object storage, not in the chat message body.
  • Least-privilege access — only members who can read the chat can request playback; private manager chats stay owner-only.
  • Audit logging — each time someone lists, streams, or downloads recording audio for a chat, Gravity Rail writes a security audit event keyed by chat ID (never by audio content).
  • Lazy load — the player shows only a coarse waveform preview until a reviewer presses Play; the audio is not downloaded before then, which reduces accidental exposure.

Practices for Your Organisation​

  • Limit roles — grant chats:read (and related scopes) only to staff who need to review calls.
  • Disclose recording — many states require two-party consent. Use your phone greeting or voice_require_consent so callers know the call may be recorded before PHI is discussed. See Voice for consent configuration.
  • Retention — follow your organisation's policy for how long call audio should be kept. Gravity Rail stores recordings for operational playback; your compliance team owns retention and deletion procedures.
  • No sharing outside the product — do not export recordings to unsecured channels (personal email, public drives, messaging apps). If you must share internally, use your organisation's approved secure process.

Troubleshooting​

The Call Recording player does not appear​

  • Confirm Call recording is on under Phone numbers → Defaults.
  • Confirm the Chat contains a phone or browser voice interaction, not just text messages.
  • Refresh the page after changing the workspace setting.

"No recording available" but the call happened​

  • Recording was disabled when the call took place (the setting applies to new calls after it is enabled).
  • The call ended before audio could be finalized (abrupt disconnect, provider error).
  • The member does not have access to this chat's recording (rare — usually a permissions issue on a shared inbox).

"This recording is available but cannot be played." or "Unable to load this recording."​

  • Cannot be played means the audio is kept but cannot be turned into a playable file. Refreshing or retrying will not help; contact support with the chat ID (never the transcript or what was said).
  • Unable to load is temporary. Wait a moment, then press Play again or refresh the page.

Playback stutters or fails to start​

  • Check network connectivity — audio streams from the API on demand.
  • Very long calls may take a moment to load; wait for Preparing the recording… to finish.
  • Try another browser if corporate extensions block media fetch.

The highlight does not follow the audio​

  • If no message is highlighted while the audio plays, or clicking a message does not move the audio, the call may have missing timing metadata (e.g. partial capture). The audio and the full transcript are still there; file a support ticket with the chat ID if review is blocked.

Tips​

  • Use recording for coaching, not surveillance. Pair playback with your QA rubric and note chat ID in internal tickets — never paste transcript text or describe PHI in external tools.
  • Transcripts first, audio when needed. Most reviews do not require listening to raw audio; start with the transcript and summary, then press Play only when tone or timing matters.
  • Test after enabling. Place a short test call with synthetic data in dev or staging, then confirm the player appears before rolling out to production members.
  • Phone defaults — Call recording and voicemail detection.
  • Voice — Voice stack, consent, transcripts, and troubleshooting.
  • Phone Voice — Set up telephone calls and answering rules.
  • Web Voice — Browser voice interactions.
  • Chats — Chat states, channels, and the conversation UI.