TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I hope someone on the list can help me. That's a lie. I hope a bunch of
you on the list can help me.
In my position I am responsible for usability, documentation, and
training. In addtion, Tech Support reports to me. We are a growing
company and need to formalize our Tech Support protocols to cover
timeliness of response, internal documentation of the problem,
follow-up procedures, escalation of problem status, and anything else
that you may know is important to maintaining quality support.
Additioanlly, since I am responsible for usability, documentation, and
training, I need a way to make sure that tech support understands and
documents user questions so we can review them to see if they need to be
addressed in the documentation, the training, or the design of features
for the next release.
I have a sense of what constitutes good technical support. However, I'd
appreciate the wisdom of the group so I don't look over something
important.
Thanks,
Joan
--
Joan Melgaard
Director of Training
Mirror Worlds Technologies http://www.mirrorworlds.com
