We use Twitter mostly to broadcast brief updates to our members about downtime and announcements. In general, if there's an outage or a system problem, even a relatively small one, and we're able to post any information we can about it to Twitter, we will. However, it is not one of our methods of member support. While Twitter does have some value to some people, we feel it is particularly ill-suited for working together with our members to find and solve problems.
So, if you send an @nfsn Tweet, keep in mind:
- We don't have any PR people or a "social media team." There's no one here who's job it is to look at (or post on) Twitter, so we may not even see a tweet for several days.
- Even if we see your Tweet, we're unlikely to have the information at hand needed to answer.
- We probably won't know who you are anyway.
- Even if you tell us who you are, we can't take someone's word for it over Twitter.
- The answer almost never fits in the length of a tweet. (And most people can testify that trying to force things to fit can consume a ridiculous amount of time.)
- There are usually serious Privacy Policy concerns. (If you tweet us asking why your site is down, would you really want us to tweet to the world that you ran out of money? Because that doesn't sound too good to us.)
- Answering the few questions we could answer would just mislead people who haven't read this into asking questions that we can't answer and then frustrate them when we don't.
As with all forms of feedback, we value what you have to say, and a real person will (probably, eventually) read everything Tweeted to @nfsn. So feel free to use it to say what's on your mind, as long as you understand we won't answer.
Should you want a reply, we recommend using one of the member support options that allows us to provide one, or just post on our forum.