If you could design a custom helpdesk ...
-
Features that aren't available in my current helpdesk that I would really like.
User updates via texting- Users can signup for a texting service that allows them to update tickets via SMS or MMS. They can also receive ticket updates this way
Attachments via MMS - I have users that don't know how to take screenshots on their PC. However, they can take a picture with their phone and send it. This would be also very useful for troubleshooting mobile devices
Ticket Grouping Suggestions - This is so simple, but I have yet to see it implemented. Wouldn't it be nice to see a list of similar tickets when viewing a ticket? Kind of like shopping at Amazon and you see similiar items to the one you are viewing. It would be nice to be able to link and re-categorize similar tickets on the fly as well.
-
Keep the ideas coming!
-
@thanksaj said:
My current helpdesk has a description field where all the troubleshooting notes go, but you can't tell when each not was added, or by whom.
Really? That's pretty damn bad. What are you using?
-
@IRJ said:
@thanksaj said:
My current helpdesk has a description field where all the troubleshooting notes go, but you can't tell when each not was added, or by whom.
Really? That's pretty damn bad. What are you using?
Our system is called Insight. Every technician despises it...it really flows more like a CRM than a ticketing system. That's probably what it really is.
-
@IRJ said:
Features that aren't available in my current helpdesk that I would really like.
User updates via texting- Users can signup for a texting service that allows them to update tickets via SMS or MMS. They can also receive ticket updates this way
Attachments via MMS - I have users that don't know how to take screenshots on their PC. However, they can take a picture with their phone and send it. This would be also very useful for troubleshooting mobile devices
Ticket Grouping Suggestions - This is so simple, but I have yet to see it implemented. Wouldn't it be nice to see a list of similar tickets when viewing a ticket? Kind of like shopping at Amazon and you see similiar items to the one you are viewing. It would be nice to be able to link and re-categorize similar tickets on the fly as well.
I like the trending tickets idea. Maybe an algorithm that looks at ticket content and titles and says "lots of users are having issues logging into AD" and gives dynamic suggestions that are both built-in and can be customized. A correlation engine of sorts... If 3 or more users are all unable to login to their PCs with AD, and the tickets are all opened within 2 hours of each other, it opens a ticket or sends an email suggestion/notification to have you check your DC. Something like that, or even custom rules like that, would be sweet!
-
Trending would be interesting and if it is just "these tags are hot now", that is easy. If it is a "what are people describing", that's not.
-
@scottalanmiller said:
Trending would be interesting and if it is just "these tags are hot now", that is easy. If it is a "what are people describing", that's not.
The problem is tagging is that you would need people to do the tagging, and users are lazy. They won't tag their tickets, especially if they are opened via an email. Now if you have a system that analyzes the ticket and assigns tags dynamically that way, that could work.
-
@thanksaj said:
The problem is tagging is that you would need people to do the tagging, and users are lazy. They won't tag their tickets, especially if they are opened via an email. Now if you have a system that analyzes the ticket and assigns tags dynamically that way, that could work.
Yeah, ticket AI is not really realistic. Especially as humans can rarely figure that out. Tagging is far less work than putting in a meaningful ticket.
-
@scottalanmiller said:
@thanksaj said:
The problem is tagging is that you would need people to do the tagging, and users are lazy. They won't tag their tickets, especially if they are opened via an email. Now if you have a system that analyzes the ticket and assigns tags dynamically that way, that could work.
Yeah, ticket AI is not really realistic. Especially as humans can rarely figure that out. Tagging is far less work than putting in a meaningful ticket.
My point is, you can't count on your users to put in meaningful tickets. You have to assume that, by default, your user will submit a "HEEEEELP!!!! The internet isn't loading!" as their ticket. You can try to train users and condition them all you want, but in the end, it's a futile dream...
-
@thanksaj said:
My point is, you can't count on your users to put in meaningful tickets. You have to assume that, by default, your user will submit a "HEEEEELP!!!! The internet isn't loading!" as their ticket. You can try to train users and condition them all you want, but in the end, it's a futile dream...
And my point is "garbage in, garbage out." The best AI ever, including real I (humans), can't derive a meaningful trend from bad tickets. If they aren't good tickets already, you can't get a trend.
-
@thanksaj said:
@scottalanmiller said:
@thanksaj said:
The problem is tagging is that you would need people to do the tagging, and users are lazy. They won't tag their tickets, especially if they are opened via an email. Now if you have a system that analyzes the ticket and assigns tags dynamically that way, that could work.
Yeah, ticket AI is not really realistic. Especially as humans can rarely figure that out. Tagging is far less work than putting in a meaningful ticket.
My point is, you can't count on your users to put in meaningful tickets. You have to assume that, by default, your user will submit a "HEEEEELP!!!! The internet isn't loading!" as their ticket. You can try to train users and condition them all you want, but in the end, it's a futile dream...
What might be more realistic is a template-based system. If they use a portal, they have fields to enter things like computer name, etc. If they submit by email, create a template they HAVE to use for the ticket to even be recognized. That's the only way I can think to generate some kind of order or standard for your tickets.
-
Templates help a lot with tickets. That's why most ticket systems make you use a ton of drop downs to fill out common fields and then just an extra text description field.
-
@scottalanmiller said:
@thanksaj said:
My point is, you can't count on your users to put in meaningful tickets. You have to assume that, by default, your user will submit a "HEEEEELP!!!! The internet isn't loading!" as their ticket. You can try to train users and condition them all you want, but in the end, it's a futile dream...
And my point is "garbage in, garbage out." The best AI ever, including real I (humans), can't derive a meaningful trend from bad tickets. If they aren't good tickets already, you can't get a trend.
I agree. It was a suggestion, but one that would not be utilized very much of the time due to how normal tickets look, unless you.. (see previous post)
-
@scottalanmiller said:
Templates help a lot with tickets. That's why most ticket systems make you use a ton of drop downs to fill out common fields and then just an extra text description field.
Yup. I think that's a great system honestly. You are guaranteeing certain info from your users and not making them guess what you need to at least get started. Generating a template for email submissions that can be parsed by a ticketing system would be awesome as well. Basically just an email version of the portal form.
-
We used to get alot of bad tickets, but having proper categories really curbs this. We force the user to choose different categories, but we can also change them quickly if they use the wrong category
-
@IRJ said:
We used to get alot of bad tickets, but having proper categories really curbs this. We force the user to choose different categories, but we can also change them quickly if they use the wrong category
Yeah, and having different forms for different categories also helps. So if someone can't get into their computer due to a password issue, if they select the "can't login" category, it gives them certain fields, whereas the "can't get online" category has other fields that are required.
-
I think two separate similar ticket threads would do the trick. One that is based off category and one that is based off category and user location in AD.
That way you can see a trending problem in the same location if users don't categorize it correctly.
-
@IRJ said:
I think two separate similar ticket threads would do the trick. One that is based off category and one that is based off category and user location in AD
Wait, what? What do you mean similar ticket threads? I'm guessing you don't mean threads on ML.
-
@thanksaj said:
@IRJ said:
I think two separate similar ticket threads would do the trick. One that is based off category and one that is based off category and user location in AD
Wait, what? What do you mean similar ticket threads? I'm guessing you don't mean threads on ML.
We are talking about HelpDesk here, right? I meant tickets not ticket threads
-
@IRJ said:
@thanksaj said:
@IRJ said:
I think two separate similar ticket threads would do the trick. One that is based off category and one that is based off category and user location in AD
Wait, what? What do you mean similar ticket threads? I'm guessing you don't mean threads on ML.
We are talking about HelpDesk here, right? I meant tickets not ticket threads
The possibilities for correlation and how to classify things is endless. User's OU in AD, their department, certain keywords, etc.
