What Recording Delay does and why it cuts short clips

Recording Delay is a per-campaign setting that holds off the start of automatic recording for a fixed number of seconds. If a call ends before that timer runs out, no recording file is ever written. It exists for one reason: a lot of auto-dialed calls die in the first few seconds, and you do not want a recording for every one of them.

What the setting actually does

The Recording delay field takes a number of seconds and delays the start of recording on every call by that amount. The default is 0, which means recording starts immediately. Set it to 10 and the recorder waits ten seconds before it begins capturing audio. If the call is gone before then, nothing lands on disk. It only applies when Call recording is running automatically, so it works with ALLCALLS and ALLFORCE recording modes and not with on-demand recording that an agent starts by hand.

The reason short calls pile up is simple. On an auto-dial campaign you reach a lot of answering machines and a lot of people who pick up and hang up. An AMD (answering machine detection) result or a quick no-thanks both produce a recording you will almost never listen to. Each of those files still costs disk space and still costs CPU to encode. Multiply that across thousands of dials a day and the waste is real.

How the timer decides

flowchart TD
  A[Call sent to agent] --> B[Recording Delay timer starts]
  B --> C{Call still up after N seconds}
  C -->|No| D[No file written]
  C -->|Yes| E[Recording begins]
  E --> F[Audio captured to disk]
  D --> G[Disk and load saved]

Think of the delay as a filter on the front of the recorder. The call connects, the agent screen comes up, and a quiet timer runs in the background. Cross the line and you get a normal recording from that point forward. Fall short and the system simply never opens a file. The trade-off is that you lose the first few seconds of the calls that do record, so do not set the delay so high that you cut off the opening of real conversations.

Picking a value

A delay of 10 seconds is a sensible starting point for most outbound campaigns. It clears out the bulk of machine answers and instant hangups while keeping nearly every genuine call intact. If your floor relies on hearing the agent's greeting for quality scoring, drop it to 5 or test what your reviewers actually need. If you record purely for compliance on completed sales, you can push it higher.

One gotcha: the delay interacts with other features. Routing Initiated Recording, which lets the call routing script trigger recording instead of the agent screen, will only fire on manual dialed calls when the recording delay is set to 0. If you depend on that path and also want a delay, you have a conflict to resolve before you turn both on. For the bigger picture on how recording modes fit together, read our guide to VICIdial call recording.

If your goal is mainly to stop recording very short calls rather than to understand the mechanism, we wrote a focused walkthrough on skipping recordings of short calls that covers the exact steps. Either way, a small delay is one of the cheapest wins for keeping recording storage under control.

Want a dialer where these settings are already tuned and the disk math is handled for you? See our pricing to see what a managed setup looks like.