We have an automation, when it ends, someone from the company using whats-app for business, will reply to the user with a free text, but doing so will show the welcome message again (the automation will re-start)?? so how we can prevent this? so the automation should start/resume only if the initiator user type a message? and not when we (our company) users reply to user input? this is possible? and how?
Thanks
Best answer by Fabio Gaulke
Hello,
This is a common situation, and the best way to prevent the automation from restarting when you reply manually is by using a control structure with Tags and Conditions.
The logic involves identifying who is already active in the automation or under manual care so that the trigger doesn't fire again unintentionally.
Here's the logic:
Create a specific Tag: Name it something like "Active Automation" or "In Conversation".
Add a Condition Filter: Right after the trigger of your automation, insert a Condition block.
Configure the logic:
In the condition, check if the user does have the "Active Automation" tag.
On the True path, do not connect anything. This ensures the automation stops for anyone who already has the tag.
On the False path, insert an Action block to add the "Active Automation" tag to the user.
Continue the flow: After the action block that adds the tag, connect the rest of your blocks as usual.
By doing this, when the user sends a manual message, the system will recognize that the user is already "marked," preventing the flow from restarting from the beginning. Just remember to remove this tag at the end of the flow (either through a specific button or a final action block) so the user can trigger automations again in the future.
Hope this helps!
+3Hello,
This is a common situation, and the best way to prevent the automation from restarting when you reply manually is by using a control structure with Tags and Conditions.
The logic involves identifying who is already active in the automation or under manual care so that the trigger doesn't fire again unintentionally.
Here's the logic:
Create a specific Tag: Name it something like "Active Automation" or "In Conversation".
Add a Condition Filter: Right after the trigger of your automation, insert a Condition block.
Configure the logic:
In the condition, check if the user does have the "Active Automation" tag.
On the True path, do not connect anything. This ensures the automation stops for anyone who already has the tag.
On the False path, insert an Action block to add the "Active Automation" tag to the user.
Continue the flow: After the action block that adds the tag, connect the rest of your blocks as usual.
By doing this, when the user sends a manual message, the system will recognize that the user is already "marked," preventing the flow from restarting from the beginning. Just remember to remove this tag at the end of the flow (either through a specific button or a final action block) so the user can trigger automations again in the future.
Hope this helps!
+3
Yes, but it pauses all automations, not only one. Using conditions + tags you can automatically control wich flows you wish to put on hold.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.