Use the flow designer in Connect Customer to create flows

Publisher

Amazon Web Services

URL

https://docs.aws.amazon.com/connect/latest/adminguide/create-contact-flow.html

Published

unknown

Updated

unknown

Accessed

2026-09-07

HTTP status

200

License

Proprietary. (c) Amazon Web Services Inc. AWS Site Terms. No license notice printed in the fetched body.; no-redistribution; short excerpts and locators only

Source notes citing this source

• Because a published flow cannot have unconnected branches and no default flow is dedicated to errors, a generic 'error' prompt a caller hears most likely comes from a block the flow author wired to an Error branch, or from a Lex bot's own error handling; flow logs for the contact ID will show which. inferred in context
• Every connector in a flow must be connected to a block for the flow to publish; Save stores a draft and Publish activates the flow. in context
• AWS warns against placing sensitive information in a Transfer to agent flow because on a cold transfer the transferring agent disconnects before the transfer completes and the flow is then run on the caller, so its content is played to the caller rather than to the agent. in context
• 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. inferred in context
• Amazon Connect does not allow importing a flow into a flow of a different type, so switching type after starting means recreating the flow from scratch. in context
• In the flow designer, Save stores a draft of the flow and Publish activates it immediately, and every connector must be attached to a block before a flow can be published. in context
• The flow-type table documents ten flow types: Inbound flow, Campaign flow, Customer queue flow, Customer hold flow, Customer whisper flow, Outbound whisper flow, Agent hold flow, Agent whisper flow, Transfer to agent flow, and Transfer to queue flow. in context
• Each Amazon Connect flow type exposes only the blocks appropriate to its scenario, so choosing the wrong type at creation time can leave required blocks unavailable. in context

Cite this source record

APA

WarmTransfer. (2026, September 7). Use the flow designer in Connect Customer to create flows. WarmTransfer. https://warmtransfer.net/knowledge/sources/aws-connect-create-contact-flow

BibTeX

@misc{warmtransfer-aws-connect-create-contact-flow,
  title  = {Use the flow designer in Connect Customer to create flows},
  author = {{WarmTransfer}},
  year   = {2026},
  url    = {https://warmtransfer.net/knowledge/sources/aws-connect-create-contact-flow},
  note   = {Amazon Web Services, accessed 2026-09-07}
}