Post by account_disabled on Mar 14, 2024 9:03:57 GMT
Ill tell you how to maintain the required SLA level with maximum convenience and customer involvement organize comfortable and efficient support work and also about various features of the new solution. At first everyone worked with requests in regular Jira. Imagine the support service of any large service company. This is roughly how everything works for us the process of receiving and processing requests for maintenance or repair of equipment is generally standard.
The customer sends an email or creates a request in Jira we receive Buy Email List a request with the status new. It is picked up by the hour first line and then we look at the serial number is it beating or not is it supported or not we supplement the application with information and transfer it to specialized engineers. An engineer joins. If necessary he carries out additional diagnostics orders spare parts and moves the request further from one status to another in progress awaiting delivery etc.
Receives a notification asking him to evaluate the work. For him this is where the path ends but for us it can continue. Engineers return unused spare parts to the warehouse test the hardware and analyze the causes of the incident. Afterwards we send a request for closure from the engineer. Finally the first line evaluates the engineers work and closes the request completely. fact that they almost buried service with tens of thousands of users because they didnt bother to send a notification ildarz hours ago And this is again a question of the quality of management namely business not technical. This is far from a fact according to the article it looks like a technical management problem.
The customer sends an email or creates a request in Jira we receive Buy Email List a request with the status new. It is picked up by the hour first line and then we look at the serial number is it beating or not is it supported or not we supplement the application with information and transfer it to specialized engineers. An engineer joins. If necessary he carries out additional diagnostics orders spare parts and moves the request further from one status to another in progress awaiting delivery etc.
Receives a notification asking him to evaluate the work. For him this is where the path ends but for us it can continue. Engineers return unused spare parts to the warehouse test the hardware and analyze the causes of the incident. Afterwards we send a request for closure from the engineer. Finally the first line evaluates the engineers work and closes the request completely. fact that they almost buried service with tens of thousands of users because they didnt bother to send a notification ildarz hours ago And this is again a question of the quality of management namely business not technical. This is far from a fact according to the article it looks like a technical management problem.
