AWS Security ChangesHomeSearch

AWS connect documentation change

Service: connect · 2026-05-10 · Documentation low

File: connect/latest/adminguide/create-a-multi-step-and-multi-channel-journey.md

Summary

Updated branding from 'Amazon Connect Outbound Campaigns' to 'Connect Customer Outbound Campaigns'. Enhanced time zone configuration by adding options to detect recipient's local time zone using profile attributes (primary only or all available) and clarified active communication settings.

Security assessment

Changes involve product rebranding and feature enhancements for time zone detection. No vulnerabilities, exploits, or security weaknesses are mentioned. The added configuration options for time zone detection don't address security controls but improve operational functionality.

Diff

diff --git a/connect/latest/adminguide/create-a-multi-step-and-multi-channel-journey.md b/connect/latest/adminguide/create-a-multi-step-and-multi-channel-journey.md
index 32fc50fd8..90021472e 100644
--- a//connect/latest/adminguide/create-a-multi-step-and-multi-channel-journey.md
+++ b//connect/latest/adminguide/create-a-multi-step-and-multi-channel-journey.md
@@ -34 +34 @@ On the Outbound Campaigns page, you will have two options to create an outbound
-You can control how often each recipient is contacted by setting communication limits for the Journey. Simply specify the maximum number of messages a recipient can receive within a defined time frame (e.g., per day, week, or month). If a recipient has already received the maximum number of communications within any of the time frames you set, Amazon Connect Outbound Campaigns will automatically skip that recipient and they won’t receive additional messages from the Journey.
+You can control how often each recipient is contacted by setting communication limits for the Journey. Simply specify the maximum number of messages a recipient can receive within a defined time frame (e.g., per day, week, or month). If a recipient has already received the maximum number of communications within any of the time frames you set, Connect Customer Outbound Campaigns will automatically skip that recipient and they won’t receive additional messages from the Journey.
@@ -40 +40 @@ If you set a limit of 4 communications per 2 days and 6 communications per 2 wee
-Amazon Connect Outbound Campaigns considers any time a recipient has been contacted, regardless of the recipients interaction with the message, as a communication. For example, a phone call ending in a voicemail is still considered a communication. Amazon Connect Outbound Campaigns will adjust the count of communications if it can determine that the message never reached the end user, and will always err on the side of over-counting. In addition to setting communication limits for individual journeys, you can also define **Total Communication Limits** at the instance level. These limits control how many messages a recipient can receive across all journeys running within your Amazon Connect instance over a specific time frame. If a recipient reaches the specified limit—for example, 10 communications per week—they will be excluded from further messaging across **all journeys** until the time window resets. This helps ensure that overall message volume stays within acceptable boundaries.
+Connect Customer Outbound Campaigns considers any time a recipient has been contacted, regardless of the recipients interaction with the message, as a communication. For example, a phone call ending in a voicemail is still considered a communication. Amazon Connect Outbound Campaigns will adjust the count of communications if it can determine that the message never reached the end user, and will always err on the side of over-counting. In addition to setting communication limits for individual journeys, you can also define **Total Communication Limits** at the instance level. These limits control how many messages a recipient can receive across all journeys running within your Amazon Connect instance over a specific time frame. If a recipient reaches the specified limit—for example, 10 communications per week—they will be excluded from further messaging across **all journeys** until the time window resets. This helps ensure that overall message volume stays within acceptable boundaries.
@@ -50 +50 @@ All communications across all journeys in the active state are considered when d
-Amazon Connect Outbound Campaigns measures a day as a rolling 24 hour window from the current moment.
+Connect Customer Outbound Campaigns measures a day as a rolling 24 hour window from the current moment.
@@ -62 +62 @@ In order for the Journey to determine appropriate time to attempt communication
-  * Standard time zone: The time zone selected will be used for all recipients. Select this option if you know the time zone of all recipients in your segment or if you want all communications sent at the same moment in time.
+  * **Standard time zone** : The time zone selected will be used for all recipients. Select this option if you know the time zone of all recipients in your segment or if you want to send all communications in the same time zone.
@@ -64 +64,11 @@ In order for the Journey to determine appropriate time to attempt communication
-  * Recipient's local time zone: Amazon Connect Outbound Campaigns use the provided Address and/or the area code from the Phone Number to infer the recipients time zone. If the time zone cannot be determined (for example, if either the [Address](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-customer-profiles_CreateProfile.html#connect-connect-customer-profiles_CreateProfile-request-Address) and/or [Phone Number](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-customer-profiles_CreateProfile.html#connect-connect-customer-profiles_CreateProfile-request-PhoneNumber) is missing or is invalid), the recipient will be dropped from the Journey. Select this option if it's important to send communications to recipients only during their specific local times.
+  * **Recipient's local time zone** : Connect Customer Outbound Campaigns use profile attributes to infer each recipient's time zone. If the time zone cannot be determined, the recipient will be dropped from the Journey. Select this option if it's important to send communications to recipients only during their specific local times.
+
+When you select **Recipient's local time zone** , you configure the following settings:
+
+    * **Detect recipient's local time zone** — Choose the method used to detect the recipient's time zone. Connect Customer Outbound Campaigns use a profile's [Address](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-customer-profiles_CreateProfile.html#connect-connect-customer-profiles_CreateProfile-request-Address) and/or [Phone Number](https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-customer-profiles_CreateProfile.html#connect-connect-customer-profiles_CreateProfile-request-PhoneNumber)'s area code to infer the recipient's time zone.
+
+    * **Profile attributes to use for time zone detection** — Choose the scope of profile attributes used for time zone detection:
+
+      * **Primary only** — Uses only the primary phone number and/or address attributes from the recipient's customer profile to determine the time zone.
+
+      * **All available** — Uses all phone number and/or address attributes from the recipient's customer profile to determine the time zone.
@@ -71 +81 @@ In order for the Journey to determine appropriate time to attempt communication
-The **Active communication time** represents the times during which Amazon Connect Outbound campaigns may send communications for this journey. To add active communication times: Select the channel. Alternatively, select Apply to all channels to apply the active communication times to each channel. Select the day of the week to configure. You can add multiple active communication times for each day, if desired. Select the time frame during which Amazon Connect Outbound campaigns can send communications on the given day. 
+The **Active communication time** represents the times during which Connect Customer Outbound campaigns may send communications for this journey. To add active communication times: Select the channel. Alternatively, select Apply to all channels to apply the active communication times to each channel. Select the day of the week to configure. You can add multiple active communication times for each day, if desired. Select the time frame during which Amazon Connect Outbound campaigns can send communications on the given day. 
@@ -87 +97 @@ Specify when you want your journey to begin:
-  * **Expiry Date and Time** : The date and time at which Amazon Connect Outbound campaigns should end the journey. An expired journey appears with a **Completed** status a few moments after expiry time.
+  * **Expiry Date and Time** : The date and time at which Connect Customer Outbound campaigns should end the journey. An expired journey appears with a **Completed** status a few moments after expiry time.