Flows are our way of organizing the group of User Requests and App Responses that make up a specific user journey. Each Flow contains potential conversations between the user and the Voice Platform.
Parts of a Flow
There are two parts to consider when creating a Flow:
The name of a Flow should be roughly 1-3 words and describe what is happening at this specific step.
The description is used to detail what should be happening within the Flow, along with any notes that might be important for other members of your team.
In this Community Bank Project, "Account Balance", "Next Payment","Help", and "Exit" are all examples of Flows.
Flows, along with their names and descriptions, aren't a part of the actual voice experience, but are useful to add structure to your voice application and organize all of the speech that creates the user experience.
Still confused? Learn more about the project process here.