Multi-layered Persistent Menu and the composer_input_disabled attribute are essential aspects of a Messenger Bot from now on. They’re the new normal. The new UX standard going forward for many bots. And you don’t have NLP baked-in, so there seems to be no reason why you wouldn’t drop everything and adopt this ASAP.
Are we going to get the ability to do this on our Flowxo bots before the public roll-out on March 20th?
I hope so but it doesn’t look like it…
It’d be amazing to bring something like Make Custom Request to Persistent Menu settings, so that we can use hierarchies and localizations without you having to add them to the GUI.
It’d be a shame if our bots don’t have this when every other bot will from the 20th.
Not having any idea when this is coming out is hurting us. Our clients want these features and soon they’re going to be at a disadvantage for not having them.
Need more specific communication from the team on the issue of keeping the platform up to date with the host platforms. Specially with regards to the recent Messenger update.
I hope this isn’t left unanswered.
Please give us a date. An interval at least.
I know you have a lot going on and are working on analytics but this is bigger than analytics in my opinion. At least we can build analytics into our flows with your integrations, recording interactions with Sheets or MySQL and then analyzing those tables. We can’t do anything about the UX.
Thanks for understanding.
