You’re A Web Developer, Not Tech Support
I have a handful of posts on this site about tech support problems I’ve solved for clients. I write these posts because I usually have a hard time finding the solutions to the problems online and hope that maybe it’ll be easier for the next person who has trouble to find help. These posts are actually some of the most popular on the site and they receive a lot of visitors coming from search engines.
What’s that got to do with being a Web Developer?
It’s important to remember that just because you know how to build web sites does not mean you can or should fix any of your client’s computer problems. I promise you that the second you fix one of their problems with a printer, an email client or whatever they’ll be on you every time something goes wrong in their office. That’s fine if you’re charging them through some kind of service contract but never do this kind of work for free.
People who work for free get taken advantage of.
There’s definitely an urge to fix small problems for free or to go that extra step above and beyond what you originally agreed to with a client. I understand that and I’ve certainly done the same before but I know through experience that once you take on the two-headed role of Web Designer and Go-To Tech Support Guy your life will become miserable.
The only support requests you should ever handle are ones that are directly related to any of the programming or design work you’ve done for the client under your original contract. Extra support requests come at a huge price concerning your time. This is why I recommend against providing hosting solutions for clients as well.








The only required parameter for this to work is the one that contains the actual search query. The second parameter for the category is optional. You can also have Analytics strip the parameters from the URL in its reports, if you’d like, by marking the appropriate radio button.

