Webex Contact Center recording and contact data retention

Verified 2026-09-05 · 74 claims · sources tier 2 · 4 disputed

Also known as Jukebox, purge recordings policy.

Webex Contact Center governs the retention and automated purging of voice recordings, transcripts, and operational data through a combination of Control Hub policies and service-level architecture rules 52​43. Organizations configuring these lifecycles must balance legal compliance mandates, storage entitlements, and functional trade-offs introduced by downstream artificial intelligence integrations 47​10.

Control Hub retention policies and purging mechanics

The Webex Contact Center retention period is configured in Control Hub under organization settings and retention policies 52. For voice recordings and transcripts, retention defaults to indefinite for an existing organization until an administrator explicitly sets a duration, whereas for a new organization the default is set to 1095 days 22. An administrator can specify any retention period between 7 and 3600 days 50. Cisco notes that this contact center retention policy control is being progressively rolled out and may not yet be available to all customers 21.

This scheme differs from Webex Meetings retention, which spans 7 to 360 days for standard customers and allows up to 3600 days only with a Pro Pack license 41. Furthermore, setting a data retention policy does not confer a storage entitlement: Cisco states that the 1095-day default applies solely to the retention policy itself, that storage usage is billed separately under the customer's contract, and that customers must review their agreements for storage entitlements and commercial implications 47.

Automated deletion enforces policies by removing the oldest recordings and transcripts first, with any policy change taking effect during the next scheduled purge cycle 45. Cisco states that purging permanently deletes recordings from Webex Contact Center, rendering them completely unrecoverable 48. However, Cisco states that it cannot guarantee purges on the exact scheduled day; execution delays may occur during high system load or internal failure, with unpurged files handled on the next cycle 49.

Sources disagree on whether the primary Control Hub policy applies strictly to audio or spans transcription text as well 53​51. Sources disagree because Cisco states in one document that a single retention period applies to both call recordings and transcripts, whereas the Control Hub retention policies article describes the setting as controlling only how long Webex keeps voice recordings, making no mention of transcripts 53​51.

AI feature constraints and operational lifecycles

Cisco warns that setting a retention duration of 180 days or less may degrade the performance and availability of certain artificial intelligence features, though it does not name which features are impacted 10. In addition to policy limits, Cisco states that enabling artificial intelligence features may limit access to voice transcripts 13. In parallel, the cloud offer disclosure clarifies that Cisco does not use customer content or systems information to train or fine-tune its generative or agentic models 19. That cloud disclosure identifies seven specific generative and agentic AI features, referencing technical notes for each: agent answers and suggested responses, agent burnout detection, auto customer satisfaction, call summaries and handoff to agent, topic analysis, workforce optimization enhancements, and Webex AI Agent 44. Content produced by the AI Agent and AI Assistant follows customer-configured settings while active and is purged within 60 days following contract termination 14.

The cloud offer disclosure defines specific active and post-termination periods across customer content and systems information categories 43​42​18​40​62:

Sources disagree regarding digital interaction transcripts 23​24. Sources disagree because in the main cloud offer disclosure, Cisco states that chat, email, SMS, and social media transcripts are retained for six months via Cisco Engage, with an additional eighteen months available upon request, whereas the standalone Webex Engage offer disclosure states that user-generated content—such as messages, chats, uploaded media, and social posts—is retained for one to eighteen months live and up to twenty-four months in archive depending on configuration 23​24. Webex Engage retains registration data indefinitely until a deletion request triggers obfuscation, archival, and ultimate removal after seven days 30. Engage host and usage data is kept for 180 days after session termination, while audit records are kept for 90 days active and deleted seven days post-termination 31​25. Engage events and telemetry are retained for six months live and two years in archive 27. Engage captures geolocation strictly for live chat when enabled by the customer, and collects Facebook profile pictures and gender only when permitted by individual profile settings 28. WarmTransfer's reading of the sources is that Webex Engage lacks any generative or agentic AI framework, as its offer disclosure contains no artificial intelligence section 29.

Deployment models and subprocessor boundaries

Enterprise customer content—including voice recordings, call transcriptions, screen captures, chat transcripts, and emails—is retained for the entire duration of an active subscription and deleted within 28 days post-termination, rather than relying on Control Hub retention intervals or the cloud offer's 60-day post-termination window 37​32​42. Enterprise systems information rows present ambiguities: events data is listed at 60 days while undefined "other events data" is listed at one year, and calling information is listed at 60 days while telemetry is listed at one year 38. The Enterprise disclosure also mislabels its configuration data termination period by describing it in terms of agent or user information 34. WarmTransfer's reading of the sources is that the Enterprise offer makes no commitment regarding AI model training, as its disclosure lists five AI features without stating whether customer content trains or fine-tunes them 36. WarmTransfer's reading of the sources is that identical category labels represent unaligned data models across architectures, as events data spans 36 months (or configured) in multi-tenant cloud, 60 days plus an undefined tier in Enterprise, and six months live plus two years archive in Engage 17.

Enterprise data centers are situated across Australia, Brazil, Tokyo, the Netherlands, Singapore, the United Kingdom, and the United States (Colorado and Texas) 35. While Amazon Web Services acts as the primary cloud hosting provider for multi-tenant deployments, its Enterprise role is limited to routing administrative email out of a single United States region 33. In the cloud service, Cisco notes that initial subscription records are generated, stored, and processed inside the United States regardless of the ultimate regional deployment 61. The cloud disclosure outlines six broad exceptions allowing cross-border data transfer despite residency settings: out-of-region collaboration, technical support, optional features, Cisco platform registration, ordering data, and mobile push notifications 54. Compliance certifications also dictate storage locations; holding French Health Data Hosting (HDS) certification for EEA-provisioned tenants requires customers to explicitly select an EEA data storage region 39. Cloud certifications include SOC reporting, four ISO standards, PCI-DSS, C5, HIPAA, CSA, and EU Cloud CoC adherence, whereas Engage directs customers to the Cisco Trust Portal under non-disclosure agreements 20​26. Cisco lists Calabrio as an optional cloud subprocessor for workforce optimization, screen, and voice recording storage, with Google, Microsoft Azure, Eleven Labs, Nuance, Deepgram, and Soniox providing transcription, AI, and speech services 16​46.

Contractual commitments and service levels

The Webex Customer Experience Service Level Agreement covers the voice call recording function as a core service, but contains no commitments regarding data durability, retention enforcement, or data loss prevention 56. The agreement applies strictly to orders executed on or after July 31, 2025, for Webex Contact Center under specific part numbers, Webex Connect, and Webex Campaign; it does not govern Webex Contact Center Enterprise or Webex Engage 60.

The SLA establishes availability targets of 99.999 percent on standard tiers and 100 percent on gold tiers over a calendar month, explicitly designating these metrics as targets rather than performance warranties 55. In the event of availability drops, service credits ranging from 5 to 100 percent of monthly committed spend represent the customer's sole and exclusive remedy 57. Root cause analysis objectives for severity-one incidents span ten Cisco business days for standard packages and three business days for gold tiers 59. Outage calculations exclude non-Cisco integrations, beta or trial licenses, user misconfiguration, internet outages, cyberattacks, and force majeure events 58. Finally, Cisco's transfer impact assessment documentation consists of a single-page pointer asserting reliance on EU-US Data Privacy Framework principles and standard contractual clauses; this resource was dated April 17, 2024, leaving it unaligned with the June 2026 offer disclosure cadence 64​65.

Applicability

Across the claims in this article, the evidence covers Webex Contact Center multi-tenant cloud and Cisco-hosted dedicated Enterprise deployments, verified as of 2026-09-05.

The SLA terms cited apply exclusively to orders placed on or after July 31, 2025, for Webex Contact Center under designated part numbers, Webex Connect, and Webex Campaign, and exclude Webex Contact Center Enterprise and Webex Engage 60. Cloud Webex Contact Center compliance with French HDS certification applies exclusively to tenants provisioned and storing data within the European Economic Area 39.

What remains uncertain

WarmTransfer's reading of the sources is that legacy guidance stating a 30-day recording retention default has been superseded by the current 1095-day default and 7-to-3600-day range 11. WarmTransfer's reading of the sources is that draft migration figures—such as thirteen-month CDR retention or a six-month European duration—are not confirmed by current offer disclosures, which mandate one year for CDRs and customer-defined settings for recordings 63. WarmTransfer's reading of the sources is that it cannot be determined whether thirty-six-month historical reporting represents the same data as the thirteen-month Webex Analyzer metric found in migration drafts, as neither source uses the other's terminology 15. Furthermore, WarmTransfer's reading of the sources is that ninety-day AI Agent transcript retention and 180-day debug log lifecycles documented in AI Agent Studio guides are not addressed by current core retention sources 12.

Whether the progressive rollout of the Contact Center retention control in Control Hub has reached all tenants is not covered by any claim in this article. The specific identity of the AI features whose availability or performance degrades when retention is set to 180 days or less is not covered by any claim in this article. Why the Enterprise disclosure uses mislabeled or undefined subcategories for calling, event, and configuration data is not covered by any claim in this article. Whether Cisco plans to update the 2024 transfer impact assessment to match the 2026 disclosure is not covered by any claim in this article.

WarmTransfer. (2026, September 5). Webex Contact Center recording and contact data retention. WarmTransfer. https://warmtransfer.net/knowledge/webex-cc-recording-retention

@misc{warmtransfer-webex-cc-recording-retention,
  title  = {Webex Contact Center recording and contact data retention},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-cc-recording-retention},
  note   = {Verified 2026-09-05}
}