Skip to content

Ringfully is now Inbound CX What’s new

Type a word or two. Press Escape to close.

Legal

Call recording

How recording works, what the default is when nobody configures it, and whose job consent is.

Last updated August 30, 2026.

Draft: not yet in force. Inbound CX does not yet have an incorporated legal entity, so the party, address and governing law below read [TBD]. This document is published for review and does not bind anyone until those are filled in and it has been through a lawyer.

Two things on this page will matter more than the rest: an organization that has never configured a policy does not record, because the default is off, and once recording is on the announcement is spoken before the caller is connected in always mode but only once an agent has started recording in the agent’s-choice mode. Clauses 2 and 3.

1How recording works

Recording is set per organization, not per person. An administrator picks one of three modes:

Always
Every answered call records automatically, inbound and outbound.
The agent’s choice
Agents with the right permission start and stop recording on a call themselves. An administrator can separately decide whether an agent is allowed to stop one that is already running.
Never
Recording is off and the control is hidden.

Recordings are dual-channel: each side of the conversation on its own track. The audio is held by Twilio; we store a reference to it and stream it on demand. Permission to play a recording back is separate from permission to start one, so an agent who can record is not automatically an agent who can listen to everyone else’s calls.

2The default is off

An organization that has never configured a recording policy does not record. Recording stays off until an administrator sets a mode, and while it is off nobody can start a recording on a call, whatever permission they hold.

This is deliberate. Since 30 August 2026 recording is something an organization turns on rather than something it has to turn off, and every account that already existed was switched off at the same time. So “we never set it up” and “we do not record” are now the same thing. If you want recording, set the mode to always or to the agent’s choice.

3The recording announcement, and when it is spoken

Each organization stores an announcement to be spoken to the other party on a recorded call, and it is spoken on the call. Recording cannot be turned on without one. Setting any mode other than never is refused while the announcement is empty, so there is no way to switch recording on and leave nothing to say. If a policy reaches a call blank anyway, we speak a default line in English and French rather than recording in silence. We do not write your announcement for you, and that default is a backstop, not a notice written for your business.

When it is spoken depends on the mode. In always mode the caller hears it before they are connected, which is the last moment anything can be said off the recording: the conference they join is recorded from its first second. In the agent’s-choice mode nothing is said at the start, because at that point nobody knows whether there will be a recording at all. The announcement is played into the call when an agent starts recording, which puts it just after the recording begins rather than just before. Everyone on the call hears it, your own people included.

If the announcement cannot be resolved or played, the call still connects and any recording still runs. We log it, but the other party heard no notice. A stored announcement is therefore a notice we speak, not proof that a particular person heard one.

So: if you are recording in a jurisdiction that requires notice, store an announcement; use always rather than the agent’s choice if the notice has to precede every recorded second; and brief your agents to say it out loud as well. A person saying “this call is being recorded” is the one notice that does not depend on us.

5Where recordings live, and for how long

The audio is stored by Twilio rather than by us. Playback streams through our servers so we can check the listener’s permission first, which is why a recording URL is not something that can be forwarded to someone who should not have it.

Recordings are deleted on a schedule. Each organization sets how long recordings and voicemail are kept, and an organization that sets nothing keeps recordings for 30 days and voicemail for 90. A job runs nightly and deletes what has passed its window. Shortening a window therefore deletes audio on the next run.

A single recording can also be deleted before its window ends. That is a permission of its own, separate from the permission to play a recording back, and an erasure request under the privacy policy reaches the audio the same way.

In each of those cases the audio is erased at Twilio first, and our own record of the recording is marked only once Twilio confirms. There is no archive and no second copy, so a deleted recording is gone for us as well as for you. What stays behind is a note that the recording existed and when it was erased, which is what lets anyone check afterwards that an erasure really happened. Voicemail is transcribed automatically and the transcript is stored as text alongside it. Where an organization has turned on transcripts of recorded calls, that transcript is deleted with the recording it was made from.

6Live monitoring

On the Pro and Business plans, a supervisor whose role allows it can listen to a live call without being heard, speak only to the person answering, or join the call as an ordinary participant. Listening is hidden from the person answering; a supervisor who speaks only to them is shown on the call as a supervisor only they can hear, and one who joins is shown like anyone else. Calls between colleagues and calls to emergency numbers are never monitored, and each time a supervisor starts, changes or leaves one of these sessions it is written to the organization’s audit log.

7Questions

Write to sales@inboundcx.com. Clause 7 of the terms of service carries the contractual version of this.