Genesys Cloud common module flows enable reusable logic across multiple flow types, reducing code replication and development time by allowing developers to build logic once and apply it across different flow contexts such as call flows and chat flows. Common modules accept input and output data, interact with calls, and share actions and data types across compatible flows, though flow-specific actions cannot be transferred between different flow types. When multiple flow types are selected for compatibility, the system restricts available actions and data types to those shared by all selected types, with lower size limits than other flow types. Common modules support configuration of settings, input/output variables, expressions, and task and state editor actions to enable routing conversations, prompting users, and integrating systems for building complex customer journeys and omnichannel experiences. Architect snapshots common modules into consuming flows, meaning changes to a common module require republishing the consuming flow to incorporate updates. The system uses the most recent version of a common module unless an older version is explicitly retained by publishing the consuming flow before creating a new version, with dependency tracking providing visibility of common module versions across the platform. Key constraints include: common modules cannot be deleted if referenced in published flows, common modules cannot be nested within other common modules, text-to-speech settings derive from the consuming flow rather than the common module, and common modules have reduced size limits compared to other flow types. Access to common module configuration and management through the Architect interface requires appropriate permissions assigned by organization administrators based on job functions. Genesys Cloud provides comprehensive documentation on flow design, dependency searches, best practices, and troubleshooting resources to support effective implementation and management of common module flows.