How to record every call on a campaign

If you want every call on a campaign recorded, the one thing to avoid is depending on the agent to press a button. The default recording mode is manual, which means a forgotten click equals a missing recording. To guarantee full coverage you switch the campaign to an automatic mode and let the dialer start capture on its own. Here is how to do that and how to confirm it worked.

Set the campaign to an automatic mode

Open the Campaign and find the Campaign Recording menu. The default is ONDEMAND, which only records when the agent chooses to. Change it to ALLCALLS, which starts Call recording automatically whenever a call is sent to an agent. With ALLCALLS, every call is recorded by default, though an agent can still stop a recording if they have to pause for sensitive details. If you do not want agents to be able to stop recording at all, choose ALLFORCE instead, which records every call and removes the stop control entirely.

That single menu change is what flips a campaign from optional capture to full capture. Save the campaign and the new behavior takes effect for calls routed after the change. There is no separate enable switch and no server restart needed for the mode itself. Keep in mind the change is per campaign, so if you run the same agents across several campaigns, each one needs its own setting. A team can easily end up with one campaign on ALLCALLS and another still on the ONDEMAND default, which is a common reason recordings appear to be missing for only some calls.

Trim the junk with a recording delay

Recording every call sounds clean until you see how many of those calls are answering machines and instant hangups. Both ALLCALLS and ALLFORCE support a Recording delay that holds off the start of recording by a set number of seconds. The default is zero. Setting it to around ten seconds drops most of the very short recordings where nobody real was on the line, which keeps your archive tidy and cuts load on the server. Calls that last longer than the delay are still recorded in full from the delay point onward, so real conversations are unaffected.

How full-coverage recording decides each call

flowchart TD
  A[Call sent to agent] --> B[Mode is ALLCALLS or ALLFORCE]
  B --> C{Recording delay elapsed}
  C -->|Not yet| D[Hold off recording]
  D --> C
  C -->|Yes| E[Start recording]
  E --> F{Mode is ALLFORCE}
  F -->|Yes| G[Agent cannot stop]
  F -->|No ALLCALLS| H[Agent may stop if needed]
  G --> I[Save file at end]
  H --> I

The flow is the same for both automatic modes: the call arrives, the delay clears, recording starts, and the only branch is whether the agent can stop it. With ALLFORCE there is no stop; with ALLCALLS there is. Choosing between them is a policy call covered in our ALLFORCE explainer.

Verify full coverage

After the change, run a handful of test calls of different lengths and complete the Disposition on each. Confirm a file exists for every call longer than your delay, and confirm that very short calls are correctly skipped. If a file is missing for a real conversation, your mode is probably still on ONDEMAND or your delay is set too high. The complete walkthrough of storage and filenames lives in our call recording guide.

Full-coverage recording also means planning disk space, which is easy to underestimate. Our hosted plans size storage for the volume you actually run. See the pricing to see what is included.