Use this action to make your process repeat a series of actions until it meets certain criteria before it goes on to the next action in your design. With this action, the caller determines when the loop continues. Looping continues until the flow no longer receives an affirmative reply from the caller, which indicates that no further action is necessary. You can create flow logic with this action in several ways, including:

  • Loop through items in a collection 

    Loop through items in a collection applies to the actions inside the loop to each item of a collection of variables. For example, the actions inside the loop might add 2 and then multiply by 3. If you looped through a collection of five integers, then the loop would add 2 to the first integer, multiply the sum by 3, and put the product back into the first integer's slot in the collection. The loop would do the same actions on the second integer, then the third, fourth, and fifth. When it finished with the last item in the collection, the loop would "exit" and your process would move forward to the next action in your process design.

  • Loop until a fixed count is reached 

    Loop until a fixed count is reached applies the actions inside the loop for a number of times that you specify. For example, if you specify 10, then the loop will run 10 times before moving forward to the next action in your process design.

  • Loop while a condition is true 

    Loop while a condition is true applies the actions inside the loop as long as a certain condition is true, such as an integer value being greater than zero. You use the Expression Editor dialog box to construct the condition.

Note: There are two ways to loop while a condition is true. First, you can check the condition before going through the loop. If you check before going through the loop, then if the condition is false, the process will not go through the loop. Second, you can check the condition after going through the loop. In this case, the process will still go through the loop even if the condition is already false. The “extreme case” occurs when the condition is never true. If the process checks the condition before running the loop, then the loop will never execute. If the process checks the condition after running the loop, then even if the condition is always false, the loop will always execute at least once. By default, the process checks the condition before executing the loop.
Name Description
Name Add a descriptive label for the action.
Current Index Data Name Use to track the current loop count, starting at 0 for the first loop and then by increments by 1 each time.
Question

Here, ask recipients what they would like to do. For example, “Can I help you with anything else?”
Invalid Response:
No Input

For a no input invalid response, add a phrase to play back to the recipient. For example, “Say yes if you want to proceed, or say no if you do not want to proceed.”

Note: The bot returns the configuration you define in Settings > User Input > No Input Detected > No Input Apology combined with the Question communication.
Customize No Input

Enables the No Input Reprompts field and enables you to create a list of no input prompts that the bot incrementally returns after it receives no user input.
No Input Reprompts

After the bot receives No Input, it returns the communication at the position in the No Input Reprompts collection that corresponds to the current number of No Inputs received for that action. For example, the first No Input triggers the bot to use the first No Input reprompt in the defined collection.

The length of the No Input Reprompt collection also overrides the maximum number of No Input retries that you define in Settings > User Input > No Input Detected > Maximum Number of No Input Retries for that particular action. For example, if you define two reprompts in the collection, the bot retries twice. An empty collection turns off No Match retries.

Note: The bot returns the configuration you set in Settings > User Input > No Match Detected > No Match Apology combined with the No Match communication.
Default No Input

Enables the No Input field and allows you to define a single No Input prompt that the bot returns after it receives no input.
No Match

The communication that the bot returns when the user’s input is not a valid match.

Note: The bot returns the configuration you set in Settings > User Input > No Match Detected > No Match Apology combined with the No Match communication.
Customize No Match

Enables the No Match Reprompts field and allows you to create a list of no match prompts. The bot returns these prompts incrementally after it receives No Match input events.
No Match Reprompts

When the bot receives a No Match input, it returns the communication at the position in the No Match Reprompts collection that corresponds to the current number of No Match inputs received for that action. For example, the first No Match input triggers the bot to use the first No Match reprompt in the defined collection.

The length of the No Match Reprompt collection also overrides the maximum number of No Match retries that you define in Settings > User Input > No Match Detected > Maximum Number of No Match Retries for that particular action. For example, if you define two reprompts in the collection, the bot retries twice. An empty collection turns off No Match retries.

Note: The bot returns the configuration you set in Settings > User Input > No Match Detected > No Match Apology combined with the No Match communication.
Default No Match

Enables the default No Match field and allows you to define a single No Match prompt that the bot returns after it receives No Match input events.