Re:The Costs of Running a Support Team in the Bay Area
by ethbro on Sunday November 06, 2016 @02:42AM
(#12884036)
Curious what product field was for your experience?
In my experience, support issues tended to involve legacy application technology and/or environment issues (usually antivirus given the nature of our product). Support for anything non-trivial involved WinDbg dumps or SQL dives in cooperation with development.
Did your support experience include working the issue back through development for a hotfix and retest until resolution?
My attitude at the time was to provide the support that would expect as a customer. This means that I understood the customer's problem, understood the product, and made an effort to solve the customer's problem. If the customer encountered a defect, I was honest about the defect and explained how to work around the problem.
I completely defend my statement, that, as an engineer, the problems that I solve are much more complicated then when I had to fill in while we were between support staff.
A support person's role is being an expert in the product supported; and clear communication. That is much easier than implementing a product where there are competing interests; and one customer may expect the product to behave in a way that contradicts what another customer expects; and contradicts what's in the business's best interests.
Furthermore, there is no formal eduction required for being a member of support staff; nor is there a requirement for the kind of accomplishment of skills. The appropriate analogy is nurse to doctor.