Cisco Webex for Cisco BroadWorks

Name: Cisco Webex for Cisco BroadWorks
Brand: Cisco
Rating: 4.5 (154 reviews)

Leader

We securely connect everything to make anything possible.

Est 1984|Valuation $449.2B|Raised $49.2B

LinkedIn 7.6M|Website|Web traffic 11.8M|FTEs 95,663|HQ San Jose, California, US

MarketsVoice & Video Calling (VoIP, UCaaS)

Cisco Webex for Cisco BroadWorks screenshot

Published May 16, 2026

01Common complaints

You require direct vendor accountability for PSTN, app, and support without SP variability.
- Webex for BroadWorks relies on the service provider for PSTN and first-line support; provider capabilities materially affect the solution experience.
Your organization is standardized on Microsoft Teams and requires a Teams-native calling UX.
- Teams Phone may provide a more consistent single-client experience when Teams is the established collaboration platform.
Endpoint security policies prevent the Webex desktop client installation/update behavior.
- In environments with strict AppLocker/EDR policies, Webex client behavior has generated support cases in some deployments.
You require built-in, high-fidelity contact center analytics without third-party tools.
- Control Hub reporting may not meet contact-center-grade analytics needs without add-ons.

Reference material and community reports are cited in the Sources section.

1. **You require direct vendor accountability for PSTN, app, and support without SP variability.** - Webex for BroadWorks relies on the service provider for PSTN and first-line support; provider capabilities materially affect the solution experience. 2. **Your organization is standardized on Microsoft Teams and requires a Teams-native calling UX.** - Teams Phone may provide a more consistent single-client experience when Teams is the established collaboration platform. 3. **Endpoint security policies prevent the Webex desktop client installation/update behavior.** - In environments with strict AppLocker/EDR policies, Webex client behavior has generated support cases in some deployments. 4. **You require built-in, high-fidelity contact center analytics without third-party tools.** - Control Hub reporting may not meet contact-center-grade analytics needs without add-ons. Reference material and community reports are cited in the Sources section.

Deal disqualifiers (poor fit)

Organizations that mandate a single client and are standardized on Microsoft Teams without willingness to adopt additional clients.
Environments with tightly restricted endpoint controls where the Webex client install/update behavior conflicts with policies.
Organizations that require deep, built-in contact center analytics without third-party tooling.

Evidence: Community and review references documented in the Sources section.

Vendor-documented limitations

The Webex web client does not include full calling features in the Webex for BroadWorks context.

Source:

https://help.webex.com/article/no4dlj3

Operational limitations surfaced by community

Version and update management can block logins or functionality in some enterprise rollout patterns if clients are out of date and update paths are restricted.

Source:

Community discussions cited in the Sources section.

Security limitation (configuration-sensitive)

A documented risk related to running SIP without secure transport highlights the need for TLS/SRTP and robust operational controls.

Reference:

https://www.bleepingcomputer.com/news/security/cisco-warns-of-webex-for-broadworks-flaw-exposing-credentials/

- A documented risk related to running SIP without secure transport highlights the need for TLS/SRTP and robust operational controls. Reference: - https://www.bleepingcomputer.com/news/security/cisco-warns-of-webex-for-broadworks-flaw-exposing-credentials/

Roadmap / “What’s New” (feature evolution)

Cisco maintains vendor-managed “What’s New in Webex for BroadWorks” pages describing enhancements. These pages provide a vendor-updated view of feature changes; buyers should treat roadmap items as vendor statements subject to change.

https://help.webex.com/en-us/article/ne4v0oy/What-s-New-in-Webex-for-BroadWorks

02Why they buy

Documented differentiators and structural advantages

Single app integration: A client that presents calling (BroadWorks) together with Webex meetings and messaging.
Service provider distribution model: Enables SPs to include PSTN, local compliance, and support as part of their offering.
Provisioning and automation capabilities: APIs and flow-through provisioning designed for SP operational scale.

Sources:

Cisco product overview and solution guide.

- **Single app integration:** A client that presents calling (BroadWorks) together with Webex meetings and messaging. - **Service provider distribution model:** Enables SPs to include PSTN, local compliance, and support as part of their offering. - **Provisioning and automation capabilities:** APIs and flow-through provisioning designed for SP operational scale. Sources: - Cisco product overview and solution guide.

Where competitors have advantages (balanced)

Microsoft Teams Phone: Strong integration with Microsoft 365 and a Teams-native user experience.
Zoom Phone: Familiar meeting UI and simple entry-level phone plans for SMBs.
RingCentral / other UCaaS vendors: Perceived simplicity for some telephony feature bundles, though cost and feature depth vary.

Public pricing and product references are cited in the Sources section.

03Field reports

Review platform coverage note (scope mismatch)

A limitation when assessing Webex for BroadWorks is that most public reviews address Webex Meetings, Webex Suite, or Webex Calling rather than the SP-delivered Webex for BroadWorks offering. Many observations about the Webex App and calling administration apply across these related offerings, but buyers should distinguish SP-managed configurations and support models from Cisco’s direct cloud service.

Gartner Peer Insights (access note)

Gartner Peer Insights includes entries for Webex Suite and related Cisco collaboration products; full review text may require sign-in or subscription. Cisco cites recognition on Gartner Peer Insights in vendor communications; such vendor-authored summaries should be treated as vendor-published context rather than independent review content.

Gartner Peer Insights product review page for Cisco Webex

G2 (Webex Calling) — positive and negative excerpts (paraphrased)

Positive (G2): Operational efficiency and ecosystem integration

Reviewers report that features in Control Hub can reduce user provisioning time compared with earlier processes.
Users cite benefits from SD-WAN QoS prioritization and system redundancy behaviors.

Negative (G2): Porting delays, analytics limitations, client performance, SKU complexity

Reports of porting delays, including examples of extended delays (multi-week).
Reporting and analytics may not meet all contact center requirements.
Some users report that the Webex App softphone has higher system resource usage than alternative clients.
Licensing SKUs and packaging are frequently cited as complex.

Source:

G2 product review page for Webex Calling

**Positive (G2):** Operational efficiency and ecosystem integration - Reviewers report that features in Control Hub can reduce user provisioning time compared with earlier processes. - Users cite benefits from SD-WAN QoS prioritization and system redundancy behaviors. **Negative (G2):** Porting delays, analytics limitations, client performance, SKU complexity - Reports of porting delays, including examples of extended delays (multi-week). - Reporting and analytics may not meet all contact center requirements. - Some users report that the Webex App softphone has higher system resource usage than alternative clients. - Licensing SKUs and packaging are frequently cited as complex. Source: - G2 product review page for Webex Calling

TrustRadius (access note)

TrustRadius pages reference Webex Calling and include platform-provided metrics (e.g., vendor-provided user counts). These figures are vendor/community-supplied and should be validated in procurement contexts.

TrustRadius product review page for Webex Calling

Community / Social (Reddit) — recurring themes

Client install/update friction and resource use

Community posts express frustration with installer behavior and interactions with endpoint control tools (e.g., AppLocker), indicating administrative friction for locked-down environments.

Calling reliability and network/IP range issues

Discussions describe intermittent ringing or call path issues, with troubleshooting often pointing to port changes or IP range handling.

Confusing multiple calling paths

Users discuss differing audio paths and configuration implications related to SRTP and QoS marking.

Integration usability with competing collaboration platforms

Posts indicate friction when users expect integrated calling inside a different primary collaboration client (e.g., Teams).

Migration process uncertainty

Community threads request guidance on moving from BroadWorks registration in the Webex App to other Webex calling models, indicating some documentation or procedural gaps for certain migration scenarios.

Sources:

Various Reddit and community discussion threads (see Sources section below)

1) Client install/update friction and resource use - Community posts express frustration with installer behavior and interactions with endpoint control tools (e.g., AppLocker), indicating administrative friction for locked-down environments. 2) Calling reliability and network/IP range issues - Discussions describe intermittent ringing or call path issues, with troubleshooting often pointing to port changes or IP range handling. 3) Confusing multiple calling paths - Users discuss differing audio paths and configuration implications related to SRTP and QoS marking. 4) Integration usability with competing collaboration platforms - Posts indicate friction when users expect integrated calling inside a different primary collaboration client (e.g., Teams). 5) Migration process uncertainty - Community threads request guidance on moving from BroadWorks registration in the Webex App to other Webex calling models, indicating some documentation or procedural gaps for certain migration scenarios. Sources: - Various Reddit and community discussion threads (see Sources section below)

Why customers choose Webex/BroadWorks-style solutions (inferred from reviews)

Existing Cisco UC infrastructure and desire for centralized administration via Control Hub.
Preference for provider-delivered PSTN and local compliance handling.
Need for a single client that offers calling, meetings, and persistent chat in a single interface.

Evidence: User reviews and vendor materials referenced in the Sources section.

Why some customers leave / avoid (common churn drivers)

Organizations standardized on Microsoft 365 may default to Teams for daily collaboration, creating resistance to a second client.
Endpoint control policies that interfere with client updates and installer behavior can create operational support overhead.
Perceived complexity in licensing and feature packaging.
Expectations for advanced voice analytics or contact center metrics may not be met by base reporting tools.

Evidence: Community posts and review excerpts cited above.

- Organizations standardized on Microsoft 365 may default to Teams for daily collaboration, creating resistance to a second client. - Endpoint control policies that interfere with client updates and installer behavior can create operational support overhead. - Perceived complexity in licensing and feature packaging. - Expectations for advanced voice analytics or contact center metrics may not be met by base reporting tools. Evidence: Community posts and review excerpts cited above.

Sources

Official vendor documentation and product overview pages
Gartner Peer Insights product reviews
G2 product and review pages
TrustRadius product and review pages
Industry Reddit and community discussion threads

Example: Service provider announcement (CBTS)

CBTS announced integration of Cisco Webex with BroadWorks-hosted UC to provide unified calling and collaboration.

Source: Official vendor press release

Critical evaluation: This is a press release that signals market adoption and positioning but does not provide independent validation or detailed measurable outcomes (ROI, productivity gains).

Example: Cisco partner blog (scale claim)

A Cisco partner blog referenced a large user count in promotional language.

Source: Partner blog post / vendor-authored content

Critical evaluation: The cited user figures appear in vendor-authored content and may aggregate BroadWorks ecosystem users rather than active Webex for BroadWorks seats. Without a stated methodology (time period, definition of “users,” or active versus provisioned accounts), treat such numbers as directional and verify in procurement.

A Cisco partner blog referenced a large user count in promotional language. - Source: Partner blog post / vendor-authored content Critical evaluation: The cited user figures appear in vendor-authored content and may aggregate BroadWorks ecosystem users rather than active Webex for BroadWorks seats. Without a stated methodology (time period, definition of “users,” or active versus provisioned accounts), treat such numbers as directional and verify in procurement.

Example: Third-party ecosystem integration (Rev.io)

Rev.io describes an integration that supports provisioning and package management to reduce manual administration.

Source: Third-party vendor blog post

Critical evaluation: This vendor post indicates that third-party operational tooling exists to support Webex for BroadWorks deployments. It demonstrates ecosystem activity, but it is not an independent case study of business outcomes.

04Best fit

ICP for Service Providers (primary)

Company type: Telecom operators, MSPs, UCaaS providers operating BroadWorks.
Scale: Mid-to-large providers with an established BroadWorks subscriber base.
Primary personas: Product managers, platform engineers, operations, and channel sales teams.
Fit drivers: Need to offer packaged collaboration with PSTN and regulatory support, and desire for provisioning and automation hooks for SP operations.

Evidence:

Cisco SP-focused positioning and vendor provisioning API documentation.

- **Company type:** Telecom operators, MSPs, UCaaS providers operating BroadWorks. - **Scale:** Mid-to-large providers with an established BroadWorks subscriber base. - **Primary personas:** Product managers, platform engineers, operations, and channel sales teams. - **Fit drivers:** Need to offer packaged collaboration with PSTN and regulatory support, and desire for provisioning and automation hooks for SP operations. Evidence: - Cisco SP-focused positioning and vendor provisioning API documentation.

ICP for End Customers (through SPs)

Company sizes (typical): Small to large organizations, from small teams to enterprise scale, depending on the SP’s capabilities and bundled services.
Industries: Professional services, healthcare, education, and public sector organizations where managed PSTN and local compliance are important.
Decision makers: IT/telephony leads, CIO/IT director, procurement via telecom vendor.
End users: Knowledge workers requiring calling, meetings, and persistent chat.

- **Company sizes (typical):** Small to large organizations, from small teams to enterprise scale, depending on the SP’s capabilities and bundled services. - **Industries:** Professional services, healthcare, education, and public sector organizations where managed PSTN and local compliance are important. - **Decision makers:** IT/telephony leads, CIO/IT director, procurement via telecom vendor. - **End users:** Knowledge workers requiring calling, meetings, and persistent chat.

05The pitch

What the product does (objective core value proposition)

Cisco presents this as a way for service providers to package collaboration features with their existing BroadWorks calling services and regulatory/local support footprint. Cisco's public materials describe flexibility, security, and a unified user experience delivered via provider partners.

Key architectural idea: one app, two backends.

Calling (PSTN + enterprise telephony features): BroadWorks (service provider infrastructure)
Messaging, meetings, presence, identity: Webex cloud

Sources: Official vendor product overview and Webex solution guide.

Cisco Webex for Cisco BroadWorks is a service-provider-oriented UCaaS offering that integrates BroadWorks cloud PBX calling (delivered/operated by a telecom/service provider) into the Webex App. End users receive calling, meetings, and messaging in a single client while PSTN connectivity and call control remain on the provider’s BroadWorks infrastructure. The Webex App connects to the Webex cloud for messaging/presence/meetings and registers to BroadWorks for telephony. Cisco presents this as a way for service providers to package collaboration features with their existing BroadWorks calling services and regulatory/local support footprint. Cisco's public materials describe flexibility, security, and a unified user experience delivered via provider partners. **Key architectural idea:** one app, two backends. - **Calling (PSTN + enterprise telephony features):** BroadWorks (service provider infrastructure) - **Messaging, meetings, presence, identity:** Webex cloud Sources: Official vendor product overview and Webex solution guide.

Target market and market positioning

Primary buyers / channel:

Service Providers (SPs) and SP partners who operate BroadWorks and want to offer a Webex-based collaboration bundle.

Secondary “buyers” (through SPs):

SMB to enterprise business customers of those SPs that seek UC features without running on-premises PBX/UC.

Positioning themes:

Service-provider-grade calling provided by the SP combined with Webex collaboration features in a single client.
A migration path from BroadSoft/BroadWorks-era UC-One soft clients to the Webex App (Cisco positions the Webex App as the primary soft client).

Sources: Vendor blog and product help documentation.

**Primary buyers / channel:** - **Service Providers (SPs)** and SP partners who operate BroadWorks and want to offer a Webex-based collaboration bundle. **Secondary “buyers” (through SPs):** - SMB to enterprise business customers of those SPs that seek UC features without running on-premises PBX/UC. Positioning themes: - Service-provider-grade calling provided by the SP combined with Webex collaboration features in a single client. - A migration path from BroadSoft/BroadWorks-era UC-One soft clients to the Webex App (Cisco positions the Webex App as the primary soft client). Sources: Vendor blog and product help documentation.

Get a comprehensive analysis of Cisco Webex for Cisco BroadWorks including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →