This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to handle multiple similar Incidents smartly.

Service Desk 7.4

If a Service goes down(due to say Hardware malfunction) all of the effected customers create incidents, and technicians have to provide the same details/explanation(via notes) to all the incidents one by one.

1) is there any option to address multiple similar Incidents(for the same Item) from different customers at a time.
2) if a server/service(item) goes down unexpectedly, is there any option to configure the alerts so that when customer goes to Service Desk portal to create the Incident he/she can see the alert about that offline service.
3) if a server/service(item) goes down planned/un-planned, in both the cases how can we stop customers to create Incidents, as otherwise every effected customer would create the Incident and technicians has to handle all the Incidents one by one(issue # 1)

Please help/guide.
  • 0

    If a Service goes down(due to say Hardware malfunction) all of the effected customers create incidents, and technicians have to provide the same details/explanation(via notes) to all the incidents one by one.

    1) is there any option to address multiple similar Incidents(for the same Item) from different customers at a time.

    Got the solution ;-). Incident Group is the solution to handle similar type of incidents.


    2) if a server/service(item) goes down unexpectedly, is there any option to configure the alerts so that when customer goes to Service Desk portal to create the Incident he/she can see the alert about that offline service.
    3) if a server/service(item) goes down planned/un-planned, in both the cases how can we stop customers to create Incidents for that Service(item)

    Now I am still looking for a solution to prevent customers from creating Incidents if a Service(Item) goes offline unexpected, and to let the customers know via Alerts(tickers on the Service Desk portal) that the particular service is down/offline for that much time.