Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> The call queue for that company never dropped below a constant 200-300 on hold and emails took days to even get to.

If those are the stats and you're still not actually solving many customers' problems; if tons of people are being hung out to dry with no recourse, then you're doing a bad job. If you don't have enough people to do the job, then hire more people. If you can't afford to hire more people, then don't do the job, or limit the number of customers you deal with.



The problem with customer service is that quite often the problem is larger than a single person can fix. It requires other people both within the company and outside of the company to fix an issue.

There is also the scenario in which there is no solution and you need to balance the cost of investigating to the point where you're 100% certain there isn't a solution and efficiently deciding there isn't one.

One thing I have learnt working at these companies is that some customers think the world revolves around then and that technology should work flawlessly all the time, when it doesn't.


A bad company devides available work in so many different departments and job titles the actually people with authority that is able to execute is by design very thin spread. This company could also pay higher salaries, give better training and enable more call agent autonomy because that is what is takes to deliver a frictionless delightful customer service.

That's why every mom and pop store outranks every Fortune 500 on customer service expect Amazon. Most still haven't learned to put customers central to their business but treat it as an after thought.


Putting the customer at the center of their business is a very flamboyant term that many companies say they do but appear to perhaps not do.

I like to use Telecommunication companies as an example because I worked in one heavily and dealt with these exact scenarios.

If a customer calls the service desk because their internet is broken due to vandalism at their exchange. I as a customer service agent cannot drive to the exchange and simply fix the problem myself. It requires appropriate prioritisation of all of the other problems within the network that need fixing that may also be affecting other customers, as well as requiring outside resources to rebuild that location. To add that the customer might also have a mobile SIM as a backup within the modem but is not able to achieve the speeds nor latency needs commensurate with their fixed service. And that's if you're lucky to be the wholesaler if you aren't, then your organisation literally cannot fix the problem legally because you don't have the authority to repair infrastructure that you don't own outright.

I appreciate that this a specific example, but one I have dealt with mutltiple times. Once a business grows to a greater size, it is inherently more difficult to fix problems like a mom and pop store whether or not you care the same about your customers or not. It may appear as though they don't care, but there are simply different realities at different scales.

My point being that if you assume as the beginning that they purposely distribute available work and responsibilities in such a way that to execute is difficult by design then that's not what we're talking about here. What we're talking about is where you are operating at such a scale that it is very difficult to provide great customer service even if you do care.


> One thing I have learnt working at these companies is that some customers think the world revolves around then and that technology should work flawlessly all the time, when it doesn't.

I worked alliance support for a major database vendor in a former life. My experience is that enterprise customers are usually realists. They run a very complicated environment and are aware that things, especially software, is not perfect. They expect good service (and pay through the nose for it) and can be demanding. But ultimately they're realists.

The ones that think the world revolves around them and their issue must be fixed RIGHT NOW! are usually the ones that bought some ODBC driver for 40 bucks 12 years ago, which don't really have any support entitlement to begin with.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: