IT - if you have an issue with an application, give us step by step instructions on how we can repeat your issue like we are five years old. We’ll get it fixed more quickly that way.
I have great service with IT people because I do this by default. I’ll have already tried some steps myself, so I’ll give them info about what exactly works, doesn’t work, and things that I can or can’t do that might be related to the main issue.
I feel bad that my old job’s IT department would never trust me when I listed this amount of detail, so I stopped putting in the extra effort.
My ticket:
I am not able to login using the standard portal. The error I recieve is X. I have already tried rebooting. I have confirmed that everything was fully plugged in and that I am on the correct network. I also already went through the normal recovery process which did not work. Here is the result, [X].
The first response from IT:
Why don’t you try rebooting and then let me know if it’s working. If not, go through the normal recovery process.
Like, I get it, you’re being thorough and don’t want to just blindly trust the user, but I’m only talking to you because I already tried your quick fixes. Please understand.
As an IT director, I encourage my techs first action to be to connect to the clients machine and ask them to “show me what’s happening.” Then they aren’t to interrupt the user until they complete their explanation except to ask for clarification.
You can see all the steps leading up to the error, the users workflow, typically the desired end result, and the error message.
You also are building rapport with the user making them feel listened to. Far too often I see techs assume something else is the issue, “fix” that, call it done and the user gets frustrated.
Even if you can’t fix it, like so many user issues, at the very least the support experience is a positive one for the end users. Sometimes it’s just that a specific preference isn’t in an applications options or they need to change a step in their workflow. But at least the end users was listened to and their experience and frustration was validated.
If you have metrics or surveys, it’s always interesting to hear a user write in that the issue was not resolved, but they were extremely satisfied.
I’m doing that and generally the next step after that is : “OK, can you do it again and this time DO NOT CLOSE THE ERROR POPUP so we can get information on what is happening”
Also a restart really does fix a big chunk of problems. An app not working right? Force quit & reopen the app. Problem solved. Phone or computer bugging out? Reboot. Problem solved.
IT - if you have an issue with an application, give us step by step instructions on how we can repeat your issue like we are five years old. We’ll get it fixed more quickly that way.
I have great service with IT people because I do this by default. I’ll have already tried some steps myself, so I’ll give them info about what exactly works, doesn’t work, and things that I can or can’t do that might be related to the main issue.
They really appreciate the detail.
I feel bad that my old job’s IT department would never trust me when I listed this amount of detail, so I stopped putting in the extra effort.
My ticket: I am not able to login using the standard portal. The error I recieve is X. I have already tried rebooting. I have confirmed that everything was fully plugged in and that I am on the correct network. I also already went through the normal recovery process which did not work. Here is the result, [X].
The first response from IT: Why don’t you try rebooting and then let me know if it’s working. If not, go through the normal recovery process.
Like, I get it, you’re being thorough and don’t want to just blindly trust the user, but I’m only talking to you because I already tried your quick fixes. Please understand.
As an IT director, I encourage my techs first action to be to connect to the clients machine and ask them to “show me what’s happening.” Then they aren’t to interrupt the user until they complete their explanation except to ask for clarification.
You can see all the steps leading up to the error, the users workflow, typically the desired end result, and the error message.
You also are building rapport with the user making them feel listened to. Far too often I see techs assume something else is the issue, “fix” that, call it done and the user gets frustrated.
Even if you can’t fix it, like so many user issues, at the very least the support experience is a positive one for the end users. Sometimes it’s just that a specific preference isn’t in an applications options or they need to change a step in their workflow. But at least the end users was listened to and their experience and frustration was validated.
If you have metrics or surveys, it’s always interesting to hear a user write in that the issue was not resolved, but they were extremely satisfied.
I’m doing that and generally the next step after that is : “OK, can you do it again and this time DO NOT CLOSE THE ERROR POPUP so we can get information on what is happening”
Also a restart really does fix a big chunk of problems. An app not working right? Force quit & reopen the app. Problem solved. Phone or computer bugging out? Reboot. Problem solved.