Genesys Co-Browse
Extend web messaging, voice or chat interactions with Co-browse
What's the challenge?
Your customer is frustrated because they’re having trouble on your website. Your agent is frustrated because he can’t see where the customer is struggling. The customer has to describe what’s on the screen; the agent has to articulate where to click. It’s cumbersome — and results in long handle times.
What's the solution?
Improve first contact resolution by letting agents “show and tell” with your customers through a co-browsing session, using real-time annotations, comments, or even the ability to take control of the customer’s screen. There’s zero footprint for customer ease and content masking for peace of mind.
Use case overview
Story and business context
A customer and a contact center agent are having a conversation over the phone or through a web messaging or web chat session. During the conversation, the ability to see and control the customer’s browser through co-browsing functionality enables the agent to convey information more effectively and get the customer’s issue resolved more quickly.
Use case benefits
| Benefit | Explanation |
|---|---|
| Improved Customer Experience | Mitigate customer frustration by providing a better method to serve and assist customers thereby reducing customer effort |
| Improved First Contact Resolution | Optimize the customer service experience by initiating a co-browse session with the customer to resolve their request the first time |
| Increased Revenue | Reduce shopping cart abandonment and increase online conversion rates. |
| Reduced Handle Time | Leverage annotations, comments and browser control to aid quick resolution. |
Summary
During a call or a web messaging or a chat session between a customer and an agent, the customer can initiate a co-browse session with the agent, so both the agent and the customer share the same instance of the browser. This session enables the agent to provide direct support to a customer trying to complete a request on the company’s website.
Use case definition
Business flow
- The customer and agent are connected via a web messaging session, a chat session or a voice call.
- The agent may propose to the customer to start a Co-browse session to support him/her on the website. For security reasons, the customer and agent have to initiate the Co-browse session.
- Call only: A security ID is displayed to the agent if he/she clicks the ‘screen sharing link’ in the Genesys Cloud CX UI. This security key is then given over the phone by the agent to the customer and entered by the customer. The customer enters the security key into the website to start the co-browse session.
- Web messaging only: The customer clicks the “Accept” option when asked the question if they want to share their screen.
- Chat only: The customer clicks the ‘start sharing’ option when asked the question if they want to share their screen.
- When the session is established, the Genesys Cloud CX UI displays a view of the website in the browser window the customer is using. Agents start Co-browse sessions in read-only mode. In read-only mode, the customer and the agent can see each other’s mouse pointer but the agent cannot enter any information into the web page, click buttons, or navigate the customer’s browser. The agent does have the ability to highlight sections of the page (by clicking) or to add annotations to the page to guide the customer.
- If the agent needs to enter information into the web page or to navigate the browser, he/she can send the customer a ‘request navigation’.
- Once the customer accepts this request, the agent can navigate, fill forms, and click hyperlinks on the web page. Sensitive Data can be masked before presenting to the agent, and agent controls (the ability to fill certain fields or submit forms) can be blocked through instrumentation. The customer can revoke the Write Mode at any time, returning the agent to read-only mode.
- The Co-browse session ends when any of the following events occurs:
- The customer chooses to end the Co-browse session
- The agent chooses to end the Co-browse session
- The primary web messaging, chat or voice interaction is transferred or ended by either the customer or the agent
- For a web messaging session, after 2 minutes of inactivity the Co-browse session will be disconnected.
- For a WebChat session after 15 minutes of inactivity the session will be disconnected. There is no timeout when using voice.
The primary voice, web messaging or chat interaction can continue even when Co-browse has ended.
Business and distribution logic
N/A
User interface & reporting
Agent UI
N/A
Reporting
Real-time Reporting
No real-time co-browse data is available currently, this data will be added in a future release.
Historical Reporting
- Interactions Detail View: Co-Browse sessions are shown in the Interactions Timeline information.
- Interaction History for External Contacts: Co-browse sessions are shown in the interaction history screen for related conversations.
- Additional co-browse metrics are available via the Genesys Cloud CX API’s, not all of this data is currently exposed in the various performance views.
Customer-facing considerations
Interdependencies
| All of the following required: | At least one of the following required: | Optional | Exceptions |
|---|---|---|---|
General assumptions
Co-browse with Web Messaging:
- Customer has Genesys Cloud CX 2 licensing for their organization.
- Customer has prepared their website to work with co-browse (https://help.mypurecloud.com/articles/set-up-co-browse-for-web-messaging/)
- Customer has added masking to private data on their website to control what can and cannot be seen by the agent.
Co-browse with Voice and Chat:
- Customer has Genesys Cloud CX 3 licensing for their organization.
- Customer has prepared their website to work with co-browse (https://help.mypurecloud.com/articles/set-co-browse/)
- Customer has added tags to private data on their website to control what can and cannot be seen by the agent.
Customer responsibilities
- Customer is responsible for integration of the solution into the company website.
- Customer is responsible for tagging information and fields on their website that need to be hidden from the agent during a co-browse session, or agent controls that need to be blocked (such as Submit form).
Related documentation
Document version
V 1.1.2 last updated February 10, 2023
