** ~1시간 AI 대화를 완전히 사용자 정의된 Amazon Connect PoC로 켭니다. — Classic Lex + AI Agent stack ** 또는 Agentic CX Designer(ACXD) 애플리케이션 · Amazon Bedrock 및 Strands SDK에 의해 구동

한국어 ·

---

데모

**Part 1 - Amazon Connect AI 에이전트 1 ~ 1 시간 **

https://github.com/user-attachments/assets/074983eb-43ed-4b04-a873-720795db847f] [T0]] [T0]] [T0]] [T0]] [T0]] [T0]] [T0]] [T0] [T0] [T0]] [T0] [T0] [T0]] [T0]] [T0] [T0] [T0] [T0] [T0]] [T0] [T0]] [T0] [T0] [T0]] [T0]] [T0] [T0] [T0]] https://github.com/user-attachments/assets/074983eb-43ed-4b04-a873-720795db847f] https://github.com/user-attachments/assets/074983eb-43ed-4b04-a873-720795db847f]]] https://github.com/user-attachments/assets/074983eb-43ed-4b04-a873-720795db847f]]]]]] [[https://github.com/user-attachments/assets/074983eb-43ed-4b04-a873-720795db847f]]]]]]] [[[[[[https://github.com/user-attachments/assets/074983eb-43ed-4b04-a873-720795db847f]]]]]]]]]]]]]] [[[[[[[https://github.com/user-attachments/assets/074983eb-43ed-4b04-a873-720795db847f]]]]]]]]]]]]]]]]]] [[[[[[[[[[[[[[[[[[[[[[

**Part 2 - 생성 된 에이전트와 라이브 통화 **

https://github.com/user-attachments/assets/64b4cd24-4653-4fed-86f9-4cd62866e1e2

---

v3.1의 새로운 기능 — ACXD만: 그냥 에이전트 CX 디자이너 응용 프로그램

이미 자신의 백엔드 API 및 접촉 흐름을 실행? Pick **ACXD 만 ** 에 시작 화면과 AICC Builder는 Agentic CX Designer 응용 프로그램을 혼자 구축합니다. CloudFormation, Lambda, OpenAPI spec, AI Prompt 또는 접촉 흐름 없음.

• ** 같은 대화 디자인. ** 창조적 여행, 당신의 말 요구 사항 위임, 동의 및 정체 게이트, 난간 및 FAQ 지식 기초는 ACXD 표적을 위해 정확하게 디자인됩니다.
• ** 짧은 인터뷰.** 데이터베이스, 인프라 또는 접촉 흐름 없음 질문. 인터뷰 기록 대신 각 작업의 끝점에

AICC Builder

---

Demo

Part 1 — Build an Amazon Connect AI agent in ~1 hour

https://github.com/user-attachments/assets/074983eb-43ed-4b04-a873-720795db847f

Part 2 — Live call with the generated agent

https://github.com/user-attachments/assets/64b4cd24-4653-4fed-86f9-4cd62866e1e2

---

What’s New in v3.1 — ACXD only: just the Agentic CX Designer application

Already running your own backend API and Contact Flow? Pick ACXD only on the start screen and AICC Builder builds the Agentic CX Designer application alone: no CloudFormation, Lambda, OpenAPI spec, AI Prompt or Contact Flow.

• The same conversation design. Generative journeys, the wording your requirements mandate, consent and identity gates, guardrails and the FAQ knowledge base are designed exactly as for the ACXD target.
• A shorter interview. No database, infrastructure or Contact Flow questions. Instead the interview records each operation’s endpoint on your API, the API’s base URL and the header it reads its credential from.
• Data requests that call your API. Each one calls WEBHOOK_URL plus the operation’s own path. The credential is an ACXD secret you enter when you deploy; it never enters the bundle.
• A contract for your backend. BACKEND-CONTRACT.md lists every call your API must answer: method and path, request and reply fields, and the formats the runtime actually delivers (values with or without separators, yes/no as words, dates in the business’s time zone, a 200 reply checked against the response schema).
• One command to deploy. ./deploy.sh asks for the workspace, API key, base URL and secret values it is missing and deploys the application; WIRING-GUIDE.md shows how to add the Agentic CX block to your Contact Flow.

The Classic and ACXD targets are unchanged.

📖 Bundle contents and deploy: docs/acxd-packaging.md

---