Hi, ​@gerarcat!

This is the logic to build what you're looking for:

1. Your message with buttons.
2. For each button, you set an Action adding a Tag (TEST_TAG in my example - it can be the same for all the buttons). this will be the identifier to check if the contact has clicked any button.
3. Connect your next messages for each option and continue your flow.
4. As next step for the message with buttons block, connect a Smart Delay and set the amout of time you wish to wait to check if the contact has selected any option.
5. Now set a Condition checking if the Tag isn't the tag you created for the buttons. And for the true connection (green one), connect the message and rest of the flow you wish to send if the contact doesn't click an option.

In short words, this will wait some time and check if the contact has a specific tag. If he has it, it will mean that a button was clicked and no “alternative” flow will continue. If he hasn't clicked an option, the alternative will be send. 

IMPORTANT: the example above works if the contact makes the first interaction (sends a message or clicks a button earlier in the flow), opening a message window.

If you send it via broadcast and this is the first thing that is sent, the “delay route” must be adjusted to use another message template in order to be delivered.

Hope this helps!

hey man!! you make it look so simple!  thnks a lot!