The folks at SWSoft say that their server automation software is in use by over 10,000 web hosting providers in 100+ countries (and their market penetration is nearly 100% in this industry). Together, these companies are home to tens of millions of websites. Over the past 10+ years, their users have created an enormous variety of collaboration and knowledge management tools. Sadly, surprisingly few of these ideas have been adopted by the web hosting firms who played a silent by instrumental role in their development.
Let me give you an example. While I was VP of Communications at EV1Servers, a customer complained that his support ticket was poorly handled. He asked about configuring software RAID on a Red Hat Enterprise server; the technician closed the ticket with a brief note that the issue was beyond the scope of support under his service plan. If he wanted more information, he could search on EV1Servers' FAQ or customer forum.
After performing a quick search, I found that neither the FAQ nor the customer forum contained any reference to software RAID. I found some relevant documentation on Red Hat's website and forwarded it to the customer. Since he didn't feel confident about performing the work himself, I later referred him to another customer who offers sysadmin consulting.
Over the following few weeks I received 4 or 5 other software RAID inquiries. I was able to cut and paste the info I previously collected, but the knowledge that I took time to obtain had no way of propagating across the company's other staff. And the relevant information was not distributed to other customers who might need it. There could have been dozens of other software RAID-related support requests, but I had no means of looking them up.
I suppose I could have created an FAQ entry. If every employee got in the habit of doing so, EV1 might have ended up with a knowledgebase that's as complete as what GoDaddy has. But even there, the customer is unnecessarily presented with an either-or choice. Would he like to search the Help Center or open a support ticket and wait? I know that there is available technology to implement a more efficient tech support process. It would work like so:
1. A customer logs into his hosting provider's support portal and submits his question (for instance, "how to configure software RAID on RHE4?") The system automatically queries the knowledgebase for possible matches.
2. The customer can end the session by indicating that the search results gave him what he's looking for. In this case, perhaps the hosting provider could offer him some small incentive (hosting credit? chance to win prizes?) to update relevant knowledgebase entries with any additional information he might have.
3. On the other hand, if the customer is not satisfied with the search results, his question automatically enters a support queue, where it awaits human response. When support reps receive tickets, they are prompted to complete knowledgebase entries in addition to answering the customers' questions.
4. It'd be cool to offer customers the option of bypassing the queue for a fee. The hosting provider could offer paid fast-track responses in-house - or create a Amazon-like marketplace in which third party consultants vie for the customer's business. Each consultant's listing might show pricing, customer satisfaction ratings, as well as whether he or she is currently online. If engaged by a customer, the consultant would pay the hosting provider a commission.
Earlier this year EV1Server's trouble ticket system logged its 1 millionth support request. A live human manually responded to each of these tickets. If each incident took 10 minutes to resolve, that's 166,666 man hours the company has had to pay for. Wouldn't it have made sense to redeploy some of the millions this has cost on a backend solution that could turn tech support into a profit center?