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.

Nov 02, 2026

This is the complete guide to Omnifox co-browse, in 32 chapters: the add-on, permissions, the visitor radar, identified visitors, consent and declining, remote control (cursor, typing, clicks, scrolling), data masking, highlight and draw, pause, voice call, page changes and reloads, the time limit and how a session ends. The PDF manual has the same chapters with screenshots.

1. What co-browse is and what it is for

With co-browse you see exactly what your customer sees on your web page, in real time, from the Omnifox inbox: what they type, what they choose and where they are.

It helps when someone gets stuck on a form, can't find a button, doesn't understand an option or is afraid of making a mistake when paying. Instead of explaining by chat, you guide them yourself: you point, type or click for them.

2. It is not screen sharing

Note an important difference: this is not screen sharing. The customer doesn't share their computer, their other tabs or their notifications. You only see your own website, the page where the Omnifox chat is installed.

No video is transmitted either: the structure of the page travels, and your browser redraws it. That's why it looks sharp, uses very little bandwidth and sensitive data can be hidden before it leaves the customer's browser.

3. The add-on and its tiers

Co-browse is an add-on you subscribe to separately, in Billing, Add-ons. There are three tiers depending on how many simultaneous sessions your team needs: three on Standard, six on Pro and ten on Business. For more, Enterprise is tailored.

The card shows the active tier, the simultaneous sessions, the maximum length of each session, which is ten minutes, and since when it has been active. This account is on the Pro tier.

4. Requirements: your website chat

The only technical requirement is having the Omnifox chat installed on your site: co-browse travels with the same widget, there's nothing else to install. As soon as the add-on is active, the widget enables it by itself.

That's why the co-browse button appears in your website chat conversations, and not in WhatsApp or Instagram ones: there's no page of yours to look at there.

5. Who can start sessions

Not everyone on the team needs to be able to see a customer's screen. The account owner decides in Settings, Members: the Co-browse column has a switch per person.

The account owner can always do it. You turn everyone else on or off here; for example, we turn Andrea's off and back on. The change is immediate, without having to log out.

Anyone without the permission sees the co-browse button disabled in the conversation, with a notice that their admin hasn't given them permission to co-browse.

6. The visitor radar

In the menu, Cobrowse opens the radar: the live list of people browsing your site right now with the chat loaded.

Each row shows who they are, how long they've been there and which page they're on, and it updates by itself when the visitor changes page or leaves.

7. Identified visitors

Here is Lucía Andrade, who signed in to her customer area. She hasn't written in the chat yet, but the radar already knows her name.

That's because the My account page passes the name and email of the signed-in person to the widget, with window dot omnifoxSettings or the data visitor attribute. Until she writes, her Connect button is grey: co-browsing is always tied to a conversation.

Now Lucía opens the chat and writes that she wants to check her policy. At that moment her conversation is created, already with her name and email, and the button on her row becomes active.

8. Search the radar

With many visitors at once, the search box filters by name, email or page. We type Lucía and only she remains.

Anonymous visitors show up too, as unnamed visitors, with the page they're viewing.

9. Connect from the radar

Connect & co-browse opens Lucía's conversation and, in the same step, asks her permission to see her page: ideal for offering help to someone who has been on a difficult page for a while.

The co-browse panel opens with the message Waiting for the customer to consent.

10. If the customer says no

On Lucía's side the notice appears: the agent wants to view and control this page, explaining that passwords and cards are hidden automatically and that she can stop at any time.

Lucía presses Decline. The agent sees the notice that the customer declined the request, and sees absolutely nothing of her screen. Permission always belongs to the customer, and it's asked for every time.

11. Ask again and accept

If she changes her mind later, you can ask again. The agent presses Connect & co-browse again, and this time Lucía accepts.

Instantly, the agent sees Lucía's customer area just as she sees it, and Lucía sees the Sharing screen label on her screen, with the time left and the button to stop.

12. The agent ends the session

When you're done, end it yourself with the panel's End session button. The session closes for both: the label disappears for Lucía and the agent stops seeing her screen.

Ending as soon as you finish is good practice: nobody should keep looking at someone else's screen longer than needed.

13. Start from a conversation

The most common way is to start it from the chat. Daniel wrote in through the website: he's filling in the quote and doesn't know which plan to choose. In his conversation header is the Start co-browsing button.

When you press it, Daniel is asked for permission. He accepts, and the panel opens with his page live.

14. The live screen

At the top, the customer's name, the time left in the session and a connection quality indicator, with the latency in milliseconds.

Below, the tools: pause, draw, highlight, clear marks and voice call. And at the bottom, the reminder that your clicks, scrolling and typing reach the customer's screen.

15. The customer sees your cursor

When you move the mouse over the page, Daniel sees a cursor with your name, Valeria, on his screen. That way he always knows what you're looking at and that nothing is hidden.

And every click you make leaves a small circle on his screen, so he sees it coming.

16. Type for the customer

To type, click a field and type. The agent types the make and model of Daniel's car.

On Daniel's side, the text appears in his form before his eyes, as if he were typing it himself.

17. Click for the customer

Clicks get through too. When everything is complete, the agent presses the quote button on Daniel's page.

And the confirmation appears on his screen: the quote was sent to his email. Daniel didn't have to look for the button.

18. Scroll the page

With the mouse wheel over the panel you scroll the customer's page, for example to show them the benefits further down.

Daniel sees his page move, and he can take back control at any time: he keeps using his mouse and keyboard normally.

19. What the customer types stays hidden

Look at the fields: Daniel typed his name, his ID number and his card, but the agent only sees dots. Co-browse hides everything typed into text fields, and it also recognizes sensitive fields by their name, such as card, ID number, password, account, security code or passport, in Spanish, English and Portuguese.

The hidden content is replaced in the customer's browser, before it's sent, so that data never reaches the agent.

20. Hide other parts of your page

If your page shows other private data, like a policy number or a balance, you can hide it yourself. Just add the data rrweb mask attribute to the element in your site's code.

On the Seguros Cumbre page, the policy number has that attribute: Daniel sees it normally, and the agent sees it hidden.

21. Highlight

To guide without touching anything, use Highlight. With the tool active, a click marks a spot on the customer's screen.

For example, the agent highlights the card field so Daniel checks the number, without typing in that field herself.

22. Draw and clear marks

With Draw you sketch freehand over the page: an arrow, a circle or an underline. Daniel sees the stroke instantly, over his own form.

The strokes fade by themselves after a while, and Clear marks removes them all at once.

23. Pause and resume

If the customer needs a moment alone, for example to check something private, Pause stops the stream: the agent stops receiving what happens on their screen.

Resume shows it live again, without asking for permission again.

24. Voice call

If typing gets slow, Call starts a voice call in the same browser, with no phone. Daniel gets the notice, Valeria Cueva wants to talk to you, and can accept or decline; to talk, his browser asks for microphone permission.

While they talk, the customer's label shows On call, and co-browsing carries on as before. Hang up ends the call and the session continues.

25. Minimize, full screen and size

The panel can be minimized to keep handling other chats: a pill stays at the bottom with the customer's name and the time. One click opens it again.

You can also view it in full screen, to read better, or resize it by dragging the edge. The session stays active in the meantime.

26. The customer changes page

The session isn't lost if the customer browses your site. Daniel moves to the home insurance page.

The agent keeps seeing him on the new page, with the same session and the same time left, without asking permission again.

27. If the customer reloads

And if he reloads the page? Daniel presses reload in his browser.

The session resumes by itself in a few seconds: the label appears on his screen again and the agent sees his page live again.

28. Time limit

Each session lasts up to ten minutes, and the panel counter always shows it. When only a few seconds are left, Omnifox warns you, and when it reaches zero the session closes by itself.

If more time is needed, a new session is started, again with the customer's permission.

29. The customer ends the session

The customer is in control: at any time they press Stop on the Sharing screen label, and the session ends.

The agent gets the notice that the customer ended the session, and the panel closes. The chat conversation stays open, to keep helping in writing.

30. Simultaneous sessions and limits

Simultaneous sessions count for the whole account: your tier defines how many co-browsing sessions can be running at the same time across your whole team, six on the Pro tier.

There are browser-side limits: co-browse shows your site, not other tabs or other applications, and content living inside an iframe from another domain, like an external payment form, isn't visible.

31. Privacy and good practices

Co-browse doesn't record video: it streams the page structure live, with sensitive data already hidden, and none of it is stored when the session ends.

Good practices: explain to the customer why you want to see their screen before asking for permission, don't ask them to type passwords while you watch, hide anything private your page shows with data rrweb mask, and end the session as soon as you finish.

32. Common problems

Is the Start co-browsing button disabled? You're missing the permission in Members. Doesn't it appear? The conversation isn't from your website chat. The customer doesn't see the notice? They must have your site's tab open with the chat loaded.

Nothing shows after accepting? Wait for the first image, a few seconds; if the customer's connection is weak, the panel warns that it's reconnecting. The call doesn't connect? The customer has to allow the microphone.

Was this helpful?

Related articles

Message us on WhatsApp