How to Implement Co-browsing in Customer Support
A practical guide to co-browsing in customer support: how it differs from screen sharing, how to roll it out, how masking works, and how it runs in native apps and contact centre platforms.

Co-browsing lets a support agent see the web page a customer is on, point at it and, with permission, help fill it in. It solves the problems that are hard to talk through: a form that will not submit, a checkout step that is confusing, a setting buried three menus deep. This guide explains what co-browsing is, how it differs from screen sharing, and how to roll it out in a contact centre, step by step.
What is co-browsing?
Co-browsing (collaborative browsing) is a shared view of a web page. The customer stays in control of their own browser, and the agent sees a live copy of the same page in theirs. Both can see each other’s pointer, and the agent can highlight parts of the page to guide the customer.
The important word is page. Co-browsing shares what is happening inside your website or app, not the customer’s whole computer. That keeps the session focused on the task, and it means you decide which parts of the page an agent may never see.
In Auvious, web co-browse works by sending a live copy of the page’s HTML to the agent, rather than a video of the screen. Because the agent is looking at the real page structure, sensitive fields can be filtered out before anything leaves the customer’s browser. You can read the technical detail in the Auvious co-browse guide.
Co-browsing vs screen sharing
They are often confused, but they solve different problems.
Screen sharing sends a video feed of the customer’s screen, window or tab. The agent can look but not touch. It works for anything on the desktop, including other applications, but it cannot hide sensitive information, and mobile browsers generally cannot share their screen at all.
Co-browsing shares a live copy of a specific web page. The agent can point, draw and, once the customer agrees, click and type on the customer’s behalf. Sensitive fields can be masked, and it works in desktop and mobile browsers.
A simple rule: if the problem lives on your website, co-browse. If it lives somewhere else on the customer’s computer, ask them to share their screen. In Auvious the agent can request a screen share from inside a co-browse session when a problem turns out to sit outside the page. The screen sharing vs co-browse comparison in our docs lists the differences in full, and we cover the trade-offs in more depth in screen sharing for customer support: limits and alternatives.
Where co-browsing helps most
Co-browsing earns its place wherever a customer is stuck on a page you own:
Applications and onboarding: walking a customer through a long form, an account opening or an insurance quote.
Checkout and payments: finding why an order will not go through, while payment details stay hidden from the agent.
Self-service portals: showing where a setting, an invoice or a document lives.
Technical support: following the exact steps a customer takes to reproduce an error.
For real examples of visual support in practice, see our case studies, including how IONOS moved to remote technical support after Genesys screen share was retired.
How to implement co-browsing: step by step
Pick the journeys first. List the three or four pages where customers most often get stuck or call in. Start there.
Add the widget where every page can reach it. Co-browse lives wherever the widget lives. In Auvious you add a script to the page head and the widget tag before the closing body tag. On a single-page application, wrap the widget in a component that every route shares, such as the header or footer. On a server-rendered site, put it in the master page or outermost layout. The co-browse installation guide covers each case.
Decide what agents must never see. Mark sensitive fields for masking before you go live (more on this below).
Choose how sessions start. Agents need a quick way to start a session from the channel the customer is already using, whether that is a phone call, a web chat or a video call.
Check embedded content. Frames from the same origin are included automatically. Frames from another origin need a small extra script before they can be shared.
Write a short agent playbook. Cover when to offer co-browse, how to ask for consent in plain words, and when to ask for control.
Pilot, then widen. Run it with one team, review agent and customer feedback, then extend it to more journeys and more agents.
Starting a session: PIN, chat or video
Auvious offers three ways to start a co-browse session, so it fits the conversation you are already having:
With a PIN, no call needed. The agent generates a 7-digit PIN and reads it out or sends it. The customer types it into the widget and the session starts. This works alongside an ordinary phone call or any other channel.
From a web chat. In Genesys Cloud and Talkdesk, the agent can send an invitation straight into the chat conversation, and the customer accepts it.
From an Auvious video call. The agent requests co-browse during the call and the customer accepts the request.
In every case the customer has a clear moment of consent, and either party can see when the page is being shared.
The agent’s toolkit during a session
Once a session is running, Auvious gives the agent a small, practical set of tools:
Two visible pointers, so customer and agent can always see where the other is looking.
Marker, arrow and eraser for drawing on the page. While annotating, the page turns greyscale so the drawing stands out and nothing is clicked by accident.
Actual size and zoom, so a customer’s larger screen still fits the agent’s window.
Control page. The agent can ask to click and type for the customer, for example to complete a tricky form. The customer has to grant this explicitly.
Security and data masking
Customers will only accept co-browsing if they trust it, and your security team will only approve it if they can control it. Look for three things in any tool.
Masking you configure. In Auvious you list CSS selectors for the elements agents must not see, such as card numbers or identity details. Those elements appear to the agent as a dark box, or as a blurred field with the text replaced. Password and file inputs are never sent at all. The widget co-browse settings show how to set the filters.
Scope limited to your site. The agent sees only pages where your widget is installed. If the customer opens another site, co-browse stops.
Consent and control. Sessions start only when the customer enters a PIN or accepts an invitation, and control of the page is never taken without the customer’s permission. The security FAQ covers data handling and widget integrity.
Co-browsing in native mobile apps
Many customers now reach you through your app, not your website. Web co-browse works in mobile browsers and in web-view apps built with frameworks such as Cordova or Ionic. For fully native apps, Auvious offers mobile SDKs for iOS (15 and later) and Android (6.0 and later).
Native co-browse works a little differently from the web version:
A masked screen share of your app. The agent sees a live video of your app’s screens, with sensitive views blacked out using the SDK’s masking rules. Only your app is shared.
Annotation in both directions. The agent can draw on the customer’s screen, and the customer can draw back.
Standalone or in-call. The customer can start co-browse with an agent’s PIN without a call, or the agent can request it during an Auvious video call from the app.
Clear consent. The customer sees a short explanation, then the standard iOS or Android screen-recording prompt.
One difference to plan for: on mobile, the agent guides but does not take control of the app. The mobile SDK feature list sets out exactly what each platform supports.
Co-browsing inside Genesys Cloud, Talkdesk and NICE CXone
Agents should not have to open another tool to co-browse. Auvious runs inside the contact centre platforms teams already use:
Genesys Cloud. Auvious is available as a Genesys Cloud premium application, and works with the default Genesys web chat widget as well as the Auvious widget. Agents can send a co-browse invitation from a chat. See co-browse for Genesys Cloud and the wider Genesys Cloud integration.
Talkdesk. The agent shares a PIN by chat or over the phone, and the customer enters it in the Auvious widget. See the Talkdesk integration.
NICE CXone. The Auvious widget connects to CXone through a digital point of contact. Our guide to enabling video in NICE CXone covers the wider set-up.
Teams with their own platforms can also use Auvious standalone or through its API. The product overview shows how co-browse fits alongside video, voice and AR guidance.
Choosing a co-browse tool
When you compare options, ask each vendor the same questions:
Does it share a live copy of the page, or only a video of the screen?
How do you mask fields, and is anything sensitive never sent?
Does it work in native iOS and Android apps, and how does masking work there?
Does it run inside our contact centre platform, or as a separate window?
How do sessions start from a phone call, a chat and a video call?
We have written side-by-side comparisons to help, including Auvious vs Cobrowse.io, Auvious vs Glia and Auvious vs Unblu. For budgeting, see what co-browsing plans cost.
Frequently asked questions
Does the customer need to install anything?
No. On your website, co-browse runs in the customer’s browser through the widget you have installed. In a native app, it runs through the Auvious SDK inside your app.
Can the agent see other tabs or applications?
No. Co-browse shares only pages that carry your widget. If the customer needs to show something outside the page, the agent can ask them to share their screen, which the customer chooses and can stop at any time.
Can an agent fill in a form for the customer?
On the web, yes, but only after the customer grants control. In native mobile apps, the agent can see and draw on the screen but cannot control it.
What happens when the customer moves to another page?
On single-page applications, the session carries on as the customer navigates. On traditional multi-page sites, the widget reconnects once the new page loads, so long as that page also has the widget.
See co-browse working in your own contact centre
The fastest way to judge co-browsing is to try it on one of your own journeys. Book a demo and we will show you Auvious co-browse inside the platform your agents already use.
See auvious inside your own contact centre.
Book a 30-minute demo and we will show you browser-based video and cobrowse working inside the platform you already use. On Genesys Cloud? See Genesys video calls and Genesys co-browse.