Consent and Masking in Co-Browsing: What the Agent Sees and What They Don't
How co-browsing protects the customer: explicit permission before it starts, passwords and payment data always hidden, short sessions and a log.
In this article
The first reaction most people have to "the agent can see your screen" is a flinch. Fair enough: they have banking tabs open, a half-written email, a password manager. Consent and masking in co-browsing are the two mechanisms that make the flinch unnecessary, and a support team that can explain them in one sentence gets far more "yes" answers than one that cannot.
This guide is written for two audiences at once. For the team, it lays out what happens before, during and after a session in Omnifox, so every agent describes it the same way. For customers and for the people who write your privacy policy, it lists exactly what the agent sees, what they do not, and what they cannot do, with wording you can adapt.
Before the session: nothing happens without a yes
Co-browsing in Omnifox runs on the web chat widget on your site. It cannot be started silently. The sequence is fixed.
- The agent requests a session from the chat conversation.
- The customer sees a prompt in the widget explaining that the agent wants to view the page with them.
- The customer accepts or declines. Only after accepting does the agent see anything.
- If the customer declines, nothing is shared and the chat continues as before.
Nothing bypasses the prompt. The request message should be honest about scope and length; a reasonable template:
Agent: I'd like to look at this page with you so I can point at the field that's causing the error. You'll see a prompt to accept. I'll only see this tab on our website, your password and card fields are hidden from me, and either of us can end it at any time. It usually takes two or three minutes. Shall I send the request?
During the session: the scope is your website's tab
Once the customer accepts, the agent's view is limited in three ways that are worth spelling out because customers assume the opposite.
Only the tab of your website. The agent sees the page of your site the customer is on. Not other tabs, not other windows, not the desktop, not files. If the customer switches to another site, the agent does not follow. Co-browsing is not a video feed or a screenshot of the screen; it synchronizes the page of your site, which is why it cannot see anything outside it.
Passwords and form fields masked by default. Password fields and form inputs are hidden from the agent's view. They appear as masked elements; the agent cannot read what is in them and cannot type into them. The customer fills those in themselves, always.
Additional masking by the site owner. If your pages show data that should never reach an agent (an account balance, a national insurance number, a medical field), the site owner can mask those elements too. Masking is configured once and applies to every session.
Within that scope the agent can point at elements and perform guided clicks, which is enough to steer a customer through a form, a settings page or a checkout without ever handling their data.
| The agent sees | The agent does not see | The agent cannot do |
|---|---|---|
| The page of your site the customer is on | Other browser tabs or windows | Type into masked fields |
| Unmasked text, buttons, menus, error messages | The desktop, files, other applications | Read passwords or card numbers |
| Where the customer's page is scrolled | Masked form fields and any element the site owner has masked | Open a session without the customer accepting |
| Their own pointer and guided clicks | Anything after the customer leaves your site | Continue past ten minutes or after either side closes |
After the session: it ends, and there is a record
Sessions have a hard ceiling of ten minutes. They also end the moment either the agent or the customer closes them. This matters for trust: a customer who accepts is not signing up for an open-ended window into their browsing.
Once a session ends, Omnifox keeps a record: which agent, which contact, when, and how long. That log is what lets a supervisor answer "who ran a session with this customer last Tuesday?" and what lets you show, if asked, that a session was short and consented to.
A closing message keeps the customer informed:
I've ended the co-browsing session now, so I can no longer see the page.
The address is corrected and your order went through. Anything else, just
write here.
How to explain it to a customer in one sentence
Agents freeze when they have to explain a technical safeguard mid-conversation. Give them one sentence and have everyone use it:
"I'll only see this page of our site, your passwords and card details stay hidden from me, and you can end it whenever you like."
Three claims, all true, all short. If the customer wants more, add that nothing is installed and that the session stops by itself after ten minutes.
Wording for your privacy policy
Your policy should mention co-browsing if you offer it. This is general guidance, not legal advice; confirm the wording with your own counsel, particularly around GDPR and UK GDPR if you serve European or British customers, and state privacy laws such as the CCPA in the US.
A starting draft:
Assisted browsing (co-browsing). With your explicit consent, given through a prompt in our chat widget, a support agent may view the page of our website you are on in order to help you. The agent sees only that page on our site, not other tabs, applications or files on your device. Password and payment fields, and other sensitive elements we designate, are hidden from the agent and cannot be edited by them. Sessions last no longer than ten minutes and end when you or the agent close them. We keep a record of the date, duration and agent for each session. You may decline or end a session at any time without affecting the support you receive.
Points to review with counsel:
- Whether the session log counts as personal data under your applicable regime and how long you retain it.
- Whether any page you might co-browse displays special-category data (health, financial) and whether it is masked.
- How you describe the lawful basis (consent is the natural one here, given the prompt).
- Whether your customer-facing terms should reference the policy section.
The security and privacy in co-browsing article goes deeper into the technical side; the step-by-step in helping a customer complete checkout with co-browsing shows masking at work on the page where it matters most.
A short checklist for the team
- Request only after the customer has described a problem on your site.
- Use the one-sentence explanation every time, before sending the request.
- Never ask the customer to read out anything that is masked.
- End the session as soon as the fix is done, and say so in the chat.
- Note the outcome in the conversation so the log and the history match.
- Review masking whenever a new page or form goes live on the site.
Frequently asked questions
Can an agent start co-browsing without the customer knowing?
No. The agent sends a request from the chat, the customer sees a prompt and must accept; until then the agent sees nothing, and a decline ends the matter.
What exactly can the agent see during co-browsing?
Only the tab of your website the customer is on, with passwords, form fields and any elements the site owner has masked hidden from view. Other tabs, applications and files are never visible.
Can the agent type into the customer's forms?
Not into masked fields. The agent can point and perform guided clicks to steer, but passwords, payment details and other masked inputs are entered by the customer alone.
How long does a session last and is there a record?
At most ten minutes, ending sooner when either side closes it. Omnifox keeps a log of the agent, contact, time and duration of each session.
Make the safeguard part of the pitch
Consent and masking are not fine print; they are the reason a customer says yes. Put the one-sentence explanation in your agents' snippets, update the policy, and try a session on your own site with a 7-day free trial. Plans and session limits are on the co-browsing page.
Ready to try it in your business?
Bring WhatsApp, Instagram, Messenger, email and calls into one inbox, and let AI handle the first reply. Set it up today.
7 days free. No credit card required.
Read more
-
Asking for Google Reviews by Text Without Being Pushy
-

12 Proactive Chat Messages for Your Website, by Page (Ready to Copy)
-
Handling STOP, HELP and Opt-Out Management the Right Way
-
Shared Inbox vs Help Desk Tickets vs Email Aliases
-

The Official API: The Only Safe Way to Scale on WhatsApp
-

How to Keep Your WhatsApp Bulk Messages Out of Spam
-

Unified Customer History Across Every Channel
-

How to build an IVR step by step: a DTMF options menu
Comments (0)
No comments yet. Be the first to share your thoughts.
Leave a comment
Your email is never published. Comments are moderated before appearing.