Skip to main content

This is a first. I will run through my set up and then the "error".

 

At 5:30pm, Sunday through Saturday an scenario in Make.com will trigger to gather the information of appointment data (Acuity Scheduling) of the next day and send an appointment reminder to either confirm, re-schedule or cancel their appointment. Every patient in Acuity must have their own phone number in order to send the reminder through WhatsApp. I first look for the contact in Manychat with the phone number as a custom field. If the contact doesn't exists, it is created. After that, I update some of the contact's custom fields that contain the appointment data and finally I send the message using the "Send Flow" module of Manychat in Make.com.

This has been working good for over a month now. Yesterday the workflow ran as usual with no errors.

This is one of the situations in which the "error" occured.

I get notified that some patients didn't receive the reminder and here's the kicker: in the chat with the contact the data is updated but the message wasn't sent.

Here's the same contact but with no message sent.

I've tried looking for any error messages in the log or email and nothing appears.

And I also got everything in check:

  • I have enough funds on the Manychat Wallet
  • Phone number is correct and complete
  • WhatsApp subscriber was created correctly as any other previously
  • I'm using a paid message template for every time a message is sent.

I can't find or think of a possible root to his problem. Any help is appreciated

​@DCCAMPOS it looks like you’re doing everything right from what you mention…

Do this, in the flow you’re triggering, add a tag as the first step. This way you can check if the API call is working.

If you see the tag in the Live chat, then the problem is with messaging.

Talk to support to see if they see any errors on the backend.

If you don’t see the tag, then the sendFlow is failing for some reason.

Hope this helps!

​@DCCAMPOS Can you share a screenshot of the flow you’re sending?

​@DCCAMPOS it looks like you’re doing everything right from what you mention…

Do this, in the flow you’re triggering, add a tag as the first step. This way you can check if the API call is working.

If you see the tag in the Live chat, then the problem is with messaging.

Talk to support to see if they see any errors on the backend.

If you don’t see the tag, then the sendFlow is failing for some reason.

Hope this helps!

Thanks Gustavo, will try this for today's messages.

​@DCCAMPOS Can you share a screenshot of the flow you’re sending?

This flow is for the case I used as an example.
With this one I also had to cases in which the custom fields were updated but the message wasn't sent.

For context, I initially was going to use those Manychat triggers so that's why there are 3 but all deactivated. 

​@DCCAMPOS perfect. Your setup look ok.

Try the tag before the message, this will help you debug and determine that the flow actually triggers (and the issue is with the message per say)

Reply


Community Terms & ConditionsCookie settings