@GwenGwen
The issue I find, is the low scalability of the system using it the way you comment.
I'm not sure if for some clear niche this (time of not mass automatizing some tasks/success rate) could be somehow profitable, but instead of increasing my total number of account management I've been decreasing it (not replacing when banned for example) on purpose because each day I feel I cannot manage it and the results are not into my expectations
Probably as you mention mass dming the same thing could result in ban but I feel it will be better to manage like 5 or 6 projects of 40 accs each (200 accs in total), mass dming different dm each project, that only handling 10-20 accs in total with different dm each acc. for the same total amount of time invested (due to the lack of batch automation process). Maybe you can get 2-3 accs banned in each project each week, but this mean 3x6~$20 at most, that is less than an hour work budget (and believe me, managing 200 accs for a week is far more time than 1 hour). Obviously with a tight budget and trying to do everything the most free as possible, this mechanism is not the best.
BTW, FYI I've been testing mass dming the exact same message in a single project with 20 accs with 0 bans. So maybe upscaling a little bit could be feasible but maybe FL does not give this option at last.
So believe me, I'm asking this because I'm 100% sure it could give much more profits managing it properly. I'm starting to think to build something self-made with Selenium or something, because I'm not sure to which extent FL has editable files to accomplish this.
