Skip to main content

Something strange is happening with our ManyChat automations. We have two flows: "Current WhatsApp" and "Not Current WhatsApp."

In the image I’m sharing, users are supposed to be entering the "Current" flow, but the options they're being shown belong to the "Not Current" one.

However, as you can see in the image, the CTR data appears under the 'Current' flow, and not in the 'Not Current' one.

My suspicion is that the initial trigger is somehow redirecting users from the first step into the 'Not Current' flow, though that still wouldn’t fully explain the CTR numbers.

We’re still quite new to ManyChat, and the base setup was actually built by an external developer, so we’re now trying to understand and audit what they did. 

Any idea what might be causing this?
 

Note: “Whatsappp copy” was the previous name of  “current whatsapp”.

Thanks in advance

 

Hi, ​@CLICC_manyC!

 

Best approach would be getting in contact with the external developer to understand the logic behind it (like, what in the heavens is coming from the connections at the left of the triggers 😅). But I don't know what happened between you and them… maybe it's not a possibility.

 

From the screenshots we can see that the "Not Current WhatsApp" flow has just a disabled “Ad Trigger”. This also means that absolutely nothing will trigger this flow.

 

Now, for the "Current WhatsApp" flow, there's a default reply trigger and it will probably trigger for every new message sent to that number. And the other flows that appear on the triggers, you have to look if there's any active trigger that also could start the flow and land on that one.

 

Again, without taking a look on the whole logic (flows, triggers, conditions...), it's hard to give any tip or direction that could solve the issue you're having. 

 

Anyway, hope it helps somehow. 🙌

Hi, ​@CLICC_manyC!

 

Best approach would be getting in contact with the external developer to understand the logic behind it (like, what in the heavens is coming from the connections at the left of the triggers 😅). But I don't know what happened between you and them… maybe it's not a possibility.

 

From the screenshots we can see that the "Not Current WhatsApp" flow has just a disabled “Ad Trigger”. This also means that absolutely nothing will trigger this flow.

 

Now, for the "Current WhatsApp" flow, there's a default reply trigger and it will probably trigger for every new message sent to that number. And the other flows that appear on the triggers, you have to look if there's any active trigger that also could start the flow and land on that one.

 

Again, without taking a look on the whole logic (flows, triggers, conditions...), it's hard to give any tip or direction that could solve the issue you're having. 

 

Anyway, hope it helps somehow. 🙌

The thing is that “Current Whatsapp”  is not what our custemer seen, but the “not current” one. We check it ourselves. But just because it does not have a relevant trigger do not understand how they end up there. Despite what the CTR shows, people aren’t seeing "Current Whatsapp":/. Yeah, may be we should look at the entire automatization.

Make some tests “playing” with the triggers… disable one by one a test to see what happens. 

You will have to poke around to discover what does what. 😅

Make some tests “playing” with the triggers… disable one by one a test to see what happens. 

You will have to poke around to discover what does what. 😅

Yeah… seems like our only choice. Thank you for the help! 

Reply


Community Terms & ConditionsCookie settings