Skip to main content
Question

Facebook DM to Comment success rate - Is ManyChat no longer fit for purpose on FB.

  • September 17, 2026
  • 4 comments
  • 61 views

em0132

Is ANYONE using Facebook comment to DM successfully?

Has ANYONE got an example where their Facebook automations are being opened and responded to?

Is ManyChat now REDUNDANT on Facebook and NOT FIT FOR PURPOSE?

My account is 6 months old and had strong engagement, but for first 4 months only had 1% delivery/open rate. After reading various forums on here and speaking to Meta agents, I disconnected ManyChat (MC) to rebuild trust in my account. 

I responded to comments manually for over 60 days (note physically impossible to respond to all) and reached a point where response rate was 45-50%. 

I reconnected MC this week, have limited the number of messages sent (using a niche trigger word) to prevent any “spam-like” behaviour. I set up 10 variations in comment responses, and 12 variations for the DM. These are sent with smart delays and include no buttons or links, just conversational.

Despite this, I am back to a 1% open rate. At the same time I have continued to manually send messages with a 45% open/response rate.

I am using the exact same comments and DM’s in my manual messages vs the automated, and 45% of people type a response to my manual messages. 

Per the “AI Help” on MC website, the message is not active till I get a response vs my manual DM’s are already active and I am therefore more likely to get a response. Please expand on this - how can I change this/does this mean that Manychat will always go to spam and therefore not seen? Is ManyChat redundant and not fit for purpose on Facebook despite being an approved partner?

 

4 replies

em0132
  • Author
  • Up-and-comer
  • September 17, 2026

Note in addition to this I have checked the handling of the message in Facebook/no other automations/ManyChat selected as on in all of the troubleshoot areas. Permissions have been refreshed etc. 


cata_rendon
Forum|alt.badge.img+5
  • Community Moderator
  • September 17, 2026

Hi ​@em0132 ,first message from a Page to someone who's never messaged you before almost always lands in Message Requests, sometimes Spam, not the main inbox. That's Meta-wide, not a ManyChat thing, every comment-to-DM tool hits it. So this alone doesn't mean ManyChat is redundant.

What I can't explain is why the gap is so much bigger for automated sends when you've controlled for content and volume. Worth checking first: in your manual 45% sample, how many already had an existing thread with your Page versus brand new people? Existing threads go straight to inbox no matter who sends them, that alone could explain most of it.

If that's not it, it's a backend classification question Support would need to check, not something visible from here.

Hope this helps 
Cata


em0132
  • Author
  • Up-and-comer
  • September 18, 2026

Hi Cata, 

 

Thanks for the response. 100% understand the messages should be going to requests, in the period I was not using ManyChat I got them to the standard request folder rather than spam. 

Since my last message I have tested the automation further. All messages are now going to spam (manual and MC), which has led to a decrease in response rate of manual messages to 30%.

The key difference seems to be that when I manually like and respond to a comment the person receives a notification (with my response telling them to check requests). Vs. when the MC automation responds to the comment, no notification is sent to the person.

I have tested a couple of times now with different profiles that have not previously interacted with the account. It applies even if I trigger the automation first, and then comment on a 2nd post and respond manually, there will be no notification for the MC comment, but there will be one for the manual. 

I hope that makes sense. 


cata_rendon
Forum|alt.badge.img+5
  • Community Moderator
  • September 18, 2026

Hi ​@em0132 that's a clean test, controlling for order and using fresh profiles takes the guesswork out. If manual gets a notification and automation doesn't, that's probably Meta blocking push notifications for API-sent messages, not something wrong with your setup. No notification means nobody checks spam or requests, that alone explains the gap.

Worth a support ticket with exactly this, and maybe post it in Known issues too if you keep seeing it.