Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
During a support call with Apnalaya, we encountered an issue in their "volunteer registration" flow with the keyword "volunteer" and the child flow "priority challenges." When selecting 'health' as the priority issue, the response for 'education' was being triggered instead. After investigating, we found that the default validation in the "wait for response" node was set to "has any of the words." This caused incorrect responses to be triggered when multiple words were involved. Changing the validation type to "has the phrase" fixed the issue, and the flow then worked as expected.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Update the default validation in the "wait for response" node to "has the phrase" instead of "has any of the words." This would help avoid miscommunication issues in the flows. If needed, NGOs can still manually change the validation to their preference.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
An alternative approach could be to keep the default validation as "has any of the words," but include clearer guidance or prompts advising NGOs to adjust the validation based on their flow’s requirements.
Additional context
Add any other context or screenshots about the feature request here.
A screenshot demonstrating the issue is attached.
Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] During a support call with Apnalaya, we encountered an issue in their "volunteer registration" flow with the keyword "volunteer" and the child flow "priority challenges." When selecting 'health' as the priority issue, the response for 'education' was being triggered instead. After investigating, we found that the default validation in the "wait for response" node was set to "has any of the words." This caused incorrect responses to be triggered when multiple words were involved. Changing the validation type to "has the phrase" fixed the issue, and the flow then worked as expected.
Describe the solution you'd like A clear and concise description of what you want to happen. Update the default validation in the "wait for response" node to "has the phrase" instead of "has any of the words." This would help avoid miscommunication issues in the flows. If needed, NGOs can still manually change the validation to their preference.
Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. An alternative approach could be to keep the default validation as "has any of the words," but include clearer guidance or prompts advising NGOs to adjust the validation based on their flow’s requirements.
Additional context Add any other context or screenshots about the feature request here. A screenshot demonstrating the issue is attached.