Enhance your support experience by starting a co-browsing session with a Customer. This allows you to view precisely what your Customer is seeing, even highlight or point to areas on your website that you’d like to bring your Customer’s attention to. Seeing what your Customer can see can make it much easier to assist them when they need help.
Here are a few tips to keep in mind before you start a cobrowse session:
You can initiate the cobrowse feature from any Channel. However, the process to initiate a session while on a call is slightly different from that of other Channels.
You’ll be prompted to sign in to your Screenmeet account in Gladly approximately once a week. Work with your Manager if you need a ScreenMeet account.
ScreenMeet’s cobrowse feature works on mobile devices.
Follow your company policy on how to manage your Availability during a co-browse session.
From the Customer Profile, click , then select Cobrowse with ScreenMeet.
The ScreenMeet widget tab opens next to the call Composer.
Depending on whether you signed into ScreenMeet recently, you’ll see either a Sign In or Cobrowse button in the widget.
If you see Sign In – Click Sign In to bring up ScreenMeet’s sign-in modal. Enter your ScreenMeet email address and password, then click Sign In. Once authenticated, you’ll see the Cobrowse option.
From the ScreenMeet widget, click Cobrowse.
From the New Cobrowse Session screen, click Create Session to generate a pin number.
All ScreenMeet sessions are recorded, so there’s no need to click Record Cobrowse Session.
With the Customer on your company’s website, ask them to locate the “Co-browse with…” link (or something similarly named) that is likely located in the footer area of your company website. This will bring up the pin entry modal (shown below), where the Customer enters the pin you generated and then clicks Accept.
You can also copy and send the invite link from the Conversation Timeline to the Customer through another Channel (if available), like email or SMS. This should open the exact pin entry modal.
Once the Customer enters their pin to allow the session, clickView Screen on the widget, which opens a new browser tab so you can see what the Customer is seeing. This officially starts the co-browsing session.
A recording of the ScreenMeet session is started in the Conversation Timeline. When the co-browsing session ends, clicking the link will take you to ScreenMeet, where you can view the recording.
Start a co-browsing session over Messaging Channels #
Remaining available in the Messaging Channel means you’ll continue to be routed new messaging requests while on a co-browsing session with a Customer. We suggest marking yourself Unavailable in this Channel to stop receiving new requests so you can focus on the co-browse session or follow your company policy on how to manage Availability during a co-browse session.
From the Customer Profile, click , then click Cobrowse with ScreenMeet.
The ScreenMeet widget tab opens next to the messaging Composer.
You’ll see either a Sign In or Cobrowse button in the widget, depending on if you’ve signed into ScreenMeet recently.
If you see Sign In – Click Sign In to bring up ScreenMeet’s sign-in modal. Enter your ScreenMeet email address and password, then click Sign In. Once authenticated, you’ll see the Cobrowse option.
From the ScreenMeet widget, clickCobrowse.
From the New Cobrowse Session screen, then click Create Session to generate a pin number.
All ScreenMeet sessions are recorded, so there’s no need to click Record Cobrowse Session.
Go back to the messaging tab and tell the Customer how to start a co-browsing session, along with the pin number.
The Customer can access the pin entry modal in one of two ways:
From your website – Ask them to locate the “Co-browse with…” link (or something similarly named) that is likely located in the footer area of the website. This will bring up the pin entry modal and have the Customer enter the pin you generated, then click Accept.
Direct link – Copy the invite link from the Conversation Timeline and send it over the Messaging session. Clicking on this link opens the pin entry modal. Ask the Customer to enter the pin you generated, then click Accept.
Once the Customer enters their pin to allow the session, click View Screen on the widget, which opens a new browser tab so you can see what the Customer is seeing. This officially starts the co-browsing session.
The Conversation Timeline starts a recording of the ScreenMeet session. When the co-browsing session ends, clicking the link will take you to ScreenMeet, where you can view the recording.
You’ll need to multitask by sending your messages to assist the Customer while working on the cobrowse session. If you feel that calling the Customer will create a better experience, offer to call the Customer. If they agree, click , then click Call.
The To field should auto-populate with the Customer’s number. If it doesn’t, type it manually, then add their phone number as part of their contact details.
The session officially ends if the Customer clicks End on their ScreenMeet session. When they do, you’ll see “This session has been closed” on your screen.
If the Customer closes the browser tab for the cobrowse session, your co-browsing tab (not in the widget) will show that the Customer is disconnected or navigated Away from the page. The session is still technically active, and they can come back by re-entering the pin in the modal or using the invitation link.
Back in Gladly, the ScreenMeet widget returns to the Cobrowse screen. Click Close ScreenMeet to close the ScreenMeet widget.
Phone Call – If the call ends simultaneously, you’ll see the Notes Composer, where you can jot down your notes about the call. Otherwise, Notes will appear once the call ends.
Messaging – Click , then Notes to leave additional notes about the cobrowse session.
Click Close & Next to close the Conversation, or Next if you need to keep the Conversation open.
From Gladly, click End Session from the ScreenMeet widget. You’ll be asked to confirm your request, click End Session again.
The ScreenMeet widget returns to the Create New Session screen.
Phone Call – If the call ends simultaneously, you’ll see the Notes Composer, where you can jot down your notes about the call. Otherwise, Notes will appear once the call ends.
Messaging – Click , then Notes to leave additional notes about the cobrowse session.
Click Close & Next to close the Conversation, or Next if you need to keep the Conversation open.
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
Cookie
Duration
Description
__cf_bm
29 minutes
This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_wpfuuid
1 year 1 month 4 days
This cookie is used by the WPForms WordPress plugin. The cookie is used to allows the paid version of the plugin to connect entries by the same user and is used for some additional features like the Form Abandonment addon.
BIGipServer*
session
Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user.
cookielawinfo-checkbox-advertisement
1 year
Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category.
cookielawinfo-checkbox-analytics
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional
11 months
The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance
11 months
This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
CookieLawInfoConsent
1 year
CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie.
PHPSESSID
session
This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.
viewed_cookie_policy
11 months
The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Cookie
Duration
Description
li_gc
5 months 27 days
Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.
lidc
1 day
LinkedIn sets the lidc cookie to facilitate data center selection.
UserMatchHistory
1 month
LinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Cookie
Duration
Description
_ga
1 year 1 month 4 days
Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.
_ga_*
1 year 1 month 4 days
Google Analytics sets this cookie to store and count page views.
_gd_session
4 hours
This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded.
_gd_visitor
1 year 1 month 4 days
This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads.
_sp_id.*
1 year 1 month 4 days
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
_sp_ses.*
30 minutes
Snowplow sets this cookie to store user information that is created when a user first visits a site and is updated on subsequent visits.
AnalyticsSyncHistory
1 month
Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie.
mf_user
3 months
Mouseflow sets this cookie to identify whether a visitor is new or returning.
vuid
1 year 1 month 4 days
Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website.
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Cookie
Duration
Description
_mkto_trk
1 year 1 month 4 days
This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo.
bcookie
1 year
LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.
bscookie
1 year
LinkedIn sets this cookie to store performed actions on the website.
li_sugr
3 months
LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant.