Classic WFM and New WFM variants of Webex Workforce Optimization

Verified 2026-09-15 · 37 claims · sources tier 2

Also known as CWFM, Calabrio ONE, Classic WFM, New WFM, Smart Desktop, TWFM, product activation key, state groups.

Cisco maintains 2 parallel documentation sets for Webex Workforce Optimization: 1 for Classic WFM and 1 for New WFM 33. Both guide sets cover user guides, API references, installation guides, and data import and export references 33.

Documentation and variant maintenance

The Classic WFM guide set was first published on 10 July 2020 4. The New WFM guide set was first published on 20 July 2021 15. Both variant guide sets were updated in September or October 2025, and neither guide set is marked superseded or withdrawn 2.

WarmTransfer's reading of the sources is that the variant split affects the workforce management layer only, while quality management, analytics, recording, and Insights are documented in common across both guide sets 36. Despite this shared scope, the New WFM user guide runs to 2588 pages compared to 1050 pages for the Classic WFM user guide 16. Insights is documented extensively in the New WFM user guide and barely at all in the Classic WFM user guide, which accounts for much of the difference in length 9. As a result, a Webex Workforce Optimization Classic customer who licenses Insights has no authoring reference for it in their own Classic user guide 10.

Differences also appear in other manuals across the two sets:

• The Classic WFM API reference contains 336 pages, whereas the New WFM API reference contains 210 pages 3. WarmTransfer's reading of the sources is that the New WFM API reference does not document the workforce management REST APIs that the Classic WFM API reference documents 17.
• The New WFM data import and export reference was last updated in October 2024 and is the only guide in either set whose last update predates 2025 14.
• The documentation set contains a Webex Contact Center integration guide for New WFM, but no Classic WFM counterpart was found 24.
• Neither Webex WFO design guide defines New WFM, as the phrase occurs only once in each document in the title 11. WarmTransfer's reading of the sources is that the 2 design guides are distinguished by their titles and by nothing in their bodies, each naming its variant once on the cover while describing the same architecture thereafter 8. In the field, each design guide calls itself something different in its own body from what its cover and its hosting article call it 6.

In the field, Webex WFO guide PDFs are served from a CloudFront address embedded in the help centre article rather than from cisco.com or help.webex.com, and they cannot be reached by guessing a URL 7. In the field, a help.webex.com article can return a correct title and description while serving the wrong document, so the title element is necessary but not sufficient to establish what a page contains 32. For example, the article titled Webex WFO Cloud Design Guide names no variant and serves the Webex WFO Design Guide For Deployments with Classic WFM 5. In addition, the article titled Webex WFO Data Import/Export Reference Guide for Deployments with Classic WFM serves an unrelated document, the Webex WFO Webhook Change Real-Time Adherence Reconfiguration Guide, first published in June 2026 34. WarmTransfer's reading of the sources is that this misfiled webhook reconfiguration guide describes New WFM rather than Classic WFM because its procedure is built on state groups and ungrouped states, which appear only in the New WFM user guide 35.

Functional differences

The workforce management standard report catalogues of the 2 variants share no report name in common 37. The New WFM guide lists reports such as Abandonment and Speed of Answer and Absence Time per Absence, while the Classic WFM guide lists Agent Interval, Agent Overtime, and Agent Report Card 37.

Real-time adherence terminology also diverges: state groups and ungrouped states are New WFM concepts that occur throughout the New WFM user guide and do not appear in the Classic WFM user guide 28.

User administration and permissions operate under different architectures:

• The New WFM deployment carries 2 separate user directories with no automatic user synchronisation between the applications 23.
• WarmTransfer's reading of the sources is that the New WFM deployment carries 2 permission systems where the Classic WFM deployment carries 1 22.

Teleopti references differ between the two variants:

• The New WFM user guide documents a readiness check for moving from Cisco Teleopti WFM to New Cisco WFM 21.
• The New WFM API reference states that its historical APIs support current and new versions of WFM, naming TWFM alongside New WFM 13.
• Teleopti appears in both variant user guides under different roles: the New WFM guide documents a migration from Cisco Teleopti WFM into New WFM, while the Classic WFM guide documents configuring a link to a separate Teleopti site 29.

Licensing and platform architecture

New WFM licensing is enforced through a product activation key that an administrator manages inside the application 1. Licensing for quality management, analytics, and Insights is documented separately from workforce management licensing in the New WFM guide 26. Under New WFM:

• The Cisco WFM application issues a warning when the number of named agents is exceeded, and the system stops working when the number of active agents exceeds the limit defined in the product activation key 19.
• Cisco states that the New WFM active agent limit might include a grace percentage without publishing the percentage 18.
• The application issues a warning 15 days before a product activation key expires, and the product stops working if the key expires 20.

In the field, the installers, services, file paths, and configuration fields of Webex WFO carry the Calabrio product name throughout 25.

For recorded interactions and media:

• In cloud deployments, only the tenant controls the keys that encrypt recordings, and a second layer of encryption is embedded in the product that Cisco's own cloud operations cannot access either 30.
• The desktop client captures calls by reading network traffic on the agent's computer and requires the network interface to support promiscuous mode 27.
• Data moved to third-party storage at the end of its retention period is purged from Webex WFO and can only be reviewed with other applications 31.
• Neither design guide addresses what happens to a recording across a transfer, a consult, or a conference: every occurrence of the word "transfer" is the phrase "data transfer", and the word "conference" occurs 0 times across both documents 12.

See also

See also Help centre articles that serve the wrong document.
See also Webex Contact Center Analyzer and the legacy reporting split.
See also Webex Contact Center Functions as a development platform.
See also Webex Contact Center platform generations and predecessors.
See also Webex Contact Center Enterprise as a distinct product.
See also Webex Engage as the digital channel product.
See also Webex Workforce Optimization and quality management.
See also How Webex WFO records a Webex Contact Center interaction.
See also Transition from Classic WFM to New WFM.
See also The New WFM workforce management API surface.
See also Failure and rollback behaviour of the Classic to New WFM transition.
See also Webex WFO role based operational documentation on wfohelp.com.
See also Webex Contact Center Enterprise add-on ecosystem.

Applicability

Across the claims in this article, the evidence covers Cisco Webex Workforce Optimization and Cisco Webex WFO across cloud deployments, verified as of 2026-09-15. The design guides state cloud deployment applicability for tenant encryption keys, where only the tenant controls the keys encrypting recordings 30.

What remains uncertain

Whether a customer can migrate from Classic WFM to New WFM is not covered by any claim in this article. Concrete scheduling and forecasting differences between the variants are not covered by any claim in this article. Which variant a new customer receives is not covered by any claim in this article. The New WFM workforce management API surface is not covered by any claim in this article. The Manage WFM integrations section is not covered by any claim in this article. How Classic WFM enforces its licence is not covered by any claim in this article. How many other help centre articles serve the wrong document is not covered by any claim in this article. Where a Classic WFM customer finds Insights documentation is not covered by any claim in this article.

WarmTransfer. (2026, September 15). Classic WFM and New WFM variants of Webex Workforce Optimization. WarmTransfer. https://warmtransfer.net/knowledge/webex-wfo-classic-vs-new-wfm

@misc{warmtransfer-webex-wfo-classic-vs-new-wfm,
  title  = {Classic WFM and New WFM variants of Webex Workforce Optimization},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/webex-wfo-classic-vs-new-wfm},
  note   = {Verified 2026-09-15}
}