How the consent flow works and what the visitor sees
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.
Watch this step in the video · If the customer says no
Co-browse lets you watch a webchat visitor's screen in real time so you can help them finish a purchase or fix an error. The key thing: it never starts without permission. This article walks through the consent flow step by step and shows exactly what the customer sees.
When it applies
Co-browse only works in Webchat conversations (the widget on your site), because it needs a web page to mirror. On WhatsApp, Instagram or SMS the button doesn't even appear.
How it starts (agent side)
- The agent opens the webchat conversation in the Inbox.
- In the chat header they click the Co-browse icon (a small screen, next to the call button).
- This sends a request to the visitor. The session is NOT active yet — it waits for their answer.
What the visitor sees
As soon as the agent requests the session, the visitor gets a box on top of the site titled “Screen sharing request”, showing the agent's name and two buttons:
- Accept — starts sharing the screen.
- Decline — dismisses the request, nothing happens.
Below it they read a clear note: “Passwords and card data are masked automatically. You can stop sharing at any time.”
During the session
While sharing, the visitor sees a persistent “Sharing screen” label with a Stop button. A few details worth knowing:
- The agent sees a mirror of the page; password and card fields are masked and are never transmitted.
- If the connection drops, the label changes to “Reconnecting…” and, if it's fully lost, to “Connection lost”.
- If the agent pauses, the visitor sees “Paused” and mirroring stops.
- Sessions last at most 10 minutes and then end on their own.
The visitor is always in control
The customer can hit Stop at any moment and the session ends instantly, no matter what the agent is doing. Consent is not “once and forever”: every new session asks for permission again.
Verify it
- As an agent: after requesting, you should see a “waiting for answer” state until the visitor accepts.
- As a test visitor: open your own webchat in another window and have a teammate start co-browse; you should see the request box.
If it doesn't work
- No co-browse button: confirm the conversation is Webchat and that the add-on is active. Your user also needs permission to start sessions.
- The visitor doesn't see the request: make sure the webchat widget is loaded and not blocked by a script blocker.
- It cuts out right away: usually the visitor's connection; when it returns, the label goes from “Reconnecting…” back to normal.
Tips
- Before clicking the button, announce it in the chat: “I'll send you a request to view your screen and guide you.” Acceptance goes way up.
- Reassure the customer that passwords and cards are masked automatically.
Related articles
Related articles
-
What Co-browse is and how to enable it
Co-browse lets you see the customer's screen in real time to guide them better. Learn how to enable it.
-
Co-browse complete guide
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: add-on tiers and pricing
Co-browse is bought separately on any plan: Standard 50 USD/mo (3 concurrent sessions), Pro 90 (6), Business 150 (10) and custom Enterprise.
-
How to start a Co-browse session with a customer
Step by step to invite the customer to share their screen and guide them in real time.
-
Prerequisites for using Co-browse
Before you start your first Co-browse session, check the add-on, your permissions and the Webchat channel conditions.