We noticed that an “Offers and announcements” message is appearing in our chatbot, even though we did not add this in our automation. Most of our customers are receiving it, and we do not want users to see information that is not part of our chatbot flow.
At the moment, we are not sure where this message is coming from or how to disable it. Has anyone else experienced this issue recently, or does anyone know what might be causing it and how to turn it off? It has been happening in our chatbot over the past few days.
Best answer by cata_rendon
Hi @Pan Dev , ok I now understand better what is your challange. To be honest it aslo has happendend to me before. Probably what you can try to do, is to create and publish a new flow (you can copy and paste most info from the past flow so you wont spend to much time doing the new one) and see if the bug is gone.
Hi @Pan Dev Most likely this message is not coming from ManyChat. The "Offers and announcements" message migth be a native Meta/Facebook feature that can appear automatically in Messenger when your Facebook Page has promotional messaging options enabled.
To disable it, check the following in Meta Business Suite:
Go to your Facebook Page Settings → Messaging
Look for any Offers or Recurring Notifications settings that may be active
Also check Meta Business Suite → Inbox → Automations — Meta has its own native automation layer that can send these independently of ManyChat
This is related to another issue. Most of the users see it like that. Even though we build the flow with "Get updates" but users see with "Get Offer" and text with Don't want to miss out on the latest sales? You can stop these messages at any time.
Is there any specific reason do you know, why this happens?
Hi @Pan Dev , ok I now understand better what is your challange. To be honest it aslo has happendend to me before. Probably what you can try to do, is to create and publish a new flow (you can copy and paste most info from the past flow so you wont spend to much time doing the new one) and see if the bug is gone.
