Flow level override of contact centre recording policy
Verified 2026-09-05 · 22 claims · sources tier 2 · 1 disputed
Also known as Continue On Transfer, Purge Recordings Policy Control, Recording Control activity, recording consent.
Webex Contact Center documents call-recording enablement as configurable at 3 named levels: tenant, queue, and recording schedule 12. Setting the consent configuration within a flow provides direct control over whether a call is recorded 65.
Flow precedence and configuration levels
In the field, the Recording Control activity's own documentation never uses the word override, stating instead that priority is given to the user consent setting in the flow 3. Setting the flow's consent configuration to Yes records the call regardless of the configuration set at tenant, queue, or recording schedule level 6. Setting the flow's consent configuration to No means the call is not recorded regardless of the configuration set at tenant, queue or recording schedule level 5. When consent is not configured in the flow, a Yes at any 1 of the tenant, queue, or recording schedule levels records the call 13.
Sources disagree, however, as the recording-schedules article states an ordered resolution where a matching active schedule decides, and Contact Center evaluates queue settings and then tenant settings only when no schedule matches 11.
Scope of flow-level precedence
The flow-level precedence covers only the decision whether to record 9. Continue On Transfer, Pause Resume Enabled, and Pause Duration continue to follow the tenant, queue, and recording schedule hierarchy 9.
Consent reporting and activity outputs
Whether a recording consent decision is ever reportable is a flow-design choice, with Cisco directing authors to use a global variable to generate a consent report and a local variable when they do not want to capture it 4. The Recording Control activity has no output variables of its own, meaning nothing emitted by the activity itself can be hooked to a record of the decision 2. Furthermore, neither the recording-schedules article nor the retention and purge article contains the word audit or the word log anywhere in its body 8.
Retention and boundary behaviors
Neither article states what happens to an in-progress recording when a recording schedule's time window ends while the call is still active 10. Additionally, neither article states whether a recording created because the flow forced recording on—against a tenant, queue, or schedule setting of No—is retained or purged any differently from an ordinarily authorised recording 7.
See also
See also The Webex Contact Center Flow Designer activity set.
See also Who can change a recording and what happens at a transfer.
See also Webex Contact Center recording and contact data retention.
See also What the Control Hub administrator activity log records.
See also Agent and supervisor recording controls in Webex Contact Center.
See also What a transfer does to a recording a transcript and a summary.
Applicability
Across the claims in this article, the evidence covers Cisco Webex Contact Center, verified as of 2026-09-05. The deployment model is not covered by any claim in this article.
What remains uncertain
Sources disagree on which of the two stated recording precedence rules governs when resolving tenant, queue, and schedule levels 1113. Neither article states what happens to an in-progress recording when the schedule window closes while a call remains active 10. Whether any Control Hub article documents an audit log for recording policy is not covered by any claim in this article. Whether a supervisor can start or stop recording live during a call is not covered by any claim in this article. Whether Continue On Transfer and Stop recording on transferred calls are one control is not covered by any claim in this article.
See also
Governs
- Webex Contact Center recording and contact data retention — A recording must exist before a retention policy can apply to it
Part of
- The Webex Contact Center Flow Designer activity set — The Recording Control activity sits in the Flow Designer activity set
Referenced by
- What a transferred call leaves behind across Cisco products — Whether a transfer artefact exists at all is decided by the recording policy layers
- The Webex Contact Center Flow Designer activity set — The activity that overrides recording policy
- Agent and supervisor recording controls in Webex Contact Center — The agent-facing end of the recording policy layers
- Who can change a recording and what happens at a transfer — The precedence chain and the reserved state
- What a transfer does to a recording a transcript and a summary — Where the decision to record is made
- What the Control Hub administrator activity log records — Whether a policy change is recorded
Claims
| # | Claim | Status | Confidence | Verified |
|---|---|---|---|---|
| 1 | The word audit does not appear anywhere in the Flow Designer article, which describes no audit trail for any outbound call, for any change to an egress configuration, or for any use of the decrypt control. Build and manage flows with Flow Designer · Whole document, full-text search of the extracted text | fact | 0.90 | 2026-09-05 |
| 2 | The Recording Control activity has no output variables of its own, so nothing the activity itself emits can be hooked to a record of the decision. Build and manage flows with Flow Designer · Recording Control > Output Variables | fact | 0.90 | 2026-09-05 |
| 3 | The Recording Control activity's own documentation never uses the word override; it says priority is given to the user consent setting in the flow. Build and manage flows with Flow Designer · Recording Control section, note after the configuration steps | field-pattern | 0.90 | 2026-09-05 |
| 4 | Whether a recording consent decision is ever reportable is a flow-design choice: Cisco directs authors to use a global variable to generate a consent report and a local variable when they do not want to capture it. Build and manage flows with Flow Designer · Recording Control, second paragraph | fact | 0.90 | 2026-09-05 |
| 5 | Setting the flow's consent configuration to No means the call is not recorded regardless of the configuration set at tenant, queue or recording schedule level. Build and manage flows with Flow Designer · Recording Control, scenario list, item 2 | fact | 0.90 | 2026-09-05 |
| 6 | Setting the flow's consent configuration to Yes records the call regardless of the configuration set at tenant, queue or recording schedule level. Build and manage flows with Flow Designer · Recording Control, scenario list, item 1 | fact | 0.90 | 2026-09-05 |
| 7 | Neither article states whether a recording created because the flow forced recording on, against a tenant, queue or schedule setting of No, is retained or purged any differently from an ordinarily authorised recording. Manage Retention and Purge Recordings and Transcripts in Webex Contact Center · Whole document; the recording-schedules article read in full for the same question | fact | 0.90 | 2026-09-05 |
| 8 | Neither the recording-schedules article nor the retention and purge article contains the word audit or the word log anywhere in its body. Manage call recording schedules · Whole document, full-text search; the same search run against the retention and purge article | fact | 0.90 | 2026-09-05 |
| 9 | The flow-level precedence covers only the decision whether to record; Continue On Transfer, Pause Resume Enabled and Pause Duration continue to follow the tenant, queue and recording schedule hierarchy. Build and manage flows with Flow Designer · Recording Control, paragraph after the scenario list | fact | 0.90 | 2026-09-05 |
| 10 | Neither article states what happens to an in-progress recording when a recording schedule's time window ends while the call is still active. Manage call recording schedules · Duration settings section; Recording Control section of the Flow Designer article | fact | 0.90 | 2026-09-05 |
| 11 | The recording-schedules article states an ordered resolution: a matching active schedule decides, and only when no schedule matches does Contact Center evaluate queue settings and then tenant settings. Manage call recording schedules · Step 7 preamble, immediately before the Recording details table | disputed | 0.60 | 2026-09-05 |
| 12 | Webex Contact Center documents call-recording enablement as configurable at 3 named levels: tenant, queue and recording schedule. Manage call recording schedules · Introductory paragraph | fact | 0.90 | 2026-09-05 |
| 13 | When consent is not configured in the flow, a Yes at any one of the tenant, queue or recording schedule levels records the call. Build and manage flows with Flow Designer · Recording Control, scenario list, item 3 | fact | 0.90 | 2026-09-05 |
| 14 | The strongest candidate for the setting that governs recording through a blind transfer is Continue On Transfer, named in Flow Designer at tenant, queue or recording schedule level. Build and manage flows with Flow Designer · Recording Control, final paragraph before Output Variables; compared against the recording-schedules reserved-state sentence | inference | 0.60 | 2026-09-05 |
| 15 | No source in the corpus defines what organization level means for a Webex Contact Center recording setting, and no source names the setting that decides whether recording continues through the reserved state of a blind transfer. Manage call recording schedules · Note block preceding Create a call recording schedule; searched across the Flow Designer, recording schedules and agent states articles | fact | 0.90 | 2026-09-05 |
| 16 | Cisco states that a matching recording schedule determines whether a call is recorded, and that where no schedule matches, Webex Contact Center evaluates the queue-level settings and then the tenant-level settings. Manage call recording schedules · Manage call recording schedules, Recording details step | fact | 0.90 | 2026-09-05 |
| 17 | Cisco states that where flow-level Recording Control is used, the flow-level configuration overrides the recording settings in Control Hub. Manage call recording schedules · Manage call recording schedules, opening section | fact | 0.90 | 2026-09-05 |
| 18 | The recording precedence runs 4 levels deep: a flow's Recording Control, then a recording schedule, then queue level, then tenant level. Manage call recording schedules · Manage call recording schedules, the opening section composed with the Recording details step | inference | 0.60 | 2026-09-05 |
| 19 | Cisco states that on a blind transfer the receiving agent enters a reserved state briefly and that, depending on the settings configured at each organization level, call recording can either continue or stop at that point. Manage call recording schedules · Manage call recording schedules, blind transfer and reserved state paragraph | fact | 0.90 | 2026-09-05 |
| 20 | A recording schedule carries a setting named Stop recording on transferred calls, which stops recording when an agent transfers a call. Manage call recording schedules · Manage call recording schedules, schedule settings table | fact | 0.90 | 2026-09-05 |
| 21 | Manual deletion of a voice recording or transcript is logged for auditing with 4 fields: who deleted it, when, the reason, and any notes provided. Manage Interaction History · Key Capabilities, Deletion Reason and Audit Trail | fact | 0.90 | 2026-09-05 |
| 22 | During a blind transfer the receiving agent briefly enters a reserved state, and whether recording continues or stops at that point depends on settings configured at organization level. Manage call recording schedules · Note block, bullet 3, nested sub-bullet 1 | fact | 0.90 | 2026-09-05 |
Sources
Build and manage flows with Flow Designer
Manage call recording schedules
Manage Interaction History
Manage Retention and Purge Recordings and Transcripts in Webex Contact Center
Cite this page
APA
WarmTransfer. (2026, September 5). Flow level override of contact centre recording policy. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-recording-policy-override
BibTeX
@misc{warmtransfer-wxcc-recording-policy-override,
title = {Flow level override of contact centre recording policy},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/wxcc-recording-policy-override},
note = {Verified 2026-09-05}
}