Skip to main content
Question

ManyChat messages showing as blank or failing delivery in Facebook Messenger — anyone else experiencing this?

  • Oct 31, 2026 3:31 AM UTC
  • 0 comments
  • 4 views

youaresojen

I'm experiencing a serious, ongoing issue with ManyChat automations on Facebook, and I'm hoping someone here has encountered something similar or knows how to resolve it.

My automations are triggered when someone comments a keyword on my Facebook Reels. The problem is that a significant percentage of the automated messages aren't reaching recipients correctly.

Here's what I've discovered:

  • Some recipients see a completely blank message bubble, even though the full message (including text and buttons) appears correctly in my Facebook Messenger and Meta Business Suite.

  • Other recipients don't appear to receive anything at all.

  • The issue is intermittent. Some followers and non-followers receive everything correctly, while others don't.

  • Both messages in the automation are affected, not just the initial private reply.

  • One follow-up message showed 142 sent but only 38.7% delivered, despite being triggered when someone actively clicked the button in the first message.

  • Manual messages sent to affected recipients have been delivered successfully.

I've already reviewed the automations, refreshed permissions, and tested the messaging. I've also simplified and consolidated my automations, but I haven't yet established whether that improves delivery.

At one point, my overall successful message delivery rate was as low as 8%. This is affecting hundreds of messages and causing people who requested information to think I'm ignoring them.

I've updated my ManyChat support ticket and submitted a bug report to Facebook, but I still don't have an explanation or resolution.

Has anyone experienced this, particularly the blank message bubbles or failed delivery of follow-up messages after someone clicks a button?

I'd especially appreciate insight into whether this is a Meta Messenger API issue, an account-level restriction, or something else that could explain the inconsistent behavior.

Any troubleshooting suggestions or help getting this investigated by the appropriate technical team would be greatly appreciated!