The Artima Developer Community
Sponsored Link

Agile Buzz Forum
How not to run support

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
James Robertson

Posts: 29924
Nickname: jarober61
Registered: Jun, 2003

David Buck, Smalltalker at large
How not to run support Posted: Oct 3, 2007 9:41 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by James Robertson.
Original Post: How not to run support
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Latest Agile Buzz Posts
Latest Agile Buzz Posts by James Robertson
Latest Posts From Cincom Smalltalk Blog - Smalltalk with Rants

Advertisement

Chris Pirillo ran across an all too common problem in the IT sector - lousy support, with Comcast being the louse of the day. I can relate to his experience - I've had many, many encounters like this with Comcast:

My connection kept going up and down, but by the time I was able to speak with someone in the support department, everything was fine again.
“Well, sir, we’re not showing any problems with your connection right now.” Yes, it’s fine right now - but not when I try to open up more than one Internet app. I was even having issues with Vonage and Skype… “Well, sir, we can’t be responsible for programs that we do not officially supp…”
Whoa, whoa, whoa - WAIT A MINUTE! I interrupted him, loudly. I’ve been using Skype and Vonage and streaming live video and doing all sorts of wacky things across my home network and never had an issue I wasn’t expecting to experience. Vonage wasn’t the problem. Skype wasn’t the problem. My browser wasn’t the problem. The Netgear gateway router that Comcast gave me was the problem.

If I had to guess, the problem goes right back to the motivations of the support staff. They are probably rewarded based on how quickly they handle calls (or how many they handle in an interval of time, which amounts to the same thing). The rationale for such schemes is to save money - although, if you sit down and consider that for a few minutes, the rationale doesn't hold up well in an era where an arbitrary user can end up being an accidental PR nightmare.

In any event, the "get them off the phone quickly" theory holds up well in the face of experience with Comcast. If you have anything other than Windows connected to the Comcast provided router/cable modem, the phone tech will try the "we don't support that" dodge immediately. The fact that the client is irrelevant in most cases doesn't enter into it - it's a dodge to get rid of you.

I've said before that it's a bad idea to let lawyers become ad-hoc PR staff (lawsuits). It's even worse to let your support staff cause PR headaches due to poorly thought out compensation plans. Somewhere at Comcast central, a bean counter thinks his support plan is saving the company money. What he doesn't realize is that the PR staff down the hall wants to know who keeps hitting them with the ball peen hammer...

Technorati Tags:

Read: How not to run support

Topic: Industry Misinterpretations 55: Seaside on Opentalk Previous Topic   Next Topic Topic: CI Factory Beta 0.9.0.52

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use