What a consult produces in Webex Calling

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

Also known as Always with pause/resume, Converged Recordings, Dubber Go, On Demand recording, selective call recording.

The Webex Calling recording article never treats a consult as a call operation, mentioning the word consult once in the phrase consult your legal department 12. Cisco AI Assistant supports summaries for 7 named call flows and consult is not among them, while the documentation's troubleshooting guidance instructs a reader whose summary is missing to check whether the call flow is supported 11.

Recording behavior and consults

In the per-user configuration step, the Webex Calling recording article names 4 selectable recording modes—On Demand, Always, Always with pause/resume, and Never—while its overview names only 3 16. Call direction is fixed at call start for the recorded user and does not change when a transfer changes that user's call role, whereas call source is based on the actual remote party and can be rechecked when the remote party changes 14. WarmTransfer's reading of the sources is that because call source is rechecked when the remote party changes, a consult or transfer that swaps the remote party could move a call across the selective-recording boundary in mid-call 24.

When the selected direction and source do not permit recording, recording is inhibited for that call and the Call Recording Result field in the call detail record shows Inhibited 18. The Webex Calling recording article never states what a pause does to a consult, a transfer, or a conference already in flight, nor whether a pause persists across a transfer 20. Once a compliance announcement has played, announcements are not played again when a midcall operation such as a transfer is initiated on that call 10.

When a call is being recorded, dual streams are sent to the call recording provider, and announcement events are signalled to that provider as SIPREC metadata 15. Webex-provider recordings in Webex Calling are configured with a retention period of 1 year and 100 GB of storage per organisation, while the free Dubber Go tier stores each recording for 30 days 30.

Transcripts and AI summaries

A Webex Calling transcript is available only for calls recorded by the Webex call recording provider and only when the call is in English, and it is viewed inside the recording player 31. Speaker identification in a Webex Calling transcript is not supported for FedRAMP 25.

WarmTransfer's reading of the sources is that recording and Cisco AI Assistant summarisation in Webex Calling are separate pipelines, on the evidence of 4 independent divergences in retention, administrative surface, access, and timing 22. Cisco AI Assistant can generate a summary for a call that is still in progress, so a summary can exist before any recording file does 17. Furthermore, Cisco AI Assistant summaries are not supported for shared lines or virtual lines, while Webex Calling recording documents virtual lines at length and gives shared lines an inheritance rule 26.

Reporting metrics

The Customer Assist Queue Call Details report carries a conference time column and no consult column, and handle time is captured when the agent ends or transfers the call 21. In Webex Contact Center records, consult to entry point carries its own count and duration pair in the Customer Session Record only, whereas the consult to queue pair appears in the customer session, agent session, and queue records alike 36.

See also

See also What a transferred call leaves behind across Cisco products. See also Webex Calling Customer Assist as a product. See also What Cisco AI voice features retain of call audio and transcripts. See also The transcript and AI summary attached to a Webex Calling recording. See also Records and fields that represent a consult or a transfer. See also AI-generated summaries for call recordings in Webex App. See also What the Webex Calling detailed call history records. See also What an agent can do on a call and what the desktop withdraws. See also The Queue Record and what a queue counts at a transfer. See also What the Customer Session Record carries. See also Webex Calling architecture and deployment models. See also Webex Calling Dedicated Instance applicability. See also Webex Calling PSTN options and selection. See also Webex Calling locations and number management. See also Webex Calling Site Survivability Gateway. See also Webex Calling supported devices and MPP firmware. See also Webex Calling license types and entitlements. See also Webex Calling administration APIs and scopes. See also Webex Calling calling features and feature parity vs UCM. See also Webex for Government calling restrictions.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Calling, Cisco Webex Calling Customer Assist, and Cisco Webex Contact Center, verified as of 2026-09-05. The deployment model is not covered by any claim in this article. Speaker identification in transcripts is excluded from FedRAMP 25.

What remains uncertain

The following items are not covered by any claim in this article:

• The article on playing a recording with a transcript and AI summary is not covered by any claim in this article.
• Whether a consult produces a call detail record leg is not covered by any claim in this article.
• The Webex Calling retention policy article is not covered by any claim in this article.
• What happens to the dual stream when a third party joins is not covered by any claim in this article.

WarmTransfer. (2026, September 15). What a consult produces in Webex Calling. WarmTransfer. https://warmtransfer.net/knowledge/webex-calling-consult-artefacts

@misc{warmtransfer-webex-calling-consult-artefacts,
  title  = {What a consult produces in Webex Calling},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-calling-consult-artefacts},
  note   = {Verified 2026-09-15}
}