Default Reply Trigger for Unrecognized Input

REQUEST_SUMMARY_V2 Problem - -> Current System: Currently, there may not be a specific trigger for sending a default automated reply when the bot receives input that doesn't match any predefined keywords which results in the flow stopping temporarily. -> Suggested Feature: Implement a 'Default Reply Trigger' that activates when a user's input is not recognized or doesn't match any existing keywords. This default reply could include buttons, quick replies, or even initiate a longer flow to guide the user back on track, enhancing the overall user experience and ensuring continuous engagement. Submitted by House of Chikankari. Expected behavior - Allow this condition/action directly in workflow builder - Support testing with real sample events before publishing - Provide clear logs for why a workflow did or did not run Business impact - Reduces manual operational effort for teams - Improves consistency and customer experience - Helps teams move faster with fewer support escalations Legacy category: New Feature