So, Soundcloud is asking as part of a community manager position to sum up some personal thoughts on customer service and community building. Here they are:
1) Wait a moment before interfering. Even if someone is complaining, it is hugely more satisfying to most people if s/he can figure out his/her own problems by him/herself. Barring that, it is equally appealing, if not more so, to work with a community at large to figure out the problem. It is one of those behaviors that seem to increase loyalty over time. As wonderful as this sounds, if after a day or two there are only more complaints and no solutions, one should jump in and help.
2)Comp the hard core members on semi-irregular occasions. They represent the majority of your income, and tend to notice shoddy service because they use your service the most. Delay that in advance and also get them involved in the occasional community building through their comped service(s).
3) Don’t interfere with unexpected user behavior and unexpected requests (eg: like this: http://bit.ly/f0My0r – there are multiple versions of this request) The reason is as follows: You can’t tell users what to do or not do with your product, and allowing them to play around and then tell you about features that they need/want will guide you to a better customer/product fit. With that in mind- DO ask questions on a regular basis to your customers to get you to a point where you understand their logic behind the product, as well as where these sorts of requests come from.)
4) ABN – Always be nice. It is your reputation on the line, and being nice never hurts it.
5) Don’t try to have everyone love you – it almost never works. Some people are not going to be a fit, accept it and move on.
Hmm, that is really it.




Or What You Shouldn’t Do To a Theme
As some people may or may not know, I’ve been trying to create a new WordPress theme for this blog. I’m using the same base theme ad before (Thematic), and I thought it would be worth it to mention a major mistake I made.
I wanted to make a HTML5 compliant theme so that the blog would age gracefully. I found out that the way thematic works there is a file called “Extensions” which contains a number of files that are the basis of most of the basic functions that are called in the theme framework. I figured that I could just change one function to echo the right doctype, and delete the other function that creates extra material for head. This broke the theme. Apparently there is a hack for your functions.php folder for your child theme – but I don’t think it as cool as editing the original theme to make sense in HTML5 in the first place.
My other big issue as of the moment is that editing in Chrome is a pain in the a**. I’m getting the following message:
This StackOverflow post seems to have a hint. One problem – I don’t understand it.
Other problem – I am not running a multisite. So umm help in the comments please? (yes I am port: 80 in case you need to know this, I switched it from port: 8888 I believe, so umm why is this happening.)