AWS connect documentation change
Summary
Renamed 'Amazon Connect' to 'Connect Customer' throughout the document to reflect a branding change
Security assessment
This is purely a branding/nomenclature update with no changes to security requirements or features. All security-related content (e.g., cookie requirements, browser restrictions) remains functionally identical, only with the updated product name.
Diff
diff --git a/connect/latest/adminguide/connect-supported-browsers.md b/connect/latest/adminguide/connect-supported-browsers.md index 5a44ed172..d89356677 100644 --- a//connect/latest/adminguide/connect-supported-browsers.md +++ b//connect/latest/adminguide/connect-supported-browsers.md @@ -9 +9 @@ Mobile browsersSupported browsers and mobile OS for in-app, web, and video calli -# Browsers supported by Amazon Connect +# Browsers supported by Connect Customer @@ -15 +15 @@ Mobile browsersSupported browsers and mobile OS for in-app, web, and video calli -Before you work with Amazon Connect, verify that your browser is supported using the following table. +Before you work with Connect Customer, verify that your browser is supported using the following table. @@ -30 +30 @@ For more requirements, see [Agent headset and workstation requirements for using -The Amazon Connect console, Contact Control Panel (CCP), and agent workspace do not support mobile browsers. However, your agents can forward the audio portion of the call to their mobile device. For instructions, see [Forward calls in the Amazon Connect CCP to a mobile device (iPhone, Android)](./forward-calls-to-mobile-device.html). +The Connect Customer console, Contact Control Panel (CCP), and agent workspace do not support mobile browsers. However, your agents can forward the audio portion of the call to their mobile device. For instructions, see [Forward calls in the Connect Customer CCP to a mobile device (iPhone, Android)](./forward-calls-to-mobile-device.html). @@ -63 +63 @@ On July 22, 2024, Google announced a change in its plans regarding third-party c -**For businesses that embed the Contact Control Panel (CCP) into a custom workspace** : If your agents use Google's opt-in mechanism to disable third-party cookies, it will cause authentication issues when they use the CCP. Amazon Connect relies on third-party cookies to facilitate authentication. Ensure that third-party cookies are enabled in your agents' browser settings to avoid any authentication issues while using the CCP. +**For businesses that embed the Contact Control Panel (CCP) into a custom workspace** : If your agents use Google's opt-in mechanism to disable third-party cookies, it will cause authentication issues when they use the CCP. Connect Customer relies on third-party cookies to facilitate authentication. Ensure that third-party cookies are enabled in your agents' browser settings to avoid any authentication issues while using the CCP. @@ -67 +67 @@ On July 22, 2024, Google announced a change in its plans regarding third-party c -As of February 2024, Firefox prevents the Amazon Connect CCP from being embedded in another application. As a result, agents are prevents from handling contacts. This is because Firefox enabled Total Cookie Protection by default for all users, including users who have set their [Enhanced Tracking Protection setting as Standard](https://support.mozilla.org/en-US/kb/introducing-total-cookie-protection-standard-mode) . +As of February 2024, Firefox prevents the Connect Customer CCP from being embedded in another application. As a result, agents are prevents from handling contacts. This is because Firefox enabled Total Cookie Protection by default for all users, including users who have set their [Enhanced Tracking Protection setting as Standard](https://support.mozilla.org/en-US/kb/introducing-total-cookie-protection-standard-mode) . @@ -82 +82 @@ To prevent impacts to your users (agents), we recommend that your users complete -The Amazon Connect CCP conforms to Firefox microphone usage guidance, and only has access to connect to the user's microphone when the CCP tab is in focus. This may lead to missed call scenarios when the CCP tab is not in focus, for example, if the agent focused on a different tab or application. +The Connect Customer CCP conforms to Firefox microphone usage guidance, and only has access to connect to the user's microphone when the CCP tab is in focus. This may lead to missed call scenarios when the CCP tab is not in focus, for example, if the agent focused on a different tab or application. @@ -91 +91 @@ The Amazon Connect CCP conforms to Firefox microphone usage guidance, and only h -Microsoft Edge version 146, released on March 13, 2026, introduced a change to its autoplay policy behavior that affects Amazon Connect agents. In Edge v146, when the `AutoplayAllowed` enterprise policy is set to "Disabled", it now maps to "Block" — preventing websites from autoplaying media. In Edge versions 92 through 144, this same setting mapped to "Limit" and permitted audio playback on active WebRTC streams. +Microsoft Edge version 146, released on March 13, 2026, introduced a change to its autoplay policy behavior that affects Connect Customer agents. In Edge v146, when the `AutoplayAllowed` enterprise policy is set to "Disabled", it now maps to "Block" — preventing websites from autoplaying media. In Edge versions 92 through 144, this same setting mapped to "Limit" and permitted audio playback on active WebRTC streams. @@ -108 +108 @@ This issue only affects customers using Microsoft Edge version 146 or later who -Configure the **AutoplayAllowlist** policy in Microsoft Edge to explicitly permit autoplay on your Amazon Connect instance URL. +Configure the **AutoplayAllowlist** policy in Microsoft Edge to explicitly permit autoplay on your Connect Customer instance URL. @@ -121 +121 @@ To configure: -Add your Amazon Connect instance URL to the AutoplayAllowlist policy. The URL format is: +Add your Connect Customer instance URL to the AutoplayAllowlist policy. The URL format is: