Amazon Connect now supports the use of flow modules across all Connect flows, allowing you to reuse common logic and functionality beyond inbound customer experiences. Flow modules organize repeatable logic and create common reusable functions across the customer experiences you build with flows. For example, you can now use a module to share information about a customer’s recent transactions in an agent whisper flow, preparing the agent with relevant details and leveraging functionality that was previously only available as part of inbound flows.
Additionally, you can now use flow modules within other modules, enabling you to build complex logic by stitching together pre-built intermediary steps under a single module. For example, a credit card eligibility module can invoke other modules that check credit scores, verify income, and review payment history before making a final determination. This modular approach allows you to build reusable components that can be combined and extended as your business requirements evolve.
To learn more about these features, see the Amazon Connect Administrator Guide. To understand recent enhancements to flow module capabilities, see our AWS blog post. This feature is available in all AWS regions where Amazon Connect is offered. To learn more about Amazon Connect, the AWS cloud-based contact center, please visit the Amazon Connect website.
Categories: general:products/amazon-connect
Source: Amazon Web Services
Latest Posts
- Amazon Connect flow modules now work across all flow types and within other modules

- (Updated) Microsoft Purview | Data lifecycle Management cmdlet connectivity change [MC1213770]
![(Updated) Microsoft Purview | Data lifecycle Management cmdlet connectivity change [MC1213770] 3 pexels cottonbro 5473955](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- (Updated) InfoPath 2013 client and InfoPath Forms Services in SharePoint Online will reach end of support in July 2026 [MC616550]
![(Updated) InfoPath 2013 client and InfoPath Forms Services in SharePoint Online will reach end of support in July 2026 [MC616550] 4 pexels pixabay 227692](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)
- (Updated) SharePoint Designer 2013 reaches end of support on July 14, 2026 [MC1230891]
![(Updated) SharePoint Designer 2013 reaches end of support on July 14, 2026 [MC1230891] 5 pexels deuspix 2234006](data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjwvc3ZnPg==)


![(Updated) Microsoft Purview | Data lifecycle Management cmdlet connectivity change [MC1213770] 3 pexels cottonbro 5473955](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-cottonbro-5473955-150x150.webp)
![(Updated) InfoPath 2013 client and InfoPath Forms Services in SharePoint Online will reach end of support in July 2026 [MC616550] 4 pexels pixabay 227692](https://mwpro.co.uk/wp-content/uploads/2024/08/pexels-pixabay-227692-150x150.webp)
![(Updated) SharePoint Designer 2013 reaches end of support on July 14, 2026 [MC1230891] 5 pexels deuspix 2234006](https://mwpro.co.uk/wp-content/uploads/2025/06/pexels-deuspix-2234006-150x150.webp)