Prerequisites for using Co-browse
Before you start your first Co-browse session, check the add-on, your permissions and the Webchat channel conditions.
Watch this step in the video · Requirements: your website chat
What this checklist is for
Co-browse lets you view and, with permission, control the screen of a visitor browsing your site — without them installing anything. For the button to appear and the session to start smoothly, a few conditions must be met. If the Co-browse button is missing or greyed out, it's almost always one of these.
Requirements
- The Co-browse add-on enabled for your organization. Co-browse is a paid add-on. An administrator turns it on from Billing; while it's off, the button doesn't even show in the Inbox.
- Agent permission to start Co-browse. Each agent needs the Start Co-browse capability enabled on their workspace role/user. Without it the button appears disabled with a "not allowed" hint.
- The conversation must be on the Webchat channel. Co-browse mirrors the page DOM, and only the Webchat widget can host it. On WhatsApp, Instagram, etc. the button doesn't appear (there'd be no page to share).
- The Webchat widget installed on your site. You need the widget script (loader) loaded on the pages where you want to offer Co-browse. It's the same chat widget; without it there's no screen to mirror.
- The visitor online at that moment. The session needs a live visitor tab with the widget loaded and heartbeating (presence). If they closed the tab, you can't start.
- Not exceeding the concurrent-session limit. Each organization has a cap on Co-browse sessions active at once. If it's maxed out, wait for one to end.
How to check you're ready
- In the Inbox, open a Webchat conversation with a connected visitor.
- The Co-browse button in the chat header should be active (not greyed).
- When you click it, the visitor receives the screen-sharing request.
If it doesn't work
- I don't see the button: confirm with an administrator that the add-on is on and that the conversation is Webchat.
- The button is greyed out: you're missing the Start Co-browse permission; ask an administrator.
- "Visitor not available": the person closed the page or lost connection. Ask them in chat to reopen the site.
- "Limit reached": too many active sessions; wait or close one.
Tips
- Privacy: during a session, passwords and card data are masked automatically, and the visitor can stop at any time.
- Grant Start Co-browse only to agents who actually handle Webchat, to keep control and avoid burning your session quota.
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.
-
The visitor consent modal
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.