Claim record · Amazon Connect contact flows and routing profiles
Because block availability in Amazon Connect is scoped per flow type and flows cannot be imported across types, a routing design authored as a single flow on another vendor's designer generally has to be decomposed into several Amazon Connect flows of different types.
inference · verified 2026-09-07
- Vendor
- Amazon Web Services
- Product
- Amazon Connect Customer
- Subsystem
- flow-types
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-07
- Status
- inference
- Confidence
- 0.60
- Verified
- 2026-09-07
Sources
- Use the flow designer in Connect Customer to create flows — Amazon Web Services · tier 2 current vendor documentation · Section Choose a flow type, Important callout read together with the ten-row type table
Cite this claim
APA
WarmTransfer. (2026, September 7). Amazon Connect contact flows and routing profiles: claim amazon-connect-flows-crosswalk-needs-decomposition. WarmTransfer. https://warmtransfer.net/knowledge/claims/amazon-connect-flows-crosswalk-needs-decomposition
BibTeX
@misc{warmtransfer-claim-amazon-connect-flows-crosswalk-needs-decomposition,
title = {Amazon Connect contact flows and routing profiles: claim amazon-connect-flows-crosswalk-needs-decomposition},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/amazon-connect-flows-crosswalk-needs-decomposition},
note = {Claim amazon-connect-flows-crosswalk-needs-decomposition, verified 2026-09-07}
}