# Who can change a recording and what happens at a transfer

Canonical: https://warmtransfer.net/knowledge/wxcc-flow-designer-recording-control

Last verified: 2026-09-05

Cisco provides settings and flow activities that determine when a call is recorded, paused, or stopped across transfers[^5][^11]. These controls evaluate across multiple administrative layers and behave differently depending on the transfer type and participant actions[^2][^10].

## Precedence and actor capabilities

Cisco states that where flow-level Recording Control is used, the flow-level configuration overrides the recording settings in Control Hub[^5]. Cisco further states that a matching recording schedule determines whether a call is recorded, and where no schedule matches, Webex Contact Center evaluates queue-level settings and then tenant-level settings[^2]. WarmTransfer's reading of the sources is that the recording precedence runs 4 levels deep: a flow's Recording Control, then a recording schedule, then queue level, then tenant level[^9].

WarmTransfer's reading of the sources is that the 3 actors that can affect a recording have different abilities: a flow can force it on or off, an agent can pause and resume but not during a consult, and a supervisor can do neither[^12]. In the field, the pause and resume capability is named 3 different ways across the 2 recording documents, and none of the 3 is cross-referenced to another[^7].

The Recording Control activity in Flow Designer takes a single boolean flow variable and no output variable, and is configured through 1 setting that enables or disables recording for the call[^8]. The Recording Control activity carries no stated placement restriction, whereas the blind transfer and bridged transfer activities in the same catalogue state theirs[^6].

## Transfer behaviors

A recording schedule carries a setting named Stop recording on transferred calls, which stops recording when an agent transfers a call[^11]. 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[^10]. Cisco warns that on blind transfers to a dial number, and on entry point to dial number patterns, the duration of speech and the duration of the recorded call shown in the interface may not match[^3].

On an entry point to dial number call, Cisco records the call during consult and conference and not during other parts of the call[^4].

## See also

See also [Agent and supervisor recording controls in Webex Contact Center](https://warmtransfer.net/knowledge/wxcc-call-recording-controls).
See also [Flow level override of contact centre recording policy](https://warmtransfer.net/knowledge/wxcc-recording-policy-override).
See also [The entry point](https://warmtransfer.net/knowledge/wxcc-entry-point-artefacts).
See also [What happens to a flow when a contact is transferred to an entry point](https://warmtransfer.net/knowledge/wxcc-routing-strategy-reruns).
See also [Webex Contact Center Flow Designer architecture](https://warmtransfer.net/knowledge/webex-cc-flow-designer).
See also [Webex Contact Center queues teams and routing strategies](https://warmtransfer.net/knowledge/webex-cc-routing).
See also [Webex Contact Center Agent Desktop and widgets](https://warmtransfer.net/knowledge/webex-cc-agent-desktop).
See also [Webex Contact Center workforce optimization and recording](https://warmtransfer.net/knowledge/webex-cc-wfo).
See also [Where the Webex Contact Center Record a call article went](https://warmtransfer.net/knowledge/wxcc-recording-njxdvzv-successor).
See also [Webex Contact Center voice channel and PSTN options](https://warmtransfer.net/knowledge/webex-cc-voice-channels).
See also [Webex Contact Center APIs and webhooks](https://warmtransfer.net/knowledge/webex-cc-apis).
See also [Cisco first-party Webex Contact Center repositories](https://warmtransfer.net/knowledge/webex-cc-github-registry).
See also [Webex Connect digital channel flow orchestration](https://warmtransfer.net/knowledge/webex-connect-digital-flows).
See also [Webex Contact Center system limits reference](https://warmtransfer.net/knowledge/webex-cc-system-limits).
See also [Webex Contact Center RONA and agent state handling](https://warmtransfer.net/knowledge/webex-cc-rona-agent-state).
See also [Webex Contact Center holiday and emergency routing overrides](https://warmtransfer.net/knowledge/webex-cc-holiday-emergency-routing).
See also [Pebble template syntax and filters in Flow Designer](https://warmtransfer.net/knowledge/pebble-template-expressions).
See also [Webex Contact Center Voice Services Platform and Voice POP](https://warmtransfer.net/knowledge/webex-cc-voice-services-platform).
See also [Webex Contact Center preview and progressive outbound campaigns](https://warmtransfer.net/knowledge/webex-cc-outbound-campaigns).
See also [Webex Connect Flow Builder node reference](https://warmtransfer.net/knowledge/webex-connect-node-reference).

## Applicability

Applies to: Cisco Webex Contact Center. Sources checked 2026-09-05.

## What remains uncertain

The name of the setting that decides recording at the reserved state is not covered by the sources below. Whether Stop recording on transferred calls and Continue On Transfer are 1 setting is not covered by the sources below. The default recording setting at each of the 4 precedence levels is not covered by the sources below. Whether a consult flow may carry a Recording Control activity is not covered by the sources below.

## Sources

[^1]: Restrictions are stated for some activities and not others: blind transfer is terminal and unsupported for consults, bridged transfer is unsupported in outbound and event flows and for a contact already assigned to an agent, and most activities state none (field report). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, activity catalogue. Checked 2026-09-05.
[^2]: 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. Source: [Manage call recording schedules](https://help.webex.com/en-us/article/ejatso/Manage-call-recording-schedules), Manage call recording schedules, Recording details step. Checked 2026-09-05.
[^3]: Cisco warns that on blind transfers to a dial number, and on entry point to dial number patterns, the duration of speech and the duration of the recorded call shown in the interface may not match. Source: [Manage call recording schedules](https://help.webex.com/en-us/article/ejatso/Manage-call-recording-schedules), Manage call recording schedules, blind transfer paragraph. Checked 2026-09-05.
[^4]: On an entry point to dial number call, Cisco records the call during consult and conference and not during other parts of the call. Source: [Manage call recording schedules](https://help.webex.com/en-us/article/ejatso/Manage-call-recording-schedules), Manage call recording schedules, entry point to dial number paragraph. Checked 2026-09-05.
[^5]: Cisco states that where flow-level Recording Control is used, the flow-level configuration overrides the recording settings in Control Hub. Source: [Manage call recording schedules](https://help.webex.com/en-us/article/ejatso/Manage-call-recording-schedules), Manage call recording schedules, opening section. Checked 2026-09-05.
[^6]: The Recording Control activity carries no stated placement restriction, where the blind transfer and bridged transfer activities in the same catalogue state theirs. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Recording Control against Blind Transfer and Bridged Transfer. Checked 2026-09-05.
[^7]: The pause and resume capability is named 3 different ways across the 2 recording documents, and none of the 3 is cross-referenced to another (field report). Source: [Manage call recording schedules](https://help.webex.com/en-us/article/ejatso/Manage-call-recording-schedules), Manage call recording schedules and Flow Designer, pause and resume settings. Checked 2026-09-05.
[^8]: The Recording Control activity takes a single boolean flow variable and no output variable, and is configured through one setting that enables or disables recording for the call. Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer, Recording Control activity. Checked 2026-09-05.
[^9]: The recording precedence runs 4 levels deep: a flow's Recording Control, then a recording schedule, then queue level, then tenant level (inferred). Source: [Manage call recording schedules](https://help.webex.com/en-us/article/ejatso/Manage-call-recording-schedules), Manage call recording schedules, the opening section composed with the Recording details step. Checked 2026-09-05.
[^10]: 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. Source: [Manage call recording schedules](https://help.webex.com/en-us/article/ejatso/Manage-call-recording-schedules), Manage call recording schedules, blind transfer and reserved state paragraph. Checked 2026-09-05.
[^11]: A recording schedule carries a setting named Stop recording on transferred calls, which stops recording when an agent transfers a call. Source: [Manage call recording schedules](https://help.webex.com/en-us/article/ejatso/Manage-call-recording-schedules), Manage call recording schedules, schedule settings table. Checked 2026-09-05.
[^12]: The 3 actors that can affect a recording have different abilities: a flow can force it on or off, an agent can pause and resume but not during a consult, and a supervisor can do neither (inferred). Source: [Build and manage flows with Flow Designer](https://help.webex.com/en-us/article/nhovcy4/Build-and-manage-flows-with-Flow-Designer), Flow Designer Recording Control, against the agent desktop and supervisor articles. Checked 2026-09-05.
[^13]: No source names the organization-level setting that decides whether recording continues through a blind transfer's reserved state; Cisco states only that the outcome depends on the settings configured at each organization level. Source: [Manage call recording schedules](https://help.webex.com/en-us/article/ejatso/Manage-call-recording-schedules), Manage call recording schedules, blind transfer and reserved state paragraph. Checked 2026-09-05.