Yea, we addressed our twitter folks about this as well. They aren't in support so typically have no context for tweets they are seeing. They just respond in the

Yea, we addressed our twitter folks about this as well. They aren't in support so typically have no context for tweets they are seeing. They just respond in the best way they are able to. In this case I believe that the social team saw that you were having issues with a restore and with data not being there, so they assumed that it had something to do with our 30 day retention window, which is most commonly the case when users are experiencing issues with the dashboard not showing what they think is accurate (typically this is with an unplugged hard drive or something similar). 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.