Ask HN: What's the best way to handle internal tech support?
3 by underyx | 3 comments on Hacker News.
My company has around 1000 CS reps and 200 engineers. The CS reps very often need to ask the engineers questions, report bugs heard about from customers, etc. Us engineers also get bug reports about the internal tools we've developed for CS. Currently, all this is handled via a simple Slack channel. This is actually great, since there's no bureaucratic cost to getting in touch, unlike with a proper ticketing system, and having actual public conversations is the fastest way to resolve issues. But of course, we started seeing inefficiencies in other aspects. The same questions keep being asked over and over again. There's an FAQ linked in the channel topic and it's automatically posted in the channel every 12 hours, but it's still not enough, we still get tons of questions that could be self-solved without engineers' intervention. So, that made me curious, how are other companies handling this? Could we somehow maybe auto-respond to Slack messages with the correct answer with some bot, or just come up with something that actually makes people check the FAQs before posting? Or is there some way better solution to replace all this?
Post Top Ad
Responsive Ads Here
Saturday, June 30, 2018
Home
Hacker News
New top story on Hacker News: Ask HN: What's the best way to handle internal tech support?
New top story on Hacker News: Ask HN: What's the best way to handle internal tech support?
Subscribe to:
Post Comments (Atom)
Tackling Trump’s Policy in the Americas, Rubio Would Confront New Tensions
By Edward Wong and Hamed Aleaziz from NYT U.S. https://ift.tt/EF9jn1u
Post Bottom Ad
Responsive Ads Here
Author Details
Templatesyard is a blogger resources site is a provider of high quality blogger template with premium looking layout and robust design. The main mission of templatesyard is to provide the best quality blogger templates which are professionally designed and perfectlly seo optimized to deliver best result for your blog.
No comments:
Post a Comment