Skip to main content

Hello everyone!

I’m experiencing an issue when sending a follow-up message via ManyChat to a specific lead. Here’s the context:

I scheduled a commercial meeting with the lead, and immediately after the scheduling, my automation attempts to send the following message:

"Hi "Name],

Your portfolio analysis meeting is scheduled with icloser x] on December 16th at 4:30 PM (Brasilia time).

In order to proceed with the meeting, I need you to send me your current investment positions. If you need any help, feel free to reach out.

On the day of the meeting, I will contact you to confirm and send the access link.

Best regards! If you have any questions, just let me know!"

This lead opted-in for WhatsApp/Email/SMS, and the number is correct. However, when ManyChat tries to send the message using my Meta-certified number, I receive the following return message:

"Failed to send message to test number. Possible causes:

  • Contact has an experimental number (130472)
  • User's number is part of an experiment
  • Message not delivered by Meta (131049)
  • Meta chose not to deliver."

According to the documentation, the message might not have been delivered due to limitations or to maintain "ecosystem health." I’ve tried waiting before resending, checking the template, and confirming opt-in, but the error persists.

Has anyone experienced this issue or have any suggestions on how to resolve it? Any help is greatly appreciated!

Hey ​@juliodall 

To start, I’d try to run this with different numbers, to check if this is a widespread issue or if it’s isolated to a specific phone number.

If it’s widespread, next I’d try sending a simpler template with less content. Something very simple like ‘Your call is scheduled for December 16th’ and nothing more.

If this works, then the issue is likely in the content of the message you’re trying to send. I would guess that the words ‘portfolio’ and ‘investment’ could potentially trigger some of Meta’s content restrictions.

If the simpler message does not work, I’d try reconnecting the account and testing again. If all still fails, you’ll need to contact support to see if they have additional information on why it’s failing.

Hope this helps!

Reply


Community Terms & ConditionsCookie settings