There are several cases in which you might want to embed one flow within another flow. For example, if you're creating a troubleshooting flow for a complex product it might be easier to maintain several different flows for troubleshooting each of the product's major components and then embed them all into a master troubleshooting flow. Or perhaps you might create a standardized escalation process you'd like to reuse across several different flows.
This can be accomplished by using flow components. A flow (or part of a flow) can be turned into a component which can then be inserted into other flows as desired. They're also easy to maintain - updates made to the component's underlying flow are immediately reflected in any other flows that embed it as a component, meaning you can easily update multiple flows at once.
Note that while checkflows can only contain checkflow components, flowcharts can contain both flowchart components and checkflow components. This means that you can build flowcharts which direct users to a variety of flow components for different purposes. For example, you can build a flowchart which embeds both a flowchart component containing FAQs and a checkflow component containing troubleshooting and which directs the user to whichever one they say they need.
When the user enters a flow component, they will start at the component's entry point. For flowchart components, that is the START step; for checkflow components, the entry point depends on how the flow is structured.
For the mechanics of working with components in the assistant builder, see Create and embed flow components.