this post was submitted on 11 Jun 2024
204 points (97.7% liked)
Asklemmy
43942 readers
790 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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"