Co-browse in depth, in 32 chapters: radar, identified visitors, consent, remote control, masking, marks, voice call, page changes and how a session ends, all real.
Co-browse is bought separately on any plan: Standard 50 USD/mo (3 concurrent sessions), Pro 90 (6), Business 150 (10) and custom Enterprise.
Co-browse lets you see the customer's screen in real time to guide them better. Learn how to enable it.
Step by step to invite the customer to share their screen and guide them in real time.
Before you start your first Co-browse session, check the add-on, your permissions and the Webchat channel conditions.
What the customer sees when you start Co-browse: the screen-sharing request, what happens if they accept or decline, and the active-session bar.
The RADAR is a live list of the people browsing your webchat right now and whom you can start co-browsing in one click.
From the Radar you can jump into a visitor's conversation and start co-browsing in a single click — no need to dig through the inbox.
A visual guide to every part of the live co-browse session: header, timer, tools (Pause, Draw, Highlight, Call) and the Cut button.
Co-browse sessions end on their own after 10 minutes or a stretch of inactivity. Learn how the limit works and how to keep helping afterward.
When the customer grants permission, you can click on their screen to guide them step by step. Here's how to turn it on and use it safely.
With remote control on, you can type for the customer in forms and text fields. Learn how to use remote typing without exposing their data.
Learn how to scroll the visitor's page with your own mouse during a co-browsing session to guide them to the right spot.
As you move your mouse over the co-browsing panel, the visitor sees an arrow with your name following your cursor. Here's how to use it to guide them.
Use the Pause button to freeze the mirror of the customer's screen while they enter sensitive data, and Resume to start seeing it again.
Use Draw mode inside a Co-browse session to sketch freehand over the customer's screen and guide them step by step.
Use Highlight mode to emphasize areas of the customer's screen, and the Clear marks button to wipe every annotation at once.
Start a browser-based voice call with the visitor during a Co-browse session, with no phone number to dial.
What your browser needs for the in-session voice call in Co-browse, and how to fix the most common microphone and connection problems.
During Co-browse, the customer's sensitive fields are hidden automatically. Here's how the masking works and what each side controls.
The keyword list Omnifox uses to detect and hide sensitive fields in Co-browse, and how to add your own.
Co-browse never starts silently. The visitor gets a request, decides whether to accept, and can stop at any time. Here is every step from the customer's side.
Co-browse is an add-on you turn on from Billing. Pick the plan based on how many simultaneous sessions your team needs and start sharing screens in minutes.
With the add-on active, you decide agent by agent who can start co-browse sessions, with a checkbox in Members. Here's how, and what the agent experiences.
Move up or down a Co-browse tier as your demand shifts, and keep an eye on how many concurrent sessions your team is running.
Which limits each Co-browse tier brings, which are fixed by design, and which an admin can tune per organization.
How the Co-browse add-on is billed: card or bank transfer, when it renews, and what happens when it expires.
Manage how the Co-browsing add-on is charged: update your card and cancel the add-on without touching your base plan.
Turn on browser push so you never miss a Co-browse request, and mute alerts outside business hours with Do Not Disturb.
Advanced guide to install the Omnifox widget on your site and tailor the consent prompt customers see before sharing their screen.
Use window.OmnifoxCobrowse.mask() and the data-rrweb-mask attribute to hide bespoke sensitive fields during co-browse.
Co-browse works in es/en/pt and hides sensitive data via per-language keywords. How the language is chosen and which terms trigger masking.
Missing button, no consent, timeout, remote control, annotations, audio, permissions, visible data and performance: causes and fixes.
How Co-browse works under the hood: live presence, the session lifecycle and one-shot tokens, rrweb capture, the file proxy, and the watchdogs that close stale sessions.
The screen-share icon depends on the conversation's channel, the add-on status, and the agent's individual permission.
Every Co-browse session closes for a specific reason, shown right in the agent's session panel.
Co-browse mirrors the visitor's screen live, but masks sensitive fields and never stores a recording.
If the real-time link drops during Co-browse, Omnifox retries on its own before giving up on the session.
Every Co-browse plan caps how many sessions can run at once; hitting the cap means waiting or upgrading.
Co-browse works on nearly any Webchat page, but two technical limits are worth knowing beforehand.