Co-browse for web messaging overview
- Genesys Cloud User 2, Genesys Cloud User 3
- Conversation > Cobrowse > Add permission
With Genesys Cloud co-browse for web messaging, customers can share their view of their current browser tab with an agent if they are browsing the website over https. After sharing starts, sharers can see where agents click on the page. Co-browse for web messaging provides the following features:
- Ability for agents to propose a co-browse session during an existing web messaging interaction
- Zero downloads for sharers
- No additional co-browse code required. Use your existing web messaging deployment snippet
- Configurable masking rules for sensitive data
- Cursor mirroring that allows sharer and viewer to see each others’ cursor movement
- Click annotations that show both parties where the other user clicks
- Sharing limited to one sharer and one viewer
- Supports Shift JIS encoding
- Industry standard encryption for both data at rest and data in transit
- Drawing annotations for sharer and viewer
How co-browse for web messaging works
Co-browse sessions have one sharer and one viewer:
- Sharer: The user who shares their screen, usually a customer.
- Viewer: The user who sees the shared screen, usually an agent. An agent can run one co-browse session at a time.
During a co-browse session, co-browse sends any changes to your website’s Document Object Model (DOM) to Genesys Cloud. The DOM describes the underlying structure of webpages. Co-browse then uses this information to build the same page the sharer sees on the viewer’s screen seamlessly. Co-browse watches for any change on the page, such as scrolling, clicking, or text typed in a form field. When there is a change to the DOM, co-browse sends the change to Genesys Cloud to update the viewer’s screen in real time.
Because co-browse watches for updates to the DOM, it is lightweight and fast. Co-browse sends only textual information, as opposed to video of the sharer’s screen. Co-browse also sends information only when there is a change instead of continuously streaming. This architecture also provides security, because when you configure masking, viewers cannot see any information that you mark as sensitive, and that information never leaves the sharer’s system.