Plunks Posted February 10, 2013 Posted February 10, 2013 I have recently started my first IT helpdesk role and I have noticed that there is no sort of documentation or database for faults/trouble shooting which more often than not requires putting the customer on hold, hunting down someone from software engineering or sys eng to get an answer for the fault that is occurring I was wondering if anyone has suggestions on a program or a good way of localizing all this information for easy access whilst dealing with customers? Seems to be that finding the answer slows down not just me, but everyone in the support team. The management team at work seem to be fairly open to suggestions on changing processes and anything that speeds up customer support I think would be welcomed. Thanks in advance Quote
Infiltrator Posted February 10, 2013 Posted February 10, 2013 (edited) If your company has a Webserver with PHP extensions, you can use this PHP web-based application, to keep track of incidents and problems logged by the clients. http://osticket.com/ Edited February 10, 2013 by Infiltrator Quote
digip Posted February 10, 2013 Posted February 10, 2013 We used to use incident response tickets kept in a binder by month, but also stored them on a network share for the Helpdesk users, in directories by topic if needed. My suggestion is build a basic form, or excel sheet of questions user had, fixes, and then index them in a share all helpdesk users have access to. It was way harder to search for them from the binders other than when someone said, remember last month when such and such happened, we could pull the incident response ticket from the book to prove we fixed it, etc, fax a copy over to them, if a user says it was never fixed or whatever the case may be, paper trails plus digital copies for all in the department to share and use help greatly though. One of the guys went as far as building something similar to what infiltrator said, which was a searchable webpage on the intranet lan that users could use to help troubleshoot dumb shit, like, is the printer powered on, check for toner in fax machine, etc. Quote
Inertia Posted March 3, 2013 Posted March 3, 2013 We just built a pretty simple lookup database in Access. Nothing hard just a search box and a table. For bigger stuff, microsoft has some troubleshooting 101 type guides that might help you out. Quote
infinitedaemon Posted March 4, 2013 Posted March 4, 2013 In episode S04E02 they talk about spiceworks @ http://www.spiceworks.com. It looks pretty robust. I've never used it. Request tracker is free and I know of a few people that use it. At my company we use Dell's KBox. It does asset inventory, ticketing and patching but it's a bit pricey so if you're looking for something free I would look into the first two. Quote
wh1t3 and n3rdy Posted March 4, 2013 Posted March 4, 2013 Spiceworks does a reasonable job of a ticketing system. Their inventory scanner leaves a lot to be desired by their own admission with many false positives etc but the ticketing system is good for a free product. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.