3 ms·
I agree with you, but there's a lot going on here: - Customer support is expensive. If keeping customers happy and lowering churn is important, you spend a lot
by echelon 5y ago
I agree with you, but there's a lot going on here:
- Customer support is expensive. If keeping customers happy and lowering churn is important, you spend a lot of money on it.
- If you can't afford enough staff, the next best option is to put up a few barriers to slow down the incoming requests. Maybe automated means can solve a large percentage of problems.
- Not everyone knows how to search or navigate a tree. Think about the non-tech folks. You have to offer them something different. It's hard to strike a balance.
- Chat bots are being hyped and sold by new tech companies trying to build larger scale solutions. They want to build more, but they need to sell, grow cash flow, etc.
Etc.
- fivre 5y agoI'd challenge the idea that customer support is _expensive_. Generic customer support requires no specialized expertise: you need knowledge your company's business processes, tooling related to third parties they worked with (redirecting a courier's shipment via the courier or whatever), and general customer service skills, and that's about it. _Specialized_ customer support, e.g. support for complicated software, is expensive, because it requires technical domain knowledge equivalent to or above many engineering employees, and employees that can perform it effectively could probably move to engineering and increase their salaries twofold because compensation isn't tied to expertise, it's tied to what the market will pay, and you can more easily get away with shit support than shit engineering, but ignore that--it's not the majority of customer support. Customer support _is_, in the simplest view, a cost center. Customers contact support when something has gone wrong that they can't resolve otherwise. If nothing goes wrong, you don't need it. If you, as support management, can reduce the time it takes to resolve things that go wrong (by any means) and reduce the number of staff needed to handle cases, you win: your department doesn't directly generate revenue, so your goal is to reduce expenses. Tying lost revenue to customers lost after poor support experiences is difficult and noisy: there are plenty of customers who have poor experiences because they're incompetent and wouldn't succeed with any amount of support, and because of this are more likely to request support, and the high-level categorization used to describe issues often obscures what actually went wrong (a generic "Account > Creation" category isn't going to capture issues like "users can't create an account if their address includes non-ASCII characters", but execs don't see anything more than the category). These issues (and others) combine to promote an environment where support is more a buffer to getting support with limited ability to fix issues, and a perverse incentive to _not_ fix issues since metrics are focused towards reducing time to resolution (easy to measure) versus quality of resolution (hard to measure!). Poor support is furthermore easy to ignore because you can either often focus more on new business first and foremost (hello, every startup ever!) or rest comfortably on a monopoly position where customers can't drop you even if you provide terrible support (hello, the US ISP market!). Cost is not strictly an disincentive to providing sufficient, capable, and effective support, but it's difficult to recognize the value it provides and there are more immediate cost savings from reducing support cost than long-term revenue from customer retention by providing good support. This compounds into even poorer service in more specialized environments because talented people will leave, because working in a cost center sucks. The flipside of support is essentially sales engineering, AKA support while trying to court a customer. The technical skills needed aren't any different, but one brings in revenue in an easily quantifiable way, so it gets more political clout and more organizational investment.
- harha 5y agoNon tech folks come up quite often: I disagree with that, chatbots often require talking to them in a precise language to find an answer or reply in a strange way if they don’t have an answer, I think that’s even worse for a non tech savvy user. Also: what level of non tech savvy are we taking about? Test with some real users of different ages, I’m sure there’s something to be found that improves usability to a point that’s better than a bot. Agree on the cost cutting though, if you don’t care about an individual user go ahead and waste their time. I’ve actually had enough encounters with the human counterpart of a chat bot that was equally unhelpful in resolving simple issues.
- diegof79 5y agoYes, the cost of having real agents is the main reason for chat bots to exist. The bot is like a buffer: you can deflect simple issues; capture information for the agent; show feedback about the wait time and agent availability. Badly implemented bot AI is not the only issue. To give a good CX, companies need to invest in giving the agents the right tools. It’s extremely frustrating when the canned responses fail and there isn’t anybody to answer or when you have to repeat all the info (because the agent cannot see your chat with the bot).
- _jal 5y ago> Customer support is expensive. Yep, and that's a key thing to get right. One challenge for those promoting robots is that they are unpleasant to deal with and suck at their purpose (from the customer's perspective - they're deflecting traffic, so they're working for the business). Worse, everyone knows they suck, and people with a choice choose not to use them. I know I've dropped one vendor who forced me to. (I'm sorry, life's too short to talk to robots.) Things like this make the customer very aware of how they are valued - as cattle not pets, to steal a metaphor.