DTMF Muting vs the Mute Recording button: when each wins

VICIdial gives you two ways to keep part of a call out of the recording. One is automatic: the system mutes the audio when it detects a keypad tone. The other is manual: the agent clicks a Mute Recording button when they want silence. They solve the same broad problem from opposite directions, and you cannot run both on one campaign, so it helps to know which fits your work.

The automatic route: DTMF muting

Recording DTMF Muting blanks the recording for a set number of seconds after the first keypad tone is detected, with no agent action required. It needs the Allow Recording DTMF Detection system setting on, then a non-zero second value on the campaign. This is the right tool when the sensitive part of the call is something the customer types, like a card number. The customer keys their digits, the DTMF tones trigger the mute, and the file is clean without anyone remembering to do anything.

The strength of DTMF muting is that it does not rely on the agent. It fires the instant a tone is heard, so there is no window where digits slip into the file because someone was slow on the button. The limit is that the mute is a fixed length and only triggers on tones. It will not help with a card number a customer reads aloud, because spoken digits make no keypad tone.

The agent-driven route: the Mute Recording button

When enabled, the Mute Recording button shows on the agent screen below the existing recording button. The agent clicks it to mute, and the recording records silence or pauses until they click it a second time to resume. This is the right tool when a human has to judge the moment, such as a customer reading sensitive details aloud or sharing something off-topic that should not be kept. The agent controls both the start and the end. One guardrail: do not leave a recording muted for more than fifteen minutes at a stretch.

Why you pick one, not both

flowchart TD
  A[What needs hiding] --> B{Customer types digits}
  B -->|Yes| C[Use DTMF muting]
  B -->|No| D{Agent must judge the moment}
  D -->|Yes| E[Use Mute Recording button]
  C --> F[Enable on campaign]
  F --> G[Mute button auto disabled]
  E --> H[Agent controls start and stop]

The choice is partly made for you. Turning on Recording DTMF Muting for a campaign automatically disables the Mute Recording button on that campaign. They are not designed to coexist, so each campaign runs one model. Decide based on what you are protecting: tone-triggered muting for keyed input like payments, the agent-clicked button for anything an agent has to mute by ear and judgment.

Many floors split this across campaigns. A payments Campaign runs automatic DTMF muting so card tones never reach the file, while a general support campaign keeps the agent-clicked button for the occasional sensitive aside. For how to add the button itself, see how to add the Mute Recording button, and for the automatic side read our call recording guide.

Either way, keeping audio you should not store out of the file is a basic part of running clean recordings. If you would rather have it configured correctly from day one, check our pricing to see how fast you can be running.