.svg?alt=media&token=ff97d6ac-c76d-45bc-af5b-04ffd317e2e2)
Genesys Cloud
The Cobrowse integration for Genesys Cloud may be installed from the App Foundry as a Premium App. Get links here.
Last updated
The Cobrowse integration for Genesys Cloud may be installed from the App Foundry as a Premium App. Get links here.
Last updated
The Cobrowse.io integration for Genesys Cloud may be installed from the App Foundry as a Premium App.
AppFoundry listing: https://appfoundry.genesys.com/filter/genesyscloud/listing/af9a5848-07fd-4021-bce0-663c02970566
Demo video: https://vimeo.com/919780454.
In total, there are two separate apps to install:
Cobrowse.io (Standalone App) - installed as usual via AppFoundry.
Cobrowse.io (Interaction) Widget - installed after the Standalone app. Go to Genesys Cloud at Admin -> Integrations -> + Integrations (shown below) and search for Cobrowse.io, selecting the Widget app.
For each Premium App, please activate it.
For information on what is different between these apps, see this article - https://support.cobrowse.io/genesys-cloud-standalone-and-widget-apps
Under Configuration you can select which Groups will have access to each app. Regular agents usually only require access to the Widget app. Supervisors and Administrators might require access to both apps, or just the Standalone app.
Roles: the Cobrowse.io apps will create two additional roles, one for Agents and one for Administrators. Please see this article for more information: https://support.cobrowse.io/genesys-user-roles
Group configuration: Groups can be configured to automatically assign Roles, so you may wish to control access based on Groups which use the default Cobrowse.io Roles. Group access must be configured in order for the apps to appear.
For the Cobrowse.io Interaction Widget, you can also specify the Queue Filtering. This will determine which agent queues the Widget app should appear for, in addition to any other filtering you have configured, e.g. Groups, Communication type, etc. Leaving this blank will mean no additional filtering is performed by queue.
For the Cobrowse.io Interaction Widget, you can also specify the Communication Type Filtering, e.g. chat,call,callback,email,sms,line,facebook,twitter,whatsapp. This will determine which communication types the Widget app should appear for, in addition to any other filtering you have configured, e.g. Groups, Queues, etc. Leaving this blank will mean no additional filtering is performed by communication type.
Possible communication types can be found in the Genesys docs: https://developer.genesys.cloud/routing/routing/available-media-types. Note that for Message, you only need to list the subtype name, e.g. open.
Please email us at hello@cobrowse.io before switching to your self-hosted instance.
If you are self-hosting the Cobrowse.io instance, you will need to replace "cobrowse.io" in both Application URLs with your self-hosted domain, e.g. https://<your self-hosted domain>/apps/genesys/index.html?langTag={{pcLangTag}}&environment={{pcEnvironment}}&env=cloud
If you wish to present the Agent's desktop from within Genesys Cloud you need to add display-capture to the Iframe Feature/Permissions Policy configuration within the Cobrowse Integration. Without this you won't be able to share the agents desktop.
Sometimes the Cobrowse.io default Roles might not appear immediately after app installation. This issue resolves itself after logging in and out, and if not, then after some time has passed. Please check again after a couple of business days. If the roles still do not appear then please contact us here: https://cobrowse.io/support-request.
Confirm that the Cobrowse.io Widget within the “Integrations” page within the Genesys Cloud account Admin space. The app should be installable there.
If not then it should also be available to install in the marketplace in the same location:
If the Widget app is still not appearing, then please check your Role, Group, Queue, and Communication Type filtering configuration for the Widget app. If you are testing in non-production, then removing any Queue and Communication filtering can help to see if the issue lies with this.
