AWS connect documentation change
Summary
Renamed 'Amazon Connect' to 'Connect Customer' throughout the document. Updated references to admin website, queues, and historical data sources to reflect the new service name.
Security assessment
The changes are purely branding/naming updates (Amazon Connect → Connect Customer) with no modifications to security protocols, access controls, or data handling procedures. No vulnerabilities, security incidents, or security features are mentioned or addressed in the diff.
Diff
diff --git a/connect/latest/adminguide/import-data-for-forecasting.md b/connect/latest/adminguide/import-data-for-forecasting.md index ef622657d..8ea31a58c 100644 --- a//connect/latest/adminguide/import-data-for-forecasting.md +++ b//connect/latest/adminguide/import-data-for-forecasting.md @@ -9 +9 @@ When to import dataImportant things to knowHow to import historical dataDelete i -# Import historical data for forecasting in Amazon Connect +# Import historical data for forecasting in Connect Customer @@ -11 +11 @@ When to import dataImportant things to knowHow to import historical dataDelete i -Amazon Connect requires sufficient historical data to learn the contact pattern and make good forecasts. By default, it uses historical contact data in Amazon Connect for forecasting. You can import historical data from external applications for Amazon Connect to use for forecasting. When you import data, Amazon Connect uses both its data and the imported data for forecasting. However, _the imported data takes precedence over the Amazon Connect data_. +Connect Customer requires sufficient historical data to learn the contact pattern and make good forecasts. By default, it uses historical contact data in Connect Customer for forecasting. You can import historical data from external applications for Connect Customer to use for forecasting. When you import data, Connect Customer uses both its data and the imported data for forecasting. However, _the imported data takes precedence over the Connect Customer data_. @@ -17 +17 @@ We recommend importing historical data from external applications in the followi - * **Insufficient historical data in Amazon Connect**. If you have less than one year of historical data in Amazon Connect, we strongly recommend that you extract historical data from your previous system and upload the data to Amazon Connect. It is fine to have data split between your Amazon Connect data and uploaded historical data. For example, if you want to generate forecasts on January 1, 2022, and you have nine months of historical in Amazon Connect (from April 1 to December 31, 2021), we recommend importing three additional months of data (from January 1 to March 31, 2022) to make a _continuous_ one-year historical data set available. + * **Insufficient historical data in Connect Customer**. If you have less than one year of historical data in Connect Customer, we strongly recommend that you extract historical data from your previous system and upload the data to Connect Customer. It is fine to have data split between your Connect Customer data and uploaded historical data. For example, if you want to generate forecasts on January 1, 2022, and you have nine months of historical in Connect Customer (from April 1 to December 31, 2021), we recommend importing three additional months of data (from January 1 to March 31, 2022) to make a _continuous_ one-year historical data set available. @@ -19 +19 @@ We recommend importing historical data from external applications in the followi - * **Incorrect historical data in Amazon Connect**. If the historical contact pattern is incorrect (for example, the contact volume is abnormally low on the day of a wide-spread power outage in the contact center), you can import data that is more representative to override historical data and correct for the anomaly. + * **Incorrect historical data in Connect Customer**. If the historical contact pattern is incorrect (for example, the contact volume is abnormally low on the day of a wide-spread power outage in the contact center), you can import data that is more representative to override historical data and correct for the anomaly. @@ -24 +24 @@ We recommend importing historical data from external applications in the followi -If you have more than one year of historical data in Amazon Connect, you can choose to skip data import and start [creating forecasts](./create-forecasts.html). +If you have more than one year of historical data in Connect Customer, you can choose to skip data import and start [creating forecasts](./create-forecasts.html). @@ -28 +28 @@ If you have more than one year of historical data in Amazon Connect, you can cho - * The data file must be a CSV file and it must be in the required format. If the file format and data don't meet the requirements, the upload does not work. We recommend downloading and using the template provided through the Amazon Connect admin website (see step 4 in How to import historical data) to help you prepare the historical data. + * The data file must be a CSV file and it must be in the required format. If the file format and data don't meet the requirements, the upload does not work. We recommend downloading and using the template provided through the Connect Customer admin website (see step 4 in How to import historical data) to help you prepare the historical data. @@ -36 +36 @@ Following are the requirements for imported data: - * `QueueName`: Enter the Amazon Connect queue name. + * `QueueName`: Enter the Connect Customer queue name. @@ -38 +38 @@ Following are the requirements for imported data: - * `QueueId`: Enter the Amazon Connect queue ID. To find the queue ID in the Amazon Connect admin website, on the left navigation, go to **Routing** , **Queues** , choose the queue, select **Show additional queue information**. The queue ID is the last number after `/queue/`. + * `QueueId`: Enter the Connect Customer queue ID. To find the queue ID in the Connect Customer admin website, on the left navigation, go to **Routing** , **Queues** , choose the queue, select **Show additional queue information**. The queue ID is the last number after `/queue/`. @@ -56 +56 @@ If duplicate data are found across multiple files, the last uploaded records are - 1. You have the original historical data (from Amazon Connect) from 7/1 to 8/1. + 1. You have the original historical data (from Connect Customer) from 7/1 to 8/1. @@ -86 +86 @@ The following image shows an example of what the data looks like in a CSV file t - 1. Log in to the Amazon Connect admin website with an account that has security profile permissions for **Analytics** , **Forecasting - Edit**. + 1. Log in to the Connect Customer admin website with an account that has security profile permissions for **Analytics** , **Forecasting - Edit**. @@ -90 +90 @@ For more information, see [Assign permissions](./required-optimization-permissio - 2. On the Amazon Connect navigation menu, select **Analytics and optimization** , **Forecasting** , and then choose the **Import Data** tab. + 2. On the Connect Customer navigation menu, select **Analytics and optimization** , **Forecasting** , and then choose the **Import Data** tab. @@ -113 +113 @@ The following image shows the download details file opened by using Notepad. It -You can delete previously imported historical data in Amazon Connect. +You can delete previously imported historical data in Connect Customer. @@ -125 +125 @@ After the imported historical data is deleted, the last previously uploaded data - * You have the original historical data (from Amazon Connect) from 7/1 to 8/1. + * You have the original historical data (from Connect Customer) from 7/1 to 8/1.