I'm annoyed with that kind of response because I want to know what was broken, so I can keep an eye out for it in the future or be careful not to trigger the behavior.
I'm annoyed with that kind of response because I want to know what was broken, so I can keep an eye out for it in the future or be careful not to trigger the behavior.
Those messages can be a little short. For the back end staff, I hope they collect meaningful information to resolve subsequent issues down the road. But I don’t expect the user to respond to the IT staff w “thank you. I can verify you solved my problem as I can now perform eigenvalue decomposition” What pissed me off was my occasional lazy employee who would report the problem fixed but no verbiage as to what was fixed. Problem would reoccur and everyone would be frustrated.