Co-browse troubleshooting

Missing button, no consent, timeout, remote control, annotations, audio, permissions, visible data and performance: causes and fixes.

Jun 26, 2026

Watch this step in the video · Common problems

What it is and when it helps

This guide gathers the most common co-browse problems and how to fix them, grouped by symptom. It's useful for both agents and admins.

The co-browse button doesn't appear

The Start co-browsing button (next to the call button in the chat header) only shows when all three conditions hold:

  1. The conversation is Webchat. WhatsApp, Instagram, SMS, etc. have no DOM to share, so the button isn't rendered.
  2. The organization has the Co-browse add-on active (Billing → Co-browse).
  3. Your user has the Co-browse permission enabled by an admin (Settings → Workspace members, Co-browse column).

If the add-on or permission is missing, in some cases you'll see a dimmed icon with a tooltip explaining it ("ask your admin to enable the add-on" / "Your admin has not given you permission to co-browse").

The customer doesn't consent

On start, the agent sees "Waiting for the customer to consent…". The customer gets the "Screen sharing request" banner with Accept / Decline.

  • If they tap Decline, you'll see "The customer declined the request" and the session won't start. Ask again via chat.
  • If they don't respond, the request stays pending. Hit Cancel and retry.
  • Banner not showing on the customer side? They must have the Webchat widget open in an active tab; in a background tab the widget may not load the bundle.

The session ends on a timeout

Sessions have a maximum duration set by the add-on plan. Near the end, both sides see a warning ("X seconds left"). When it expires, the agent sees "Session ended due to time limit". Start it again if you need more time.

Remote control isn't responding

Your clicks, scroll and typing are mirrored to the customer (you'll see the hint "Your clicks, scroll and typing are mirrored to the customer").

  • If nothing happens on the customer side, check whether Pause is on: while paused the DOM is frozen. Tap Resume.
  • Some elements on the customer's site (third-party iframes, native OS menus) can't be controlled remotely.
  • A poor connection shows "Reconnecting…"; wait a few seconds for it to recover.

Annotations don't show

The toolbar has Draw, Highlight and Clear marks.

  • Turn on Draw and drag over the area; release to send the stroke.
  • Highlight drops a pulsing halo where you tap.
  • Clear marks wipes everything drawn. If marks don't appear, confirm the session is streaming and not paused.

Audio (voice call) fails

From the session you can tap Call for an in-browser voice call.

  • "Couldn't access the microphone. Check your browser permissions": the customer (or you) blocked the mic. Enable it in the site permissions and retry.
  • "Your browser doesn't support voice calls": use a modern browser (recent Chrome, Edge, Safari).
  • To end the call without ending the session, tap Hang up.

Permissions: an agent can't co-browse

Ask an admin to go to Settings → Workspace members and tick the Co-browse box for that agent. The permission is also validated server-side, so without it the action is blocked even if forced.

Sensitive data is showing that shouldn't

Passwords and cards are masked automatically, but a bespoke field can slip through. Mask it with the data-rrweb-mask="true" attribute or window.OmnifoxCobrowse.mask('#field'). See the advanced masking article.

It's slow or choppy

  • Co-browse streams the DOM live; on very heavy pages or weak connections there can be lag.
  • Use Pause while the customer isn't showing you anything, to relieve the stream.
  • Close bandwidth-hungry tabs or apps on both ends.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp