AWS prescriptive-guidance documentation change
Summary
Updated service name references from 'Amazon Connect' to 'Connect Customer' throughout the document
Security assessment
The changes are purely cosmetic branding updates replacing 'Amazon Connect' with 'Connect Customer'. No security vulnerabilities, configurations, or features are mentioned or modified. The security-related content about 'security profiles' remains unchanged.
Diff
diff --git a/prescriptive-guidance/latest/strategy-migration-connect/user-journeys.md b/prescriptive-guidance/latest/strategy-migration-connect/user-journeys.md index cce6cad7e..f1a07c1ab 100644 --- a//prescriptive-guidance/latest/strategy-migration-connect/user-journeys.md +++ b//prescriptive-guidance/latest/strategy-migration-connect/user-journeys.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Strategies for migrating your contact center to Amazon Connect](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Strategies for migrating your contact center to Connect Customer](welcome.html) @@ -23 +23 @@ In this phase, you gather existing user journey flows and designs, and pass them - * Contact flow designer – Instead of using a drawing tool like draw.io or Visio, consider using the [contact flow designer](https://docs.aws.amazon.com/connect/latest/adminguide/concepts-contact-flows.html#concepts-visual-editor) that’s included in Amazon Connect to develop and document the user journey over screen-share. Use [prompt block](https://docs.aws.amazon.com/connect/latest/adminguide/play.html) placeholders for steps that should be confirmed later (for example, the exact wording or import of queuing message audio file). Use a simple [text-to-speech (TTS)](https://docs.aws.amazon.com/connect/latest/adminguide/text-to-speech.html) prompt block to record the owner who is confirming the step (for example, "Queue A message .wav file to be provided by John Smith"). This enables you to perform end-to-end testing of the user journey and routing logic in parallel. + * Contact flow designer – Instead of using a drawing tool like draw.io or Visio, consider using the [contact flow designer](https://docs.aws.amazon.com/connect/latest/adminguide/concepts-contact-flows.html#concepts-visual-editor) that’s included in Connect Customer to develop and document the user journey over screen-share. Use [prompt block](https://docs.aws.amazon.com/connect/latest/adminguide/play.html) placeholders for steps that should be confirmed later (for example, the exact wording or import of queuing message audio file). Use a simple [text-to-speech (TTS)](https://docs.aws.amazon.com/connect/latest/adminguide/text-to-speech.html) prompt block to record the owner who is confirming the step (for example, "Queue A message .wav file to be provided by John Smith"). This enables you to perform end-to-end testing of the user journey and routing logic in parallel. @@ -47 +47 @@ Design documentation is optional. It depends on the size and complexity of the c -Amazon Connect configuration is available by using [AWS CloudFormation templates and APIs](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Connect.html) in infrastructure as code (IaC) tools. Use DevOps tools to build and manage Amazon Connect components such as security profiles and contact flows. If you design flows by using the contact flow designer, you can include the flows in your IaC DevOps tools and manually export them as JSON files. +Connect Customer configuration is available by using [AWS CloudFormation templates and APIs](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/AWS_Connect.html) in infrastructure as code (IaC) tools. Use DevOps tools to build and manage Connect Customer components such as security profiles and contact flows. If you design flows by using the contact flow designer, you can include the flows in your IaC DevOps tools and manually export them as JSON files. @@ -51 +51 @@ Amazon Connect configuration is available by using [AWS CloudFormation templates -You can also start building contact flows in a development environment while other AWS accounts are being created, and export the flows into the test and production environments when their Amazon Connect instances are ready. +You can also start building contact flows in a development environment while other AWS accounts are being created, and export the flows into the test and production environments when their Connect Customer instances are ready. @@ -57 +57 @@ The test phase consists of two sequential subphases: - * Functional testing – Performed iteratively over agile sprints as contact flows are created in Amazon Connect. Performed by: functional test team + * Functional testing – Performed iteratively over agile sprints as contact flows are created in Connect Customer. Performed by: functional test team @@ -66 +66 @@ The test phase consists of two sequential subphases: -In this phase, agent and user credentials are uploaded into the Amazon Connect production instance so that users can log in. You should upload contact flows only after they successfully pass UAT testing in the previous phase. Claim a temporary phone number in the Amazon Connect dashboard and assign it to the contact flows. These phone numbers will be visible only to the project team, who will use them to place test calls. The project team often runs a selection of UAT scripts during this process. This approach provides preparatory (_pipe-clean_) testing of the user journey before the system goes live and real agents can access the workflow. At the scheduled go-live time, this temporary number is replaced by the publicly routable number used by customers―this is the point where you cut over to the new system. If necessary, you can roll back changes by swapping the number back to the legacy service line. +In this phase, agent and user credentials are uploaded into the Connect Customer production instance so that users can log in. You should upload contact flows only after they successfully pass UAT testing in the previous phase. Claim a temporary phone number in the Connect Customer dashboard and assign it to the contact flows. These phone numbers will be visible only to the project team, who will use them to place test calls. The project team often runs a selection of UAT scripts during this process. This approach provides preparatory (_pipe-clean_) testing of the user journey before the system goes live and real agents can access the workflow. At the scheduled go-live time, this temporary number is replaced by the publicly routable number used by customers―this is the point where you cut over to the new system. If necessary, you can roll back changes by swapping the number back to the legacy service line.