What an agent can do on a call and what the desktop withdraws

Verified 2026-09-15 · 23 claims · sources tier 2 · 1 disputed

Also known as Background Noise Removal, Consult Requested, State Synchronization.

During active handling, an agent can initiate transfers, consults, and conferences, but the desktop disables specific controls and restricts actions depending on state and call conditions 5​1​11. In the field, while call documentation begins by stating that available actions depend on administrator-assigned permissions, the term "permission" does not appear again, as every concrete gate named in the text operates as a desktop profile setting or a Control Hub toggle 9.

Consult and transfer operations

The target lists available to an agent differ depending on the chosen action 3. The consult target list displays agents in both the Available and Idle states, whereas the transfer target list displays only agents in the Available state 3. A call cannot be transferred to an agent who is in Wrap Up 3.

If an agent performs a blind transfer to another agent who does not accept the request, the desktop drops the call, contrasting with an unanswered inbound call that returns to the queue 5. When transferring to an organization contact or collaboration-tool expert, the action requires an administrator to have enabled State Synchronization on the Tenant Settings desktop page, the desktop profile's collaboration section, or both 13. Cisco warns that if voicemail, call forwarding, or call waiting is active on an agent's number and the reroute on no answer timer exceeds the voicemail timer, calls can be routed to voicemail and marked as connected once they reach the telephony layer 12.

When transferring a contact back to an entry point or queue, the system does not connect the contact to the agent who previously handled them 4. In entry point transfers, if a global variable shares a name with one in the receiving flow but has a different data type, the variable is not carried over 6.

Desktop controls and data visibility during consults

During an active consult, the desktop withdraws background noise removal controls, which can only be modified after the consultation concludes 1. The Resume button remains enabled even before the consulted agent accepts the consult request 11.

This is disputed: one numbered step indicates that the Transfer and Conference buttons remain disabled until the consulted agent accepts, yet another statement shortly after notes that the system enables them as soon as the consult call reaches the consulted agent's extension 16.

Data presentation across the two sides of a consultation is asymmetrical 17. The initiating agent's consult popover displays up to 9 variables, whereas the consulted agent's popover displays up to 7 variables 17. Furthermore, the consulted agent cannot edit these variables and cannot see updates without refreshing 17.

Conference management and supervisor monitoring

In a voice conference, only the primary agent is permitted to drop a participant 10. The primary agent is defined as the agent who has been present on the call the longest 10. If the primary agent leaves, the remaining agent who has been present the longest assumes the primary role and gains the ability to drop participants 10. No agent documentation states how many calls an agent can place on hold simultaneously; the only stated concurrency limit is a data center or tenant cap on concurrent calls, and the only stated party limit is 8 conference participants 7.

Desktop restrictions also apply to supervisor interactions and session termination 14​2. A supervisor cannot monitor or barge into a call that is in the wrap up state, though an active monitoring session that is already underway continues into wrap up 14. When the agent being monitored exits the call, the supervisor is dropped unless another agent remains on the call, in which case the supervisor stays on the call regardless of who was originally monitored 15. An agent cannot sign out of the desktop while in an active conversation or during an ongoing monitoring task 2. No agent-facing article states any indicator that informs an agent that a supervisor is silently monitoring their call 8.

See also

• What a supervisor can do and what is recorded of it
• Webex Contact Center RONA and agent state handling
• What a consult produces in Webex Calling
• What a transferred call leaves behind across Cisco products

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 when the Transfer and Conference buttons actually enable during a consult, with documentation stating both that they require acceptance and that they enable upon reaching the extension 16. No agent-facing article states any indicator that tells an agent that a supervisor is listening 8. The specific experience of the customer when a blind transfer is dropped is not covered by any claim in this article. In addition, no agent article states how many calls an agent may hold at once 7.

WarmTransfer. (2026, September 15). What an agent can do on a call and what the desktop withdraws. WarmTransfer. https://warmtransfer.net/knowledge/wxcc-agent-desktop-controls

@misc{warmtransfer-wxcc-agent-desktop-controls,
  title  = {What an agent can do on a call and what the desktop withdraws},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/wxcc-agent-desktop-controls},
  note   = {Verified 2026-09-15}
}