I spent some time this week with the Voice4Net team and had an opportunity to see how they are using WebRTC. Rich McFarlane, Vocie4Net CEO talked to where the company is coming from and where they are going with WebRTC and Web-based technologies. Voice4Net has been building a set of custom interaction components for a number of years. They specialize in more component and custom developments, for certain verticals and through channels for vendors like Mitel.
It is generally agreed that there are two major applications of WebRTC in the contact center, first as a customer’s client enabling clientless interactions form the customer, and second as a an agent enablement tool to allow agents to operate without a download or client app. Vocie4Net has stepped even farther back, focusing on using Web technologies and mash-ups to create a potentially transformational agent and supervisor experience first, and worrying about WebRTC voice and video second.
The first key use of WebRTC is that all of these desktop widgets use a common WebRTC data channel to send and receive data back to the RTC Gateway Server. One of the widgets is the ability to see all of the other agents and their presence. After this widget is dragged and dropped onto the template in the designer, an agent or supervisor receives that browser page image, each agent is shown including presence information. Presence status information is sent form the server to the client though the WebRTC data channel. Similarly, when a screen pop with Salesforce data is dropped into the screen, the data to populate that widget on an agent desktop is sent through the data channel. While WebRTC is not used for actual media traffic from customers in this early implementation, it can be used between agents.
Today, Voice4Net is focused on delivering this capability to enable contact centers to rapidly integrate the functions of the widgets, with the primary interface from the RTC gateway to a PBX for CTI. In this case, the PBX is providing ACD functions and real time voice is still realized through the PBX connected phones. The next step is the enable the RTC Gateway to run the Voice4Net ACD software. The client will then get WebRTC real-time audio and video. At this point, the actual media can run from the PBX to the RTC Gateway, be serviced by the Voice4Net ACD and distributed to the agent over WebRTC. Now the entire contact Center functions has been moved out from the PBX (or key system) to the Voice4Net solution. Additional modules can be added for other functions as well.
The key advantage of running traffic through the PBX is that a single trunk can be used for both DID traffic and contact center traffic. For environments where DID traffic is not important or even required, SIP trunks can be routed directly to the RTC Gateway. This solution can be used for new verticals applications, such as healthcare.
It is of note that while all of the focus of Voice4Net at this point is on using the Web and WebRTC to reduce the complexity of providing advanced tools, it also is the foundation for the integration of WebRTC into the client experience. Using tools already in the portfolio, the integration of the solution to a click from a Web page is anticipated as relatively easy.
Voice4Net is also focused on the tools necessary for Work Force Optimization in the new environment where customers are coming into the contact center from the Web site with rich contextual information. IN fact, one of the widgets that the team showed was a tracking of interactions causes, a greater intimal tool for tracking why users are leaving the web site and going to the contact center.
Edited by Maurice Nagle