"Thanks again, outstanding service and professionalism."


Carl Baker
Bakerfinancial.co.uk

Need help?

Sales | Support | Tech

Archive for October 7th, 2008

2008 Oct 7

I’m sure we have all been on this topic, where you need help and a forums seems the best place to ask. Here are some tips to make sure you get a good response.

  • Check your spelling - The amount of times I’ve read a post on a forums and the poster has abbreviated/misspelled so many words that I just think “screw this guy, he clearly does not care” is insane.
  • Check you make sense - It could just be the forums I visit, it I seems to read lots of posts in which the poster has written a load a nonsense which I cannot be bothered to read.
  • Use examples (and if possible include them in your post) - Again, another little pet hate of mine. I don’t want to have to guess the problem with your website. I want to see the code your using and find the bug (and not have to leave the page). If possible use relevant forums tags (For example, if your posting PHP, use the [php] tag supplied).
    On a sub note to this, if their is a PHP error, include it in your post and point out the line where the problem is. Just saying “I’m getting some problem, here is my code” will most likely result in a verbal backlash (from someone like me).
  • Search! - Make sure you have search the forums with a fine tooth comb before you post (and make an idiot out of yourself). If a similar problem has been asked and fixed then your just wasting peoples time.
    On another sub note, make sure you have read the manual. If something has been well documented their is likely to be a solution hanging about.
  • Be thankful - Just saying “thank you for your help” at the end of a post goes a long way. Need I say more?
  • Be Helpful - If you do find the answer else where, be helpful, make sure you go back and explain how you solved the problem, this is helpful to the users who tried to help you and also helps to improve the forum as when people search for that problem they can then find your solution.
  • Keep it clean - No one wants to have to read though a load of unnecessary text, keep to the point but still make sure you explain yourself. Also don’t put lots of unnecessary adjustments to the font.
  • (Finally) Be pactient - Don’t expect a response less then 5 minutes, just wait about for a few hours. What I normally do is I take a break from looking at the PC then take a look at the code with a fresh head (normally I find the problem).