Today I decided to write an article on the Cost of Technical Support. I'm writing this as a bonus chapter for "the book" only because of issues I have had today dealing with a customer.
During your time owning and running your directory business you will invariably find the need for technical support. This isn't just referring to support for your script, but for your hosting as well. Especially for your hosting.
I had a customer who decided they wanted to host their site with me. My prices are fair and reasonable and my support is top tier. I happen to be knowledgeable about a lot of things, and since I've been doing hosting for more years than I can remember I know quite a bit about webhosting.
The customer in question is a non profit organization with a budget in the millions per year. They planned on moving their site to my server with an account that cost just over $200 per year.
Before the actual hosting began, it was found out that they have free hosting available from their internet provider who happens to be a telco (telephone company). The decision was made with my endorsement to use the telco as their host in order to save the one person IT department some money.
I was offered a fee to move the site for them, which I agreed to. The move began, usernames and password were sent and logins failed. Apparently a web interface must be used to create an FTP login for the telco host, so one was created.
I logged in and uploaded the required files (~80MB of files) and set about trying to view the site online before any DNS changes were made. This is where technical support became necessary.
Now in my past experiences when a tech calls another tech the call goes very smoothly and quickly. Not in this case.
I called the telco and after pushing buttons for the 40th time I was able to speak to someone. I told them I want to view the users site online before DNS changes are made to ensure that it works properly.
The response was silence.
My reaction was a creeping feeling of horror.
After five minutes of trying to explain to the tech what I wanted to do I convinced him to go ask someone else for help. The other tech that came on the line asked what I needed and I told him the same thing. I want to view the customers site online before DNS changes are made.
His response to me was to visit the IP address.
That doesn't work of course, and it was the first thing I tried before I called. I stated that I assume that it was a shared IP address so I needed to know what method they use for viewing sites with no DNS. In a *nix environment this is typically ipaddress/~username/
As soon as I mentioned linux the response was that neither tech knew anything about linux. A few minutes go by with some typing and it is determined that the customers site is on a virtual IP address that cannot be viewed without a domain name.
This is repeated a number of times in different ways. At this point I feel like the horror has enveloped me and I'm in the actual movie.
The call is ended and I inform the customer that their site is uploaded, the menu change they requested was made and that they cannot view their site until they update DNS and to hope and pray everything works when the site goes live.
This was not technical support that I called. This was more like someone to answer the phone just for the sake of answering the phone to make people feel better about spending money.
Yes, that's what this world is coming to. That's why tech support is being farmed off to the company and/or country with the cheapest labour regardless of ability, language barriers and knowledge.
When you as a business owner pick up the phone or send an email you should expect to get an answer to your question(s). I have dealt with many companies and I find the largest ones have some of the worst support I have ever seen.
Can this type of support cost you money? Absolutely! What happens in two days when the DNS updates for the customers site take effect and the site doesn't work. I guarenteed their site would work on my server. If it doesn't work on the telco's server they'll need to call me back and hire me to fix it. Their IT department guy is a good guy, but he deals with networks, not the internet or HTML.
So the cost to fix it may be minimal, but they will need their site up and running immediately. This means that I would need to pull myself off of another job that I'm doing and fix their site. This means a higher cost to them.
It would have simply been easier and cheaper for them to have me host their site in the long run. And a lot less stress as well.
Now think about this the next time you're looking for bargain basement hosting. Are you going to get the kind of support that you might need one day? Can you afford not to pay a few extra dollars a month to ensure that when you email or call support that they will have the answer and know exactly what to do?
Copyright 2008 Bruce Peresky - All Rights Reserved - No duplication permitted without written permission from the author


