### Answer Components (sub-flows) in Conversation Flow are designed for organizational and maintainability benefits, not performance improvements [(1) ]() [(2) ]() . The main purposes of Components are: [(1) ]() - **Reuse**: Build once and drop into many agents and flows - **Consistency**: Keep behavior uniform across use cases (e.g., identity check) - **Clean canvas**: Hide detailed logic inside a focused sub-flow - **Faster iteration**: Update a shared Component to improve every agent that uses it Example use cases include: [(2) ]() - Security checks before proceeding with billing/support - Language-specific sub-flows that transfer to the right language component - End-of-call surveys Components help you build reusable sub-flows to keep agents maintainable and consistent [(1) ]() . They package parts of your conversation into mini flows (groups of nodes) that you can reuse across agents and flows . Regarding performance/speed: Components are not designed to increase agent performance or speed. In fact, there have been community reports of latency issues with Conversation Flow orchestration [(3) ]() . If you use Flex Mode for more than 20 nodes, performance might degrade and the agent might have higher hallucination risk [(4) ]() .

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

​ To learn more, see the sources I considered: [[1] Components](https://docs.retellai.com/build/conversation-flow/components) [[2] CF Components, Warm Transfer Caller ID, Call History & More.](https://www.retellai.com/changelog/cf-components-warm-transfer-caller-id-call-history-more) [[3] Conversation Flow has added latency between nodes.](https://community.retellai.com/t/conversation-flow-has-added-latency-between-nodes/777) [[4] Flex Mode](https://docs.retellai.com/build/conversation-flow/flex-mode) ​