Builds & deployments
Understand how builds and deployments work in agentic CX designer
Building & deploying applications
Builds and deployments are related but are not the same thing.
In agentic CX designer, a build packages the current version of your application into a deployable snapshot. A deployment makes a selected build available for use through an Amazon Connect Customer contact flow.
What a build includes
A build assembles the current application configuration into a package.
This includes:
Attached flows
Routing descriptions
Default behavior
Guardrails
Slots
Language settings
Application settings
Other configuration available at the time the build is created
Because a build captures the application at a specific moment, edits made after the build are not included in a deployment until you create another build.
Why builds matter
Builds are required before application changes can be tested or released through the application experience.
A build is especially important when you change anything that affects how the application understands, routes, or responds to users.
At least one build is also needed for test chats to work when testing from a Canvas flow or on the application's Test tab.
Create a build
From your application's Deploy tab, you can create a new build, review build history, deploy a build or roll back to a previous build.
To create or manage builds:
Open Applications.
Select the application you want to build.
Open the Deploy tab.
Choose whether the build is for a development or production environment.
Select Build & deploy to start the build process.
When you start a build, agentic CX designer walks you through the build process:
Review validation checks, such as disconnected flow paths, incomplete configurations, etc.
Critical errors appear in red and should be resolved before creating the build, as they are more likely to cause a failed build. Warnings appear in yellow and should also be reviewed, so you understand the possible impact on the user experience.
Add a build description as a simple changelog.
Select Build.
When the build completes, it appears in the builds table. From there, you can review the build version, description, status, and environment usage.
For failed builds, select the build from the table to review the full failure message.
When to create a new build
Create a new build whenever you want to test or release meaningful application changes.
Examples:
You added or removed a flow from the application.
You updated the application’s default flows.
You changed custom slot configuration or values.
You updated routing descriptions.
You added languages or translations.
You changed guardrails.
You can create builds as often as needed while developing. Creating a build does not automatically push changes to an external environment unless you continue through deployment or promotion.
Test after building
After a build is created, you may use the test chat from a flow's Canvas or use the Test tab on the application.
Deployment
Once satisfied with testing in your agentic CX designer workspace, you can deploy your application for use in an Amazon Connect Customer flow.
From the application’s Deploy tab, use the builds table to manage which build will become active.
Only one build is active at a time.
To deploy a build:
Open an application > Select the application's Deploy tab.
From the build table, hover over the selected build's status.
Choose Deploy.
A deployment may take a few minutes with a successful deployment indicated by a Live status.
You may also return to a previous build version to deploy by hovering over a past build version, and choosing Rollback.
You may select a build from the build's table for additional details, such as the build ID, deployment key, and the ability to delete a deployment (takes your application offline).
Initial setup in Amazon Connect Customer
After your agentic CX designer application has been deployed for the first time, configure Amazon Connect Customer to route conversations through it.
1. Create or choose a contact flow
In Amazon Connect Customer, create or choose the contact flow that will route incoming calls or chats to your agentic CX designer application.
This contact flow should include the routing logic needed to connect the customer entry point to your deployed application.
2. Choose a voice persona
For voice-enabled conversations, use a Set voice block in the Amazon Connect Customer flow.
To configure voice:
Add a Set voice block.
Select the block.
Choose the voice provider.
Choose the language and voice persona.
Listen to available samples, if needed.
Confirm the selection.
3. Add the Agentic CX block
After your routing and voice setup is in place, add an Agentic CX block to the contact flow.
Configure the block by selecting:
The workspace where your application lives.
The name of the agentic CX designer application.
The deployed environment alias, such as Development or Production.
Any required block pathways, including escalation, error, or timeout handling.
The block tells Amazon Connect Customer which agentic CX designer application and environment to invoke during the conversation.
4. Publish the contact flow
Publish the Amazon Connect Customer contact flow to make it active and available for use with the appropriate phone numbers or chat endpoints.
Once the contact flow has been published, you do not need to republish it every time you update the agentic CX designer application. The Agentic CX block continues to point to the selected application and environment. Any newly deployed build for that environment becomes the version used in live conversations.
If you change the contact flow itself, or any configuration on the Agentic CX block, publish the contact flow again.
Last updated