← Back to home
Comparison · Meetings

Webex vs Element Call

Side-by-side trajectory, velocity, and editorial themes.

W
Webex
MEETINGS
6.3

Webex moves its agentic-workplace features from announcement toward general availability

◆ Current state

Webex's feed is the Cisco Collaboration marketing blog, so it mixes genuine product news with event promos, awards, and customer stories. The real product signal recently: Cisco AI PODs for Collaboration reached GA (on-premises AI for secure deployments), AI Receptionist for Webex Calling went GA, and Cisco Live and InfoComm framed an agentic workplace that spans meeting platforms.

◆ Where it's heading

The through-line is agentic AI woven across Cisco's collaboration stack, calling, contact center, and management via Cisco Cloud Control/AgenticOps, with emphasis on on-prem and platform-agnostic deployment for regulated buyers. The cadence of GA milestones suggests Cisco is moving these AI features from announcement to availability.

◆ Prediction

Expect WebexOne in October to consolidate these agentic-workplace pieces into a headline platform story, with more Webex Calling and Contact Center AI features reaching GA before then.

E
Element Call
MEETINGS
6.3

Element Call moves to a multi-SFU architecture, ending per-call media-server negotiation

◆ Current state

Element Call, the Matrix-native video calling app, is iterating quickly on RC builds and just made a structural change to how calls route media. The latest RC adopts a multi-SFU approach where each participant connects to the SFU tied to their own homeserver, while recent releases also steadily improve mobile layout, error reporting, and call reliability.

◆ Where it's heading

The direction is federation-correct real-time media: rather than negotiating a single shared SFU per call, Element Call leans into Matrix's decentralized model by letting each homeserver own its participants' media and subscribing cross-server as needed. Around that, the team keeps polishing the mobile experience (edge-to-edge, portrait one-on-one layouts, PiP) and hardening LiveKit error handling.

◆ Prediction

Expect multi-SFU to graduate from RC to default with legacy single-SFU mode kept as a fallback, followed by continued work on cross-homeserver subscription reliability and mobile polish.

See more alternatives to Webex
See more alternatives to Element Call