Limitations on Mobile and on Pages with Cross-Origin Iframes
Co-browse works on nearly any Webchat page, but two technical limits are worth knowing beforehand.
Watch this step in the video · Common problems
Co-browse mirrors whatever the visitor sees in their browser, but there are two scenarios where the mirror isn't 100% complete — due to how screen-capture technology fundamentally works, not a bug.
On mobile devices
- When a session starts, the chat widget automatically minimizes on the visitor's phone (the conversation panel closes) so the agent sees the actual page underneath instead of the chat window covering the whole screen.
- The visitor still sees the sharing indicator/bubble, just not the open conversation, for as long as the co-browse session lasts.
- Touch interaction (tap, scroll) mirrors the same way mouse input does on desktop, though on small screens movements can feel less precise than on a full-size monitor.
On pages with cross-origin iframes
- Co-browse can mirror content inside iframes that share the same domain as the main page.
- If the customer's page embeds an iframe from a different domain — a third-party payment widget, an embedded video, a form hosted elsewhere — that content cannot be mirrored: the agent sees a blank area there, while the rest of the page renders normally.
- This is a browser security boundary (browsers block reading content from a different-origin iframe), not an Omnifox limitation.
Example
A customer is on a store's checkout page that embeds a card-payment form from an external payment provider inside an iframe. The agent sees the rest of the page clearly — cart, buttons, address — but the payment form's box shows up empty.
Tips
- If you need to walk a customer through a field inside a cross-origin iframe, do it over voice/chat in parallel instead of relying on the visual mirror for that specific area.
- On responsive sites, test on a simple page first to confirm the mirror looks right before relying on it with a real customer.
Troubleshooting
"There's a blank patch in the middle of the page": that's almost always a cross-origin iframe (payments, video, maps). It's not a failure — it's expected browser-security behavior.
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.