Hi SleekFlow Team, We would like to raise an issue and request clarification regarding the “Wait for Message Reply” function in SleekFlow Flow Builder. Currently, in the flow logic, there is an action called “Wait for message reply”. Based on the setup, it allows us to define: Event name: Message received Timeout if no reply after a specific duration Filter based on customer reply, for example. If message content contains “Hibah” However, we were informed that this function still needs to be connected with Condition Branching for it to work properly. From our understanding, this does not seem fully aligned with the purpose of the Wait for Message Reply action, because the action itself already has a Filter section where we can set the expected customer response. Current Issue When using Wait for Message Reply, the system should ideally wait for a customer reply that matches the filter condition before continuing the flow. For example: Customer receives a message asking them to choose or reply with “Hibah” The flow uses Wait for Message Reply Filter is set as: Message content Contains Hibah Expected behavior: The flow should continue only when the customer reply matches the filter. However, currently we were advised that we still need to add Condition Branching after this step, which makes the flow more complicated and less intuitive. Expected Behavior the Wait for Message Reply action should be able to function independently for simple response handling. For example, If the customer reply matches the filter condition, the flow should continue to the next step automatically. If the customer does not reply within the timeout period, the flow should move to the timeout path or next defined action. Suggested Improvement We suggest improving the Wait for Message Reply action so that it can include more complete settings directly inside the action itself, without requiring additional Condition Branching for basic use cases. Suggested additions: Matched reply path Continue the flow only when the customer reply matches the filter. No reply / timeout path Allow us to define what happens if the customer does not reply within the selected time. Invalid reply path If the customer replies but does not match the expected keyword or condition, allow us to send a fallback message. Multiple accepted values Allow multiple keywords or replies such as: Hibah Wasiat Pusaka Appointment Case-insensitive matching For example, “hibah”, “Hibah”, and “HIBAH” should be treated as the same response. Save customer reply into variable / contact field / custom object This would be useful for reporting, follow-up, and automation. Clear routing based on reply result The action should have built-in paths such as: Reply matched No reply Invalid reply Reason for Request For non-technical users, using both Wait for Message Reply and Condition Branching for a simple reply-based flow makes the automation unnecessarily complex. Since the Wait for Message Reply action already has a filter setting, it would be more logical and user-friendly if the action itself can handle the response logic directly. This would make the flow builder easier to use, especially for common WhatsApp automation such as: customer service selection appointment booking hibah / wasiat consultation flow document submission follow-up e-voucher redemption lead qualification Please advise whether this is a current limitation, a bug, or an upcoming enhancement. We would appreciate your recommendation on the best setup for this use case. Screenshots are attached for your reference. Thank you.
