Posted: Wed Nov 22, 2017 6:09 am Post subject: Root Cause in IM - what if customer fault?
I work in a company that develops and sells sofware. We have a technical support team that handles incidents that customers report because they believe are due to our software. We have also a development team that handles problem reports when a software error must be fixed.
Usually, the technical support restores the service to the customer and then, when they believe the root cause of the incident is due to a software defect, they close the incident to open a problem, that is then assigned to development.
However, an incident may also be due to a customer fault.
In general, our customers want always to know the root cause of the incidents they report. The root cause may be related to our software or to their fault.
It is not clear to me what the technical support should do, after service restoration. Should they do an analysis within the incident to understand if the incident was due to the customer or to the software? And then, in this case, if they found a software defect or believe it's a software defect, open a problem? Or should they open a problem to do the analysis and assign the problem to themselves?
Does anyone of you have experience on this scenario? Suggestions are welcome.
I suggest do an analysis to identify the root cause of the problem. If it's a software defect, open a problem and give it to development. If it's otherwise, then do otherwise. Just do whatever is the SOP of the company in these kinds of situations. I think that's a safer approach to this problem.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum