<em>This is in <strong>no<\/strong> way a rant. I\/We love our customers to death and pride ourselves in taking great care of them. ++extra mile<\/em>\r\n\r\nWith any SaaS type of business, your users will need support. They'll have questions about your service, or issues that come up when something breaks or does not function as expected. Sometimes the issue is related to your product or code, like a software bug - and sometimes the issue is user error. And one could argue that a case of user error is actually a defect in your product in that for some reason something was unclear or not obvious. <em> Example: You cant blame the user if that setting config menu item was 4 clicks deep and then required that something in another menu 2 screens over was activated first for your buried menu to even function.<\/em>\r\n\r\nI'm sure there are libraries of studies and reports on how to make your support system efficient and limit time per call and incidents per account. I have not read any of them.\r\n\r\nBut I have learned this: providing support costs money. Not providing support costs money. Providing half-assed support costs money. And providing great support - or even better - eliminating the need for support, costs <em>less<\/em> money and can even make you money.\r\n<h3>Lets explore:<\/h3>\r\nThere is one rather large internet company I know of that treats support as a sales channel. Grandma calls support for issue x, and gets sold z, q, and p upgrades that really don't help grandma. Support staff there appear to act as semi-trained sales staff that are incentivized with bonuses and perks to keep call time to a minimum, and up-sells to a maximum. On the surface looks like a win for megacorp. Not so much for grandma.\r\n\r\nFlipside...\r\n\r\nThere is another company I know of that also sees support as a sales channel, but does so from the place of <strong>a happy customer is a repeat customer that recommends new customers<\/strong>. They don't up-sell you (unless it is most appropriate, like a limit ceiling you have reached on your account) and then of course just mention it as possible option. The owner once told me his support system is his largest source of new\/repeat customers. Seems like a win for the company, and a win for the user.\r\n<h3>Support still costs money<\/h3>\r\nIndeed it does. Take a low dollar hosting outfit customer at $4.95\/mo... that is a ~$60\/yr. gross income account. Whittle that down after cost of providing said service and then figure each customer may have 3 support incidents a year. Figure a support incident may include some email exchanges, a live chat, maybe even a phone call. Pay the light bill and the support teams' salary.. etc. A heavy support user would burn away all profit for their account in no time. Sales volume makes up for it but you get the idea.\r\n<h3>How I see it<\/h3>\r\nSo I think like the company in our second example: provide stellar support and reap the rewards of referrals and repeat business. I also proactively look for ways to improve the product to minimize support and find ways to automate support tasks. Our WhiteScreen eliminator is a good example of this automation. I noticed support volume on the same issue, so we built a self-service system to handle it. Even better would be to prevent the issues all together... something I trust the WordPress Core team is working on feverishly.\r\n\r\nI would like to think of our support as a long-tail profit center, where in time, we will reduce overall support requests relative to customer volume by improving the system, but also by going the extra mile for our customers and keeping the up-sells to a minimum, we will yield more repeat customers and referrals over the duration. Check out our <a href="https:\/\/pagely.com\/support\/">WordPress hosting support page<\/a> for more detail on how we roll.\r\n<h3>Conclusion<\/h3>\r\nSupport is part of any business. Do it well and prosper, or don't - and piss off your customers & tank your brand.