WebRTC – Voice, Video, Screenshare


Expertflow's WebRTC implementation allows agents and customers to securely share voice, video, and screen content. It doesn't require the customer or your agents to install any software - all that is required is a WebRTC-compatible browser.

Integrated into your website, mobile app, kiosk, or digital signage device, WebRTC allows customers to establish an HD video session with an agent featuring, screen sharing, WWW activities, and chat. A video session can also be initiated as part of a chat session or a voice call. Agents use a Finesse Gadget to initiate a session.

Customers can be identified automatically using a cookie/ token on your website.

Embed any Expertflow widget such as WebRTC, Callback, or Chat with a single line of code, as a WordPress Plugin, or Google Tag.

Standalone / Cisco Unified Contact Center Express (UCCX), Enterprise (UCCE or PCCE), Freeswitch, FusionPBX

WebRTC to SIP Gateway

Customers use the WebRTC capabilities of their web browser and webcam to interact with agents. Metadata (customer name, email,...) is captured from their browser via a tag management solution. On the agent side, voice and video are transcoded to SIP and forwarded to the agent's Voice/ Videophone. The screen sharing element is available as a Finesse Gadget.

The same webphone / WebRTC capability can be enabled for agents as well. This eliminates the need for a hardphone or installable softphone such as IP communicator or Jabber.

Learn more


Available features:

  • Browser or SIP phone-based voice and video
  • Browser-based screen-sharing

Features with additional licenses

  • Hybrid Chat
  • file sharing
  • recording

WebRTC doesn't allow for

  • mouse or keyboard control
  • screen annotation, field masking, pointer

The customer identifies himself to the browser to the client's website. This browser in turn is associated with a customer profile in CIM using a cookie that will be stored in the customer's browser. The customer identity is transmitted through a tag manager data layer on the website.



 Web and Browser events EventsDOM Sharing/ Co-browsingScreen sharingWebRTC
VendorsExpertflowSurfly, Acquire, unbluJabber Guest,Cisco Webex, ZoomExpertflow
Sharing what

pages visited and actions taken by customer on a website.

Company webpages only.

Screenshare-like experience, location of the mouse
Draw something to the customer from the agent.
Company webpages only.

entire screen or browser.

control of mouse and keyboard

content of a browser or an entire screen
Field Maskingn/apossiblenot possiblenot possible
Annotationn/apossiblepossiblenot possible
Agent seestext notifications “Customer clicked on button”, “Customer navigated to www.expertflow.com.”Web events. Selective customer screen replication (masking, mouse, annotation)customer screen pixel-by-pixel, plus overlay (laser pointer, annotation,...)customer screen pixel-by-pixel (plus voice and video)
TechnologyTag Management (page views, clicks, form entries, selected DOM events..)DOM events on a webpageentire screenentire screen (WebRTC)
Required permissionsUsually accept a cookieUsually accept a cookieDownload and install a plugin, allow access to screen and mouse/ keyboard controlsWebRTC-compatible browser, usually allow cookies. Allow access to screen.
Bandwidthvery low - selected events only, from Webserver to agenthigher - all web events, from Webserver to agentHigh - every pixel from customer to agentHigh - every pixel from customer to agent

Transfer of customer data from website to callcenter

This solution includes a ICE (Interactive Connectivity Establishment) server that can be located on the client's premises or using a public server for network address translation (ICE, STUN, TURN).

Agents can use a normal Cisco SIP phone (such as Jabber), or Expertflow's WebRTC client.

With Expertflow CIM, it is possible to capture customer data from a website before a WebRTC call, and transfer the same to a Cisco Callcenter as call attached data alongside the call.
Information is captured on the website using tag management, transferred to the WebRTC switch using RTCDataChannel, transferred to CIM, from where it can be read by CVP or Finesse and written as Call Attached data/ Peripheral Variables/ Expanded Call Context (ECC). Implementing this solution usually requires professional services of Expertflow.

Learn more
Customer data