FAQs: Genesys Cloud for Chrome
How is Genesys Cloud for Chrome extension usage calculated?
Genesys checks two criteria and bills accordingly:
- A user holds a Genesys Cloud for Chrome extension license.
- A user has a logged in presence at some point during the month (in either Genesys Cloud for Chrome or Genesys Cloud).
Do agent settings in the embedded clients remain after the browser cache is cleared?
Yes. Agent settings within the embedded client are saved on the server side, ensuring that these settings stay intact even after browser resets, cache clearing, or agent sign-outs.
Agents can customize the following settings in the embedded client:
- WebRTC
- Microphone
- Speaker
- Play ringtone on separate device
- Pop WebRTC Phone Window
- Advanced Mic Settings
- Automatic Mic Gain
- Echo Cancellation
- Noise Suppression
- Queue
- Prompt for queue on click-to-dial
- Remember the last selected queue
- Notifications
- Mute ringing for alerting interactions
- Show system notification for alerting interactions
- Ringtone
- Call Forwarding
- Forwarding Number
- Extension
These settings remain consistent across multiple browser tabs and persist even after agent sign-outs and browser resets.
For more information about the integrations, see About the Genesys Cloud browser extensions, About Genesys Cloud Embeddable Framework, About Genesys Cloud for Salesforce, and About Genesys Cloud for Zendesk.
Can I still use Google’s third-party deprecation flags for testing while using Genesys Cloud?
Yes. For customers using Chrome 120 version, Google recommends using the following flag:
chrome://flags/#tracking-protection-3pcd
For customers who use Chrome 121 or later version, see Set flags for testing in the Google documentation.
Why aren’t notifications appearing?
You selected Show system notification for alerting interactions in the client, but you are not receiving any notifications.
- Check your browser notification settings to make sure that they allow notifications from Genesys Cloud. For example, if your Genesys Cloud organization is located in North American (East), then make sure that your browser notification settings allow notifications from https://apps.mypurecloud.com.
- Check your computer system settings to make sure that they allow your browser to display system notifications.
For more information about the integrations, see About the Genesys Cloud browser extensions, About Genesys Cloud Embeddable Framework, About Genesys Cloud for Salesforce, and About Genesys Cloud for Zendesk.
Name change implications for the embedded clients
In 2020, Genesys changed the name of PureCloud to Genesys Cloud. Because older managed packages, administrator configurations, and code for the embedded clients could contain references to the former product name, you could continue to see the term PureCloud in your integration.
For more information about the name change, see Did PureCloud get a new name?
For more information about the integrations, see About the Genesys Cloud embedded clients.
Can Genesys Cloud for Chrome be used with other browsers?
Genesys Cloud for Chrome is not officially supported for use with other browsers.
Do the Genesys Cloud embedded clients allow users to use click-to-dial on behalf of a queue?
Absolutely! With Genesys Cloud for Salesforce, Genesys Cloud for Chrome, and Genesys Cloud for Firefox, and Genesys Cloud Embeddable Framework, you can configure the Click-to-Dial settings to prompt users for queues when they click a phone, email, or sms link. Genesys Cloud for Zendesk allows users to input a queue name before dialing a number from a phone or sms link, or sending an email from an email link.
See information about click-to-dial in the following integrations:
- Genesys Cloud Embeddable Framework
- Genesys Cloud for Chrome
- Genesys Cloud for Firefox
- Genesys Cloud for Salesforce
- Genesys Cloud for Zendesk
For more information about the integrations, see About the Genesys Cloud browser extensions, About Genesys Cloud Embeddable Framework, About Genesys Cloud for Salesforce, and About Genesys Cloud for Zendesk.