Live data from Hacker News

Everyone should read support emails

medium.com

11–20 of 214 posts

Re: Everyone should read support emails

#11
post #6

I once joined our support team to talk with one of our clients (I'd written a new bit of functionality and they wanted me there in case they would ask technical questions). It was one of the most eye-opening experiences ever. Our client talk about their clients abusing our software in ways that we as a development team had never even thought about. EDIT: On the other hand, I don't think it should be done to create a…

Could you elaborate on the kinds of abuse you saw?

> Could you elaborate on the kinds of abuse you saw?

In a very broad sense, sure. I don't want this account to be traceable to where I work now, so some details will be changed or omitted while keeping the kind of abuse the same.

We make a website where our clients can make timeslots available to the general public. The length of a timeslot is dependent on how many people the person booking slot intends to bring, as well as some other factors. Whether a person can book at a certain time therefore (partially) depends on how many people they tell our clients they'll bring.

We also made it so that the booker can change how many people will be coming along (for example because of sickness), or, if they are delayed, by how much, so our clients can more fully use all of their available resources.

However, how bookers were often using it, is by saying they'd come alone (if you have a very short timeslot, there's a better chance it's still available), and then change the number of people to how many were actually coming along. Or they'd just book a slot at the start of the day, and then delay it until they were placed on the time they actually intended to come. In both of these cases, they were abusing features which were genuinely needed for the product to work to their own advantage. It was slightly naive of us as developers not to take this sort of behaviour into account.

Re: Everyone should read support emails

#12
Support engineer here. For anyone considering a career in support:

- It's harder than development. Green fields are easier.

- It's pretty much a thankless job.

- You are sort of the janitors of the IT world. Not much respect.

+ The money can be pretty good. Because of the above, management usually rewards good support engineers.

+ You are welcomed by those who don't want to do support.

+ You stay fresh, learning other people's ideas all the time. This contributes to longevity.

All things considered, it's been a good career move for me. YMMV.

Re: Everyone should read support emails

#13

That would require developers to think of users as people instead of cattle, and then they might have to accept that the decisions they made because "developer time is worth more than user time" have an actual real-world cost on actual real-world people.

In my experience, such time pressure comes from management, not the developers themselves. This is evidenced by the painstaking effort a dev will go to to make their ultimate experience on a side project.

In other words, users are often sidelined by new feature requests (for other users) rather than a selfish conservation of time by developers.

The priority game is as yet unsolved, unless you can point me to contrary evidence (which I would be eternally grateful for).

Re: Everyone should read support emails

#14

Fully agreed. I'll go a bit further: Everyone, especially engineers and PMs , should once in a while actually reply to support emails. As CTO of my previous company, I still found time for large amounts of customer support, and so did one of my cofounders. It's definitely important IMO for key people to be in contact with the userbase. Get a better look at what people are asking for, feel more directly responsible fo…

Even if they do not reply, they should read every support email that comes in for the product/feature they worked/are working on. It is the best way to put themselves in the shoes of the user, and make better software.

I know someone will respond that they don't have time read all of the support emails, but my response would be that getting so many support emails is itself a data point.

Re: Everyone should read support emails

#15
I built my whole company around this idea. For years, I was the front line support - IMO, its the best thing you can do to improve not only your product but your approach to life. That and having kids.

Re: Everyone should read support emails

#16
By all means make e.g. Zendesk tickets available on a Slack channel, so people can dip their toes in and see how things are looking.

Don't spam everyone with every support email. You need a ticketing system at least to coordinate work, and prioritization and assignment to get workflow. Don't spam everyone with new tickets in the ticketing system either.

Having a rota of developers who either work directly with support, or on diagnosing and addressing issues that have come from support, is also a good idea I think. Problem areas will filter through from this.

Having all developers always interruptible by support will just slow things down. Interruptions from support often blow away half a day or more worth of development time, from context switching, checking out specific branches etc.

Re: Everyone should read support emails

#17

I once joined our support team to talk with one of our clients (I'd written a new bit of functionality and they wanted me there in case they would ask technical questions). It was one of the most eye-opening experiences ever. Our client talk about their clients abusing our software in ways that we as a development team had never even thought about. EDIT: On the other hand, I don't think it should be done to create a…

We do retail / light industrial automation stuff.

Every so often (rarely but say once a year or so), we bring some members of dev team along on an install. Its always very very eye-opening for developers to see what 'problems' look like in the field.

Further, something devs miss about installs is the lack of infrastructure you have to deal with (on a new build-out for example). So saying 'Just download latest version X and install on each of the clients' will take 5x longer than it does in comfy office environment since it means: (a) Go to hotel or tether phone and download 1GB file over 3G, (b) Put on USB stick, (c) go to each client, disable all USB restrictions and install new software, re-enable all restrictions (d) do all this while power is being turned off / on because electricians are still working.

Re: Everyone should read support emails

#18
post #2

"We can't give devs access to support, because [ZenDesk, FreshDesk, etc] costs 9 gazillion dollars per user"

Then it is a product development priority to pick something else, just as you wouldn't pick a bug tracker, version control system, or language runtime that wasn't affordable to let every developer use.

Re: Everyone should read support emails

#20

That would require developers to think of users as people instead of cattle, and then they might have to accept that the decisions they made because "developer time is worth more than user time" have an actual real-world cost on actual real-world people.

In my experience, such time pressure comes from management, not the developers themselves. This is evidenced by the painstaking effort a dev will go to to make their ultimate experience on a side project. In other words, users are often sidelined by new feature requests (for other users) rather than a selfish conservation of time by developers. The priority game is as yet unsolved, unless you can point me to contrary…

> In my experience, such time pressure comes from management

In my experience, open source developers are just as bad, if not worse, when it comes to their treatment of users.

Post reply on HN