Customer experience automation is evolving beyond traditional chatbots and rigid decision trees. Modern systems need to understand customer intent, retrieve information, interact with business applications, execute multi-step workflows, and know when to involve a human.
AWS is bringing these capabilities together with Amazon Connect Customer Agentic CX Designer (ACXD) — a visual, no-code environment for building, testing, and optimizing agentic customer experiences.
What makes ACXD interesting is its combination of two approaches:
Let's explore how it works and how developers can think about building a practical customer experience with it.
ACXD provides a visual workspace where teams can design customer-facing applications without building every interaction from scratch.
It supports experiences that can:
The important architectural idea is that AI does not need to control every decision. Business-critical operations can remain deterministic, while AI handles flexible conversations and reasoning.
A simplified ACXD architecture looks like this:
Customer
|
v
Amazon Connect Customer
|
v
Agentic CX Designer (ACXD)
|
+----------------------------+
| |
v v
Deterministic Workflows Agentic AI
| |
v v
Business Rules Knowledge Retrieval
Validation Natural Language
Routing Multi-step Reasoning
| |
+-------------+--------------+
|
v
Data Requests / APIs
|
v
Business Applications
|
v
Customer Response
|
Human Escalation
This is a conceptual view rather than a complete deployment diagram. The actual implementation depends on the application, integrations, and customer journey.
Imagine an online store receiving hundreds of customer requests every day.
Customers commonly ask:
A traditional chatbot might rely on fixed menus and predefined answers. An agentic experience can understand different ways of expressing the same request and coordinate the appropriate workflow.
For example:
Customer: "I ordered a laptop last week. Can you tell me when it will arrive?"
A possible interaction:
The AI handles the conversational experience, while the order system remains the source of truth.
An agentic customer experience becomes useful when it can work with real business data.
Depending on the architecture, integrations can connect the application to:
For example, a Lambda function can act as an integration layer between the customer experience and an internal application. Where private resources are involved, Lambda can be configured to run inside a VPC and access permitted private services.
A simplified integration flow:
ACXD Application
|
v
Data Request / Integration
|
v
AWS Lambda or API
|
v
Internal Business System
|
v
Structured Response
|
v
ACXD Application
Keep integrations focused and apply least-privilege permissions. The customer-facing AI should not receive unrestricted access to internal systems.
One of the most important design decisions is knowing which tasks should use AI and which should use explicit business logic.
| Requirement | Recommended approach |
|---|---|
| Understand customer intent | Agentic AI |
| Answer policy questions | Trusted knowledge retrieval |
| Check order status | API or data request |
| Validate refund eligibility | Deterministic business rules |
| Apply approval limits | Deterministic workflow |
| Route a complex issue | Defined routing logic |
| Handle an unresolved request | Human escalation |
For example, AI can understand that a customer wants a refund. However, refund eligibility should be checked against the company's actual policy and order data.
This separation makes the application more predictable, testable, and suitable for business-critical workflows.
Customer-facing AI needs reliable information and clear boundaries.
A knowledge source can provide approved information such as:
Guardrails help define what the application should and should not do.
Consider these practices:
The objective is not simply to make an AI assistant more capable. It is to make the experience useful, controlled, and trustworthy.
A visual workflow can look correct and still behave unexpectedly when customers interact with it.
ACXD provides testing capabilities to help validate applications and their underlying flows.
A practical testing strategy should cover:
Application tests
Flow tests
Routing tests
Integration tests
Guardrail tests
Use the available debugger and testing tools to investigate unexpected flow behavior before deployment.
Building an application is only one part of the lifecycle.
A sensible delivery process is:
The Agentic CX block provides the connection point for invoking an ACXD application from an Amazon Connect Customer flow.
After deployment, review conversation history, transcripts, evaluations, analytics, guardrail activity, and flow traversal information where available.
Look for patterns such as:
Use these observations to improve the application incrementally.
AWS Builder Center provides a hands-on workshop titled:
Build, Test, Optimize: Hands-On with Amazon Connect Customer agentic CX designer (ACXD)
The workshop provides a prebuilt environment and ten industry scenarios. Participants can select a scenario and build, test, and deploy voice and digital customer experiences without writing application code.
It is listed as an intermediate-level, approximately four-hour workshop.
This is a useful way to explore the designer and understand its workflow before applying the concepts to a real customer support use case.
Amazon Connect Customer Agentic CX Designer became generally available on September 2, 2026.
AWS announced availability in multiple AWS Regions, including:
Always check the current AWS documentation for the latest regional availability and feature details.
Useful resources:
Amazon Connect Customer Agentic CX Designer represents an interesting direction for customer experience development.
Instead of choosing between traditional workflows and generative AI, teams can combine both: deterministic logic for controlled business outcomes and agentic AI for flexible customer conversations.
For developers and architects, the real opportunity is in designing the right boundaries between AI, business systems, knowledge sources, and human support.
A successful customer experience is not just one that can answer questions. It is one that can complete useful tasks reliably, protect customer data, and recognize when a human should take over.
What would you build first with ACXD — an order-tracking assistant, a technical support agent, or a customer onboarding workflow?
I'd be interested to hear your ideas in the comments.