3.0 Flow Control - Now we move on to the functions.
      Back to home
      1. Knowledge Base
      2. Flow Builder
      3. 3.0 Flow Control - Now we move on to the functions.

      3.0 Flow Control - Now we move on to the functions.

      3.0 Flow Control - Now we move on to the functions.

      In this section, we’ll explore another type of command — also commonly used — especially when you want to collect more specific information from the customer, control timing between messages, and more.

       

      3.1 Wait for User Reply

      This command is used when you’ve previously asked the customer for some input, such as:

      “Please tell me your name,” “Company name,” “Date,” etc.

      • If the user responds, you should connect the green dot to the next step you want to follow.

      • If the user does not respond within the time you set (hours, minutes, seconds), the flow will continue from the red dot and follow whatever step you’ve connected there.

      The most common actions when there is no response are:
      Archive conversation, End flow, or reconnect this step to the previous question so the bot asks again (usually with a counter in between — we’ll explain how that works later).

       

      3.2 Wait for file upload

      • Specify which file types are supported, and define a fallback path for unsupported file types. (Converting files to Base64 format is also supported.)"

       

      3.3 Variable Flow

      • This action allows you to create a branch based on variables, with an “else” option for cases where the variable does not match.de.

       

       

      3.4 Wait

      • This step is very simple — it’s used when you want to add a delay between one message and the next.
        You can choose the duration in seconds, minutes, or hours.

       

      3.5 Variable Branch

      • This action allows you to create a branch based on a variable, with two possible outcomes: one for a match and one for a non-match.

       

      3.6 Keyword Branch

      • This step consists of entering a specific keyword that the customer must type in order to proceed in the flow.

      • This option can also be used as a bot trigger at the beginning of the flow.
        (It’s especially useful when you want to activate the bot internally for testing purposes.)
        For example, if you set the keyword to "Saysimple", only people who know the keyword will trigger the bot.

       
       

      3.7 Opening Hours

      This option allows you to set working hours for interaction between the flow and the customer.

      You can add specific days and adjust the time range as needed.

      • If the customer sends a message within the configured time frame, the green connector will continue to the next step.

      • If the customer messages outside of the configured hours, the red connector will continue to the next step.

       

       

      3.7 Counter

      This step is very important, as it works similarly to a limiter.

      The Counter should be used whenever you want to return to a previous step or jump from one step to another.

      In the following example, we use a Counter with a limit of 1, which works as follows:

      • If the customer doesn’t respond within 5 minutes, the flow continues from the red connector to the counter input.
        The counter checks whether this is the first time the customer hasn’t replied within 5 minutes. If true, it follows the green connector, which leads to a message like:

      “Please answer the question to continue.”

      From there, it reconnects to the original question: “Hi, how are you?”

      • If the customer still doesn’t respond after another 5 minutes, the counter detects that this is the second time, so it follows the red connector, leading to End Flow.

       

       

       

      3.8 End Flow

      • This step is used solely to end the flow between the bot and the customer.
        (The customer will not be assigned to an agent, and the conversation will not be archived.)