Owners: embed the widget and customize the consent prompt
Advanced guide to install the Omnifox widget on your site and tailor the consent prompt customers see before sharing their screen.
Watch this step in the video · If the customer says no
Co-browse runs inside the Omnifox web chat widget: the customer shares their screen from the same window where they chat, always with explicit consent. This advanced guide is for owners and admins who install the widget and want to understand how that consent is requested.
Requirements
- Admin role in the workspace.
- The Co-browsing add-on active on the organization.
- Access to edit your site's HTML (or your tag manager).
1. Get and embed the widget code
- Open Settings → Channels and select your Webchat channel.
- Open Customize Widget to set colors, language, and branding.
- Copy the Embed Code shown in the panel.
- Paste it right before the
</body>tag on every page where you want chat. - Publish your site and reload — the floating widget button should appear.
The same snippet enables both chat and Co-browse. You don't need a second script: co-browsing is lazy-loaded when the agent requests it.
2. Verify the installation
- In the Webchat channel panel check Detected installations — it should register your domain.
- Open your site in an incognito tab and confirm the widget loads with no console errors.
3. How consent is requested
When an agent starts Co-browse, the customer sees a prompt to Accept or Decline screen sharing. This prompt is built-in and automatic — there is nothing to write or configure from the panel. What matters to know:
- The text is fixed and ships translated into Spanish, English, and Portuguese. The language is picked automatically from the session
localeor your<html>langattribute; declare<html lang="en">(ores/pt) so it shows in the right language. - Consent is requested for every session — never "once and for all." Each time an agent requests Co-browse, the customer decides again.
- The prompt already tells the customer that passwords and card data are masked automatically and that they can stop sharing at any time.
The agent only sees the screen while the customer keeps the session open; closing it ends access immediately.
If it doesn't work
- The widget doesn't appear: confirm the snippet is before
</body>and that your CDN/cache has purged the old version. - No Co-browse button: check the add-on is active and the agent has the "Can start co-browse sessions" permission.
- The customer doesn't see the consent prompt: usually widget cache — force a hard reload or re-publish.
Tips
- Keep the consent text clear and short — it raises the acceptance rate.
- If you use a tag manager, load the snippet on every template, not just the home page.
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.