2 ms·
When I worked in an internal team at a bank, we chose to make a bot to replace the FAQ when the number of daily tickets where the response that could be summed
by orwin 3y ago
When I worked in an internal team at a bank, we chose to make a bot to replace the FAQ when the number of daily tickets where the response that could be summed up as 'rtfm' hit 30.
It might have been frustrating for the users, but at least we avoided basic questions and our tickets at least we're filled correctly.
I hacked a bypass for the secops who worked a lot with us and at least knew how to fill tickets.
- nottorp 3y agoYeah, the problem is your management then removed any option to talk to a human and left the chatbot do all support.
- deepspace 3y agoYes, and since everybody did that, everyone managed to sour their entire user base on the idea of chatbots.
- aoweijrti 3y agoI've done tech support and I can sympathize, but good god I still hate you for not telling me how to use the bypass.
- orwin 3y agoTo be honest it was a hack i did in a day instead of doing my real job because it was less boring, a week after the chat bot was online, I was not really on the support side (i automate stuff). I probably gave the bypass to 6 persons, documented it but i'm pretty sure no one on my team really knew it was there because i left a month later (and also, only one person from the original team was still there. The real issue (it's also a response to the comment with management and no human interaction) was that our onboarding was shit. Not only our tools for our clients, but also our internal onboarding (i did work on that too in even if it wasn't my job, because i lost weeks in useless processes, to avoid new hires the same pain). Make a tutorial for your tools. Two even. A long-winded one, and one with only the commandlines , executables and scripts.
- navane 3y agoI believe one would be the tutorial, the other would be called a how-to.