You’re on Cisco BroadWorks. It’s not broken — it’s battle-tested, carrier-grade. What’s changed isn’t BroadWorks. What’s changed is the category of UCaaS platform around it. We took a look at the concrete things service providers gain when they move from legacy BroadWorks to a next-gen innovation-led UCaaS platform — across capability, commercial model, brand control, and strategic positioning.
With Cisco’s strategic investment moved to Webex Calling,2 and UC-One is being phased out in favor of the unified Webex App per Cisco’s own solution guide.3 The strategic question for BroadWorks service providers in 2026 isn’t whether the platform works (it does) — it’s whether the next decade of UCaaS innovation is happening on legacy carrier platforms or on next-gen ones. Moving to a next-gen innovation-led UCaaS platform like NetSapiens delivers concrete gains across capability (REST APIs, webhooks, AI surfaces, mobile SDK), commercial model (session-based licensing, ~40 seats per session), brand control (100% white-label across every touchpoint), and strategic positioning (platform ownership rather than reseller status under Cisco’s recommended Webex Calling Wholesale path).
Four numbers that define what next-gen UCaaS platforms deliver — and why service providers are moving.
API categories on next-gen platforms — REST-native, OpenAPI schema, no certification gate, same-day developer prototyping
Seats per concurrent session on next-gen session-based licensing — platform cost grows much slower than revenue
Oversubscription growth on next-gen session-based licensing — margins that expand automatically as your customer base grows
Fastest-growing UCaaS platform vendor in North America — service providers are voting with their deployments
Not abstract benefits — specific capabilities, commercial mechanics, and strategic positions that show up on day one of running a next-gen UCaaS platform
What changes: OCI-P SOAP/XML provisioning gives way to REST interfaces with downloadable JSON schemas. Modern tooling compatibility, faster developer onboarding.
What changes: Xsi long-polling event subscriptions give way to push-based webhooks. Event-driven architectures become practical.
What changes: programmatic intercept, redirect, transfer, hold — the foundation for AI voice agents, call coaching, intelligent routing.
What changes: AI-relevant surfaces become part of the platform, not features you wait for Cisco to ship through Webex.
What changes: SNAPmobile SDK for branded mobile apps and SNAPbuilder for branded portals — building your own customer-facing software becomes practical, not a Cisco services engagement.
What changes: pay for ~40 seats sharing one concurrent call session instead of paying per individual seat. Platform cost grows much slower than revenue. Margins expand with scale rather than flatlining.
Service providers gain up to 20% year-over-year oversubscription improvement on next-gen session-based licensing, meaning the platform gets more profitable per customer the longer they’re on it.
What changes: Cisco’s recommended migration path is Webex Calling Wholesale2 — which converts service providers from platform owners into resellers of Cisco’s hosted UCaaS. Moving to a next-gen platform preserves ownership.
What changes: innovation pace is set by what you choose to build, not by what Cisco decides to ship in Webex this quarter. The features you need for your customers exist when you build them, not when the vendor prioritizes them.
Twelve dimensions, organized into capability, commercial, brand, and strategic categories.
| Dimension | ✘ What You're On (BroadWorks) | ✓ What You Gain (Next-Gen) |
|---|---|---|
| API architecture Developer interface generation | ✘ OCI-P SOAP/XML provisioning; Xsi HTTP for actions/events/media; integration requires Network Access List configuration per source. | ✓ REST-native APIs with full OpenAPI schema, searchable interactive reference, downloadable JSON schemas, no per-source configuration overhead. |
| Event delivery How your applications hear from the platform | ✘ Xsi event subscriptions over HTTP long-polling. Functional but pre-dates modern push patterns. | ✓ Real-time webhook delivery to your application endpoints. Modern event-driven architecture support. |
| Live call control Programmatic call manipulation | ✘ Xsi provides call-event notifications and some action capability. AI-orchestrated call control patterns are constrained. | ✓ First-class live call control API category: intercept, redirect, transfer, hold programmatically. Foundation for AI voice agents.Row 3, Content 2 |
| AI capability surfaces Transcription, sentiment, media manipulation | ✘ Not publicly documented as developer surfaces. AI features arrive through Webex App integration, not the platform itself. | ✓ Native API categories for transcription, sentiment, and programmable media. AI products built on the platform, not waiting for vendor delivery. |
| Mobile SDK Foundation for branded mobile apps | ✘ UC-One client (being phased out per Cisco's solution guide3) or Cisco-branded Webex App. No SDK for building a different branded mobile app. | ✓ SNAPmobile mobile SDK for full white-label mobile apps under your brand. |
| Low-code UI Service-provider portal customization | ✘ CommPilot is a fixed Cisco-branded administrative interface. No developer-extensible UI platform. | ✓ SNAPbuilder low-code UI for branded portals and self-service customer apps. |
| Developer portal How developers explore and prototype | ✘ Cisco DevNet with documentation and sandbox. Production integration typically requires Cisco Solution Partner Program certification. | ✓ Interactive ReadMe-style portal with try-it-now functionality. No certification gate. Same-day prototyping. |
| CDR delivery Call detail records for billing and analytics | ✘ FTP batch file transfer or per-call RADIUS messages. Functional but pre-dates streaming data architectures. | ✓ Real-time event-driven CDR delivery, programmable Cradle-to-Grave APIs for modern data pipelines. |
| Commercial model How licensing scales with your business | ✘ Per-seat licensing — platform cost scales lockstep with revenue. Lifetime legacy licenses exist; new agreements renew 3-5 years. | ✓ Session-based licensing — ~40 seats share one concurrent session. Platform cost grows much slower than revenue. Margins expand with scale. |
| Deployment flexibility Where the platform runs | ✘ Service-provider-operated BroadWorks deployment; Cisco's recommended migration target is Cisco-hosted Webex Calling Wholesale. | ✓ Choice of self-host, vendor-cloud, public cloud, private cloud, or hybrid. Service provider controls the deployment topology. |
| Brand control Whose name the end customer sees | ✘ Service-provider branding at the client level. Cisco branding visible across CommPilot, Webex App (for Webex for BroadWorks integration), Control Hub. | ✓ 100% white-label across every customer touchpoint. No vendor branding visible to end users anywhere in the experience. |
| Strategic positioning What kind of business you're running | ✘ Cisco's recommended path is migration to Webex Calling Wholesale — converting service providers into resellers of a Cisco-hosted UCaaS product. Innovation pace set by Cisco. | ✓ Platform ownership. Your roadmap, your differentiation, your customer relationship. Innovation pace set by what you choose to build. |
Next-gen platforms run at hundreds of service providers globally with millions of end users, with the SIP interop depth, codec support, and voice-quality engineering that carrier operations require.
e911 capability, lawful intercept support, CALEA compliance, emergency services integration — table stakes for any service-provider-grade platform, including next-gen ones.
Existing PSTN routing arrangements can be preserved through BYOC (Bring Your Own Carrier) support. Phone-number inventory transfers through standard porting.
Your customers are your customers. The platform underneath changes; the commercial relationship and brand promise don't.
Mainstream SIP phones, ATAs, gateways, and endpoints work with next-gen platforms through standard certification programs. No forklift hardware replacement required.
Service providers moving from BroadWorks to a next-gen innovation-led UCaaS platform gain: REST-native APIs with full OpenAPI schema versus SOAP/XML OCI-P interfaces; real-time webhooks versus HTTP long-polling Xsi events; live call control APIs for AI voice agents; transcription and sentiment APIs for conversation intelligence; mobile SDK and low-code UI builder for branded customer experiences; session-based licensing where ~40 seats share one session, versus per-seat licensing where margins scale lockstep with revenue; 100% white-label brand control versus Cisco-branded administrative surfaces; and platform ownership versus the Cisco Webex Calling Wholesale alternative which converts service providers into resellers of Cisco’s hosted UCaaS.
A next-gen innovation-led UCaaS platform is a service-provider UCaaS platform built on modern architectural posture: REST-native APIs with published OpenAPI schemas, real-time webhook event delivery, public developer portals without certification gates, native AI integration surfaces (transcription, sentiment, live call control), mobile SDKs and low-code UI builders for service-provider product development, session-based or flexible commercial licensing, and full white-label brand control. The category contrasts with legacy carrier-grade UCaaS platforms — Cisco BroadWorks being the canonical example — which were designed before the modern programmable cloud era and rely on SOAP/XML provisioning interfaces, license-gated APIs, and per-seat commercial models. NetSapiens is one of the leading next-gen platforms in this category, publishing 80+ API categories at docs.ns-api.com.
It depends on what you’re optimizing for. Service providers whose competitive strategy depends on shipping AI voice agents, conversation intelligence overlays, vertical industry bundles, custom mobile experiences, or embedded calling for SaaS products will find the migration cost recoverable within the first deal cycle — because next-gen platforms enable revenue streams BroadWorks cannot. The harder question is the strategic-positioning one: as Cisco invests in Webex Calling rather than BroadWorks, the cost of waiting compounds, and the alternative Cisco migration path (Webex Calling Wholesale) trades platform ownership for reseller status.
Service providers keep the voice-quality and carrier-scale fundamentals they currently have on BroadWorks. Next-gen UCaaS platforms run at hundreds of service providers globally, with millions of end users, and have the SIP interop, regulatory compliance posture, e911 capability, and PSTN integration depth that carrier-grade voice operations require. Service providers also keep their existing PSTN routing relationships through BYOC (Bring Your Own Carrier) support, retain their phone-number inventory through standard porting, and retain their customer relationships and contracts. What changes is the platform underneath — not the customer-facing voice service quality.
Cisco BroadWorks pricing is per-seat — platform cost scales lockstep with revenue, so service-provider margins flatline as the business grows. BroadWorks also carries an unusual legacy of perpetual (‘lifetime’) licenses Cisco inherited from the BroadSoft acquisition, but Cisco has publicly stated software agreements typically renew at 3-5 year intervals. Next-gen UCaaS platforms like NetSapiens offer session-based licensing — service providers pay for concurrent call sessions, with approximately 40 seats sharing one session on average, meaning platform cost grows much more slowly than revenue. Next-gen platforms also typically offer commercial flexibility (subscription/OpEx or perpetual/CapEx) and deployment flexibility (self-host or vendor-cloud) that BroadWorks does not match in its current commercial structure.
Cisco’s recommended path for BroadWorks customers is migration to Cisco Webex Calling Wholesale, supported by mature tooling (Transform Tool, Provisioning Tool, Device Move Tool). Webex Calling is a real, well-engineered cloud UCaaS product — and Cisco IT itself has migrated 84,000 internal users from Cisco UCM to Webex Calling, with plans to reduce UCM servers in the U.S. by up to 80% by fiscal year 2026.5 When the vendor migrates its own employees off the legacy platform, the strategic direction is unmistakable. For BroadWorks service providers — running on a platform deployed at 600+ service providers globally and 25 of the top 30 carriers by revenue1 — the strategic trade-off in the Cisco Wholesale path is real: service providers stop owning a platform and start reselling one. End-customer experience becomes increasingly Cisco-branded through the Webex App. Innovation pace is set by Cisco’s Webex roadmap, not the service provider’s. Margin structure becomes dependent on Cisco’s wholesale pricing. And competitive differentiation becomes difficult — every Cisco-Webex-Wholesale partner has access to the same product. Moving to a next-gen UCaaS platform like NetSapiens preserves platform ownership and the ability to ship differentiated software, at the cost of running the migration to a non-Cisco destination.
Cisco BroadWorks does not document public APIs for live call control, real-time transcription, sentiment analysis, or media manipulation as developer-accessible surfaces. The Xsi interface provides event notifications for call activity, but the AI-relevant surfaces (transcription, sentiment, programmable media) are not exposed publicly — AI features arrive through Webex App integration rather than the BroadWorks platform itself. Next-gen UCaaS platforms document all of these as first-class API categories: live call control for AI agent orchestration, webhooks for real-time event streaming, transcription and sentiment APIs for conversation intelligence, and media APIs for programmable voice experiences. For service providers planning to ship AI voice agents or conversation intelligence overlays in 2026 and beyond, this is a category difference.
Cisco publishes BroadWorks developer documentation at developer.cisco.com/docs/broadworks, with sandbox access for OCI-P, Xsi, and SIP Access. The interfaces are real and well-documented, but the protocol generation shows: OCI-P is SOAP/XML, command-driven, requiring Network Access List configuration per integration. Application certification is part of the Cisco Solution Partner Program. Next-gen UCaaS platforms like NetSapiens publish interactive ReadMe-style developer portals with full OpenAPI schemas, searchable references, try-it-now functionality, and downloadable JSON schemas — no certification required to start building. A developer can land on the site, explore the API surface, and prototype against it the same day.
Faster than most BroadWorks operators expect. Initial pilot rollouts — provisioning a first customer segment with subscriber data, number porting, and device cutover — typically happen in weeks, not quarters. Next-gen UCaaS platforms with established Metaswitch and BroadWorks migration experience treat the move as a well-defined operational project with phased milestones, parallel operations during cutover, and standard tooling for subscriber data transfer, device provisioning, number porting, and feature mapping. Service providers see working pilot customers in weeks, expand by customer segment, and run BroadWorks and the next-gen platform in parallel during the broader rollout. The timeline is closer to a series of weeks-long deployment waves than a multi-quarter forklift cutover.
You’re not alone. Service providers are evaluating BroadWorks alternatives every quarter. NetSapiens is one of the most active destinations — 80+ API categories, full OpenAPI schema, interactive reference, no certification gate. Build a webhook-driven prototype this weekend.
HS Form: Netsapiens | Contact Us
