Track
Contact flows
The flow is the product the caller hears. A missing error branch is a dropped call.
6 rooms. Open one, then use its quiz.
Flow types are not one canvas
Each flow type only offers the blocks that make sense there. A hold flow is not a place to transfer to a queue and hope.
The block catalog, grouped by job
You do not memorize fifty icons. You group them by the job they do.
Attributes are the only memory the next system gets
If it is not an attribute, the CRM, the whisper, and the CTR cannot see it.
Modules are how you stop copying flows
A copied inbound flow drifts. A module has one published body.
Every error branch is a product decision
An unconnected error output hangs up. That is a choice, even if you did not mean it.
The flow language is how instances share a design
The designer is a view. The JSON is what you review and promote.
Sources and go deeper
- Use the flow designer in Connect Customer to create flows - Amazon Connect Customer AWS docs. last checked 2026-10
- Flow block definitions in the flow designer in Connect Customer - Amazon Connect Customer AWS docs. last checked 2026-10
- Connect Customer Flow language - Amazon Connect AWS docs. last checked 2026-10
- Troubleshoot contact flow errors in Amazon Connect | AWS re:Post community. last checked 2026-10
- Interactive voice response - Wikipedia Wikipedia. last checked 2026-10
sources.json (flows-types) sources.json (flows-blocks) sources.json (flows-attributes) sources.json (flows-modules) sources.json (flows-errors) sources.json (flows-language)