This is the kind of thing that happens when dealing with Backblaze. It's constant misrepresentation on the public side of things. Their twitter account people twist things around and misrepresent things and their employees come into discussions like this and defend the company by claiming I said things I didn't say.
Once we realized what was going on we told the social folks to try and defer to the support folks. It's hard to have a long conversation on twitter as well, it's not a great medium for full-on support, but it's great for sending links to FAQs and stuff like that.
I do honestly think that the conversations you had with our team on multiple fronts were misinterpreted on both sides which led to a lot of confusion. We've also gotten better at making sure that the social team asks our support folks for guidance if they see a tweet or post that they are not familiar with.
1) Answering basic general questions like "how much does it cost"?
2) Debugging live customer issues. For example, if crappy anti-virus quarantines one of the Backblaze executables, what the heck is happening and why? Of if a customer's client cannot contact Backblaze's datacenter, which firewall is blocking it (maybe it is the software firewall on the computer, or maybe it is the router not allowing HTTPS through)? Etc....
In the process of debugging problems, the customer service reps are dealing with a truly insane array of possible issues and symptoms and they go back and forth with the customer asking for log files, ask if specific symptoms are happening, and in general COLLABORATE with the customer to get to the true bottom of the issue. Nobody lied. These are good, honest people that are really looking out for our customers and take their responsibilities seriously.