Ask HN: Where do you draw the line in supporting your customers?
According to some of our customers, we break their production systems when we make what we define to be non-breaking changes. Some changes include:
- Replacing SSL certs after Heartbleed. Apparently some of our customers hard-coded the certs in their Java apps (?) and they lost connectivity.
- Rotating cloud servers. We do this regularly without downtime, but some customers hard-code IP addresses instead of using DNS. We have enterprise options available for those with firewall restrictions or who need static IPs, yet customers who can't connect to the old IPs are upset with us.
- Changing our JSON library without changing the API contract. Our old one was lenient with integer/string types, but the docs were clear about types and had examples. But when we switched JSON libraries to one that's strict, it broke a bunch of customers who relied on requests that were not correct.
These problems are preventable just by using DNS, not hard-coding certs, and following the docs. Too much to ask?
We also get lots of requests for help with implementing our API into customers' systems to the point where they share their screen, give us control, and ask us to make it work. Why are we doing that kind of help for free? Aren't there liabilities? Don't businesses charge thousands of dollars for that kind of support/freelance programming work?
We're torn. Our customer support wants to help the customers and answer their questions. They don't feel satisfied just sending them to our documentation or Stack Overflow. From the dev perspective, some customer questions are simply a matter of them not knowing how to code. We want to help, but it derails our progress on other, more important domain things.
Is it possible to do too much for customers, and where do you draw that line? Do other API providers have this issue?
12 comments
[ 2.8 ms ] story [ 35.5 ms ] thread1/ Set a strict line in the support provided: I'm happy to give a hand as long as it is mail support and whenever I have the time to reply. No direct interaction with the user code whatsoever. Otherwise we agree on a number of hours I would spend on this and they would be charged for it.
2/ Use the liberated time to set up a knowledge base: Currently I've set up a wiki, a FAQ and I'm giving free courses (101 + good practices). I try to keep everything up-to-date by adding the questions/answers I get to it.
It was not easy especially at first (convince someone non tech-savvy that their model was at fault when the error logs displays 1 error coming from the model and 80 coming from MPI processes was quite hard) but now in about 80% of the requests you could see they've started looking for stuff by themselves before contacting me. Which is really pleasant!
In your particular case I would involve the customer support in the documentation writing (at least a FAQ) so that they actually see how painful and time consuming it is to write those things. On the dev side, the technical documentation should have some good practices nuggets here and there, for example in the part where you explain server cnnection by showing the actual command line to use you could add a comment like "#connection using hostname to keep it IP independent". Which might lead a couple of newbies and junior dev to the right path. On API level ideally it should enforce good practices by enforcing more strict rules (connection only possible using hostname f.e.).
But as soon as you actually touch the system or machine of the client you should at least be legally covered. And given the set of skills involved and how the time spent here won't be available somewhere else they also should be charged for it.
I do look forward to our team coming to an agreement about precisely what we support and how we handle customer requests or complaints that are outside our scope. I imagine it'll look something like what you've described, at least in part.
We already have our support team helping with FAQ and articles about our product, so now it's just a matter of defining our scope more precisely and coaxing our customers to take care of their own internal systems.
The POS that we integrate with makes changes all the time. Sometimes, these affect our product & we have to fix them. It not a single circumstance have we ever asked them to fix the errors, nor would we.
I would stop doing any maintenance work for your customers immediately. I don't know if the examples you mentioned are just edge-cases, but to help them, you can just communicate what you have changed, why etc, so at least they are aware before their issues begin.
For SSL certs, this is a common practice and frequently needs to be coordinated between close integration partners so that nothing breaks.
If you can provide clients with ample warning about any upcoming changes, and preferably provide them with a staging/dev instance they can test their code against, it might help avoid similar problems in future.
In my experience, clients get frustrated when their business-critical processes suddenly break with no warning and they have to engage in fire-fighting. From their perspective, they had something working one day, then you "made a change" and "all their stuff broke". That might not be a fair assessment, and it might well be due to shoddy practices on their end, but the end result is the same: the client is frustrated and has a bad experience of using your product.
What kind of communication channels have you guys seen or used for that kind of scenario? A separate Twitter feed? A blog? Sending an email to all customer every time the SSL certificate changes in any way?
As a rule of thumb: I'd say if one customer makes those kind of complaints, it doesn't necessarily mean anything... but if two customers have the same exact problem then you should look into changing how you present your guidelines/docs to the users. They might need to be modified to make the warnings more aggressive and apparent. If you've done everything you can in that area, then all you can do is equip your customer-facing-teammembers with all the firepower they need to handle those kind of complaints themselves.
Yes, many companies have large lines of business just providing support. At the end of the day it's all about the value it provides your company and your clients. If you're able to retain and attract users/clients then some free support could be worth it as a sign of cooperation and goodwill. If they're already paying customers you may need to better define what's covered by your SLA and various support agreements. However, if they are asking for advanced help outside of those agreements then you can just say you don't provide additional support. Or if your company has the resources you can always charge them for engineer support (for example, MS charges $259/h for advanced support during business hours).
Also, make it harder to use improperly. Can you block direct calls to the IP address? Etc.