Blog

How is Co-Browsing Different From Screen Sharing?

Author:
Ben Lilienthal

With more and more employees working from home (and an increasing number of consumers staying at home), remote customer support tools have become even more critical to an organization's sustainability. From IT professionals troubleshooting technical issues to sales representatives demonstrating the features of a software program, remote support platforms are no longer optional — they are essential.

Two common methods for providing remote customer support are co-browsing and screen sharing. While these are similar technologies, each option has its own unique advantages and drawbacks when it comes to providing exceptional customer service. This article will answer the following questions related to these two tools:

  • What is co-browsing?
  • What is screen sharing?
  • How are they different from each other?
  • What are the pros and cons of each approach?
  • Which option is generally better for customer support?

Let's begin with a definition of co-browsing.

What is Co-Browsing?

Co-browsing, also known as collaborative browsing, is a method of synchronizing browser access across two or more devices to the same site or sites. In co-browsing, one user is in control of browsing, and the other user's interface automatically follows the lead of the administrator. For example, if the controlling user brings his mouse cursor over to click a link on the web page, the collaborative user's mouse cursor will also move over to that link.

Put simply, co-browsing lets a support agent and a user view and interact with the same web page in real time. The agent sees the page open in the user's browser window and guides the user through it in place. Some co-browsing tools run as JavaScript on the website itself, so neither the user nor the agent has to download software.

How Co-Browsing Works, Step by Step

Co-browsing relies on setup work done before any user asks for help. The organization first prepares its website for co-browsing, for example by adding a JavaScript-based co-browsing script, and that preparation lets an agent join a page later.

From there, a typical co-browsing session moves through five distinct stages:

  1. Start inside a conversation: An agent already on a call, chat or messaging thread offers co-browsing, and the user joins by entering a PIN or accepting an invitation.
  2. Share the page view: The agent's workspace then displays a live view of the web page open in the user's browser window.
  3. Guide before taking control: Some platforms start every agent in read-only mode, where the agent can point, highlight and annotate but cannot type, click or navigate.
  4. Request control with permission: The agent sends a request to navigate or fill in fields, and the user can revoke that control at any time.
  5. End without ending the conversation: Either party can close the co-browsing session, while the call or chat that started it carries on.

Co-Browsing Security: Masking, Consent and Session Controls

A shared web page can still display sensitive personal data that an agent has no reason to see. Three controls decide how much of that data an agent sees or touches.

Data Masking Hides Sensitive Fields From the Agent

Administrators tag sensitive fields and page elements, for example through CSS selectors added to the co-browsing configuration. Masked text appears to the agent as asterisks, and masked images appear grayed out.

User Consent Gates Every Co-Browsing Session

A session normally begins only after the user accepts an invitation or enters a session code. The same rule covers control, because the user approves each navigation request and can withdraw that approval mid-session.

Session Controls Restrict Agent Actions on the Page

Administrators can mark specific elements as non-interactive, which stops an agent from editing a field or clicking a Submit button. Either side can end the session at any point, and some platforms disconnect idle sessions automatically.

Consent and record-keeping matter just as much in screen sharing, which ScreenMeet Live launches from inside the Salesforce Service Console. The product embeds full consent tracking and audit trails in every session, and users join without downloading an application.

Co-Browsing Use Cases for Web-Based Support

Co-browsing fits support requests where the problem lives on a web page rather than on the device. These are the scenarios where a shared page view does the most work:

  • Multi-step forms: With the user's permission, the agent can navigate, fill in fields and follow links to help the user complete a form.
  • Portal and site navigation: The agent points to the right menu or link with a laser pointer or highlight instead of describing it aloud.
  • Online purchases and checkout: Agents can stay with a user through a transaction, a use case vendors tie to lower cart abandonment.
  • Diagnosing web errors: Seeing the actual page lets the agent diagnose the issue accurately instead of relying on screenshots or verbal descriptions.
  • Requests that would otherwise be transferred: Direct visibility into the page helps the first agent resolve the request without handing it to a colleague or supervisor.

What is Screen Sharing?

Screen sharing, as the name implies, involves one party allowing another party to access and control the screen of a particular device. Screen sharing is often referred to as "desktop sharing." This method of remote support is not limited to web browsing, but can also include assistance with regards to downloaded files, desktop applications, and other offline programs.

How are Co-Browsing and Screen Sharing Different from Each Other?

Co-browsing and screen sharing are very similar in design and functionality. However, they do differ from each other in a few significant points. For instance:

  • Co-browsing is primarily designed to allow a group of users to engage in synchronized activities, with one user at a time taking the lead. Screen sharing enables multiple users to simultaneously work on different tasks within the same page or application.
  • Co-browsing typically requires the addition of a browser plug-in. Screen sharing generally requires the installation of a 3rd party application across all associated devices.
  • Co-browsing activities are usually limited to specific web pages, or at least to the Internet. Screen sharing support allows for IT professionals or other agents to fully access the other party's desktop, including offline programs and files.

With these differences in mind, let's briefly discuss the pros and cons of each method.

The Pros & Cons of Co-Browsing

Pros:

  • Co-browsing is often highly suitable for remote demonstrations, since one user is in control of the browsing experience, and all other users are able to follow along without disrupting the process.
  • Co-browsing offers enhanced privacy and security compared to some screen sharing tools, since the remote support agent can only see the browser page in question.
  • Participants in co-browsing sessions don't have to download and install a 3rd party application that could potentially involve a security risk.
  • Control between participants can be passed back and forth depending on the nature of the session.

Cons:

  • Many co-browsing tools depend on streaming, which means a strong Internet connection on both ends is vital.
  • Co-browsing sessions are limited to online activities.
  • Communication between users may be clunky, since control has to be passed back and forth for multiple participants to show unresolved issues, or visually demonstrate the meaning of a question.

The Pros & Cons of Screen Sharing

Pros:

  • Screen sharing allows remote support specialists to solve a variety of issues on the spot, whether they involve online or offline applications.
  • Screen sharing is very effective for collaborations that require real-time interaction and feedback, since users can easily toggle between "view" and "show" modes in an instant.
  • Screen sharing sessions are often more time-effective than their co-browsing counterparts, since participants can easily switch screen control back and forth.
  • Screen sharing facilitates communication and learning by allowing participants to visually demonstrate issues they are having, or try out a program feature for themselves after the host's explanation and walk-through.

Cons:

  • Some 3rd party screen sharing applications come with the risk of spamming, or the introduction of malware into a computer system.
  • Cross-browser access to such 3rd party applications can also lead to session lag and other performance issues.

Why is Screen Sharing the Better Option for Customer Support?

While co-browsing offers several advantages, in most situations screen sharing is a more suitable technology in the realm of customer support. This is the case for several reasons. For example:

  • In order to resolve tickets, IT professionals and help desk agents must often access not just a customer's web browser, but also the customer's computer hard drive and offline files. Screen sharing allows for this capability.
  • Screen sharing is highly interactive — more so than co-browsing. While the host of a co-browsing session can easily demonstrate a program feature, or the flow of a certain process, the host of a screen sharing session has the additional option of letting the other user try to follow the steps just demonstrated for himself. This "hands on" approach will lead to a deeper comprehension of program/software features on the part of the customer, and higher satisfaction.
  • Many screen sharing tools allow the host user to record the entire session for future reference. This means that the remote support agent can later study his or her performance, and identify areas of opportunity for similar customer support activities.

Remote customer support is a growing sector, and will continue to trend upwards as technology advances, and the nature of the global workforce changes. Both co-browsing and screen sharing tools will become more popular over the next several years. Both of these methods have their unique benefits and disadvantages.

Nevertheless, in most customer support applications screen sharing is the preferred option. If you implement state of the art screen sharing solutions within your customer support processes, your agents are sure to be more productive — and your customers are sure to be happier.

Watch a ScreenMeet Demo and see for yourself! 

Ready to Replace Your Legacy Solutions?
Start Your Journey Here

Try The Guided Tour

See It In Action: Experience our comprehensive in-browser demo showcasing all core remote support capabilities and platform integrations.

Product Overview

Watch A 4-Minute Product Overview: Quick overview covering key benefits, security features, and integration capabilities for busy IT leaders. 

Talk To A Specialist

Ready To Get Started? Speak with our platform experts about your specific ServiceNow, Salesforce, or Tanium integration requirements.

Book A Demo