Hi Helder Gomes thank you for sharing the additional context.

Since you’ve already submitted this as a separate request, we’ll track updates there to keep everything consolidated. We appreciate your input and patience.

I would like to reinforce this request, as the absence of the “Ask a Question” feature for WhatsApp models has become even more relevant, both because of the user experience and the cost of the messages.

Currently, after sending a template with buttons, the workflow needs to perform subsequent checks to identify the response and then direct the contact to the correct branch. During this interval, it is common for the user to send additional text messages that do not match the responses expected by the workflow, which can lead to incorrect directions and a confusing experience.

As this behavior is frequent, several messages are often necessary before the user understands how they should interact with the flow. This also started to have a more important financial impact, considering the charge for WhatsApp messages.

In addition, without a native “Ask a Question” for WhatsApp templates, we need to add several extra steps to the workflows just to make simple flows, such as appointment confirmations, sufficiently reliable.

If the template submission could wait for the response, store it in a variable and offer a “no response” timeout/branch, in the same way as the “Ask a Question”, these problems would be practically eliminated.

Therefore, I believe that this functionality today is even more important than when I made the original request: it would allow simpler and more robust workflows, reduce unnecessary messages and, above all, provide a much better experience for contacts.