Record calls, with the consent question answered first.

Recording is easy to switch on and easy to get wrong. The audio is the simple half. Who may listen to it, how long it is kept and whether the person on the other end was told are the half that gets people into trouble.

What the call does

  1. inCall in progress
  2. step 1Recording
  3. answeredStored and access-controlled
Call recording: Call in progress → Recording → Stored and access-controlled.

Three modes, chosen per line or per queue

Recording is a property of the thing being recorded, so you can record the sales queue and not the owner's extension.

  • Always: every call on this line or queue
  • On demand: the person on the call starts and stops it
  • Off, and the interface says so rather than leaving it ambiguous

An announcement you can require

You can require a recording announcement before the call connects, per site. Whether you must play one depends on where the caller is, and that is a question for your own counsel, not something a settings page should decide for you.

Retention is stated, and deletion is real

The retention period is shown in the interface next to the recordings, not buried in a knowledge base. When a recording is deleted, the interface tells you what is being destroyed before you confirm.

Simple by default, detailed when you ask

Most people never open the second column. It is one click away rather than spread across the first.

Simple mode

  • A single control per line or queue: always, on demand, or off
  • Playback and download from the call record, restricted to roles you grant

Advanced mode

  • Retention policies per site
  • Pause during payment capture
  • Export to your own storage

On every plan

This is included whichever plan you are on, with no add-on and no module to enable. Plans differ by how calls are distributed and how long the history is kept.