RingCentral Embeddable 3.0 is now GA — plus 3.1 Beta with RingCX
With thousands of users having tested the beta, we’re happy to announce that RingCentral Embeddable 3.0 is now generally available.
What’s new in 3.0
- Side panel architecture. The biggest change in 3.0. Detail views open in a side panel instead of replacing the list you came from — call recordings, voicemail details, SMS conversations, fax details, contact details, team messaging conversations, and the call and message logging pages.
- Call Widgets. A new extensibility point that lets developers inject dynamic, contextual content directly into the calling experience. Widgets appear automatically during active calls, update in real time based on call context, and are built on JSON Schema so you can render CRM records, support cases, or anything else your integration needs.
- Voicemail Drop. Users can leave a pre-recorded message when an outbound call reaches voicemail, so they can move on to the next call instead of waiting for the recording to finish.
- Heads-Up Display. The HUD from our desktop app, now in Embeddable. Monitor team member presence and pick up calls from park locations, group call pickup, and call queue pickup.
- SMS shared inbox. Users assigned as an SMS recipient on a call queue can view and respond to customer texts from a shared inbox in the widget, so multiple queue members can share the load and keep response times down.
- New multi-tab support. The Web Phone module now uses a Shared Worker, which keeps the phone connection alive across tabs, cuts redundant resource usage, and prevents the conflicts and disconnections that multiple independent connections used to cause.
- 100% backwards compatible with 2.x. No breaking changes — update your URL and redirect URI and you’re done.
The latest branch moves on November 16
To give everyone time to test 3.0 against their own integration, we’re waiting approximately 30 days before repointing latest from 2.x to 3.0. That switch happens on November 16.
If you pin to latest, you’ll be upgraded automatically on that date. We’d encourage you to test against 3.0.0 explicitly before then so there are no surprises.
Also launching: Embeddable 3.1 Beta, with RingCX
We’re also excited to officially launch the Embeddable 3.1 beta. This release is the culmination of almost a year of planning, in which we worked to merge our RingCX Embeddable product with this one to create a single unified Embeddable phone.
3.1 brings RingCX contact center calling into Embeddable alongside RingEX. Agents get a new Agent tab to start a session, pick queues and dial groups, set their working state, handle RingCX calls, transfer and requeue, submit dispositions, work preview leads, and follow agent scripts. For developers, RingCX calls use the same events, commands, and third-party service APIs as RingEX calls — a new call.source field tells you which product a call belongs to, and your existing callLoggerPath, contactMatchPath, and callLogEntityMatcherPath registrations work without changes.
3.1 also ships a new UI built on Spring, RingCentral’s design system, and adds fax sending.
Add enableRingCX=1 to your widget URL to turn it on. Full details and setup instructions are in the Embeddable 3.1 Beta docs.
As always, we’d love your feedback.