We no longer actively support WebRTC as a service. But we are committed to ensuring our services remain platform and application-agnostic. And that they are able to be integrated into any VoIP-enabled application, including proprietary or open-source WebRTC applications. Read more here.
WebRTC has the potential to transform the way enterprises communicate, and we’ve barely begun to scratch the surface of its full capabilities. To start, a ‘click to call’ link or button can initiate a connection via a web browser, with a URL representing the recipient’s end-point of the call. We have already started to experiment with this concept at Voxbone; in fact, most employees currently have a clickable URL in their email signatures!
The potential doesn’t stop there. With the proper configuration, a URL used in place of a phone number can fully prescreen a would-be caller. By requiring the input of personal information before initiating a call, WebRTC can not only prevent unwanted calls, but it allows the call receiver to route the communication to the medium best suited for the conversation (video, voice, text, etc.).
But there are also some limitations to the power of WebRTC used as a replacement for a phone number, at least for the short to medium term. In my recent article for Programmable Web, I detail some scenarios of how WebRTC can be, as well as the challenges that need to be addressed before full-blown adoption.