5 ms·
That's comical. I feel like I have an understanding of what's going on because I've been in this scenario on a contract - not with Google. I was told - "there
by Steeeve 9y ago
That's comical. I feel like I have an understanding of what's going on because I've been in this scenario on a contract - not with Google.
I was told - "there's a backlog of support requests. They are old requests that nobody has been working on and our offshore team can't handle. Being an expert in this particular product (and always in need of some extra cash), I said "OK, but let me be very clear that this is secondary to all other work that I'm doing."
Then they proceeded to hand over tickets. I wasn't allowed to communicate directly to customers, and communicating with their offshore staff was a challenge. "I need a log to even begin to troubleshoot this." followed by a frustrated customer reporting "I don't know why you're asking for this log, it won't help." OK, I have to be more clear with support, who I assumed would know. "I need this log. You create it by taking these steps." Another follow up from the customer with the same log again, reporting more frustration. Repeat this process 5 or 6 times, on 20 different tickets. I finally follow up along a different path. "Well, you see they see a request for logs and they only have one template to ask for logs. I'll get it straightened out." A month goes by. I'm getting requests for updates. I follow up on every path I have available. One customer was smart enough to get me the right logs, but they did not forward that log on. After much back and forth I ended up getting that one log. It pointed to a source code problem that I had no access to view, let alone edit. And of course, I have no contact to send this to.
What I ended up doing is submitting a bug report, the proper logs, and a summary of the logic problem in the source through one of my clients support account. Then I updated the tickets that looked to be related with "pending outcome of support ticket 1234. Months later, that particular problem was patched.
Hopefully the customers with their tickets stuck in "level 3 support" were eventually notified. I backed out of that project at some point because it just wasn't a good use of my time.
I understand the need to find a way to scale support. But if you are going to scale, monitor for effectiveness, plan for procedural changes, and do something to make sure the communications channels are working.
- mgkimsal 9y ago"scaling support" almost always seems hand in hand with "dumbing down for lowest common denominator". By the time things have made it through "please restart your computer"-level stuff, maybe the only way to scale is to put real engineers on problems and "allow" them to actually talk to the people having the problems. This approach seems to be the only one companies seem hell-bent on never trying.
- flukus 9y agoBecause engineers are expensive, engineers that can talk to customers are even more expensive and decent engineers willing to do support are even more expensive. That said, I do think software devs should be more involved with the customer for other reasons, far to often they are building software without having any idea what the customers workflow is.
- marcosdumay 9y agoWell, an entire support department that adds no value may indeed cost less, but losing your market because your product is defective (and you don't even know) can not be cheaper.
- mgkimsal 9y ago"expensive" can be relative. $100/hr but getting to the root of actual problems in, say, 2 days, and saving other customers from having the same issues in the future...
- shermozle 9y agoThe same reason forcing devs to do ops on their own product justifies having devs do (some of) their own customer support. Otherwise they just toss any old crap over the fence and it becomes somebody elses' problem. Force them to solve those problems and they magically go away, cos devs hate support.
- zamber 9y agoAt one project we had that pushed over to QA. We didn't have to touch it. Report a problem form sent an email to JIRA allowing us to scrape the influx of 400 daily reports for potential issues. It was pretty helpful in diagnosing a Samsung Android issue where our app was killed for no apparent reason (they have their own additional resource manager that scores apps and kills them UNLESS the app has a persistent notification).
- wastedhours 9y agoIf possible, teams should always "fix it twice" from support requests - get the customer sorted ASAP, and then determine if it's possible to solve the problem fully (either extra support documentation, patch, longer term feature etc...).