Forum Discussion

richie967's avatar
richie967
Active Contributor
6 years ago

Notifying more than one customer when an update is made

Hi, 

 

I have recently started using Service desk. I have 4 users. and multiple companies with customers. I have two main questions with the system.

 

1. Assigning an incident to a different customer -

For the sake of this scenario, lets call it "company A". Company A has two customers. "Customer A" and Customer B". Customer A raises an incident. Then the technician works on the incident. How does the technicians assign the incident to "Customer B"? If it was created by "Customer A"?

 

2. Notifying all customers in the same company when an incident is updated

How do we notify all customers in the same company when a technician updates an incient?

 

Cheers, Rich

  • AshC's avatar
    AshC
    Retired GoTo Contributor
    6 years ago

    Hi Rich,

    Welcome to the Community.

     

    If you need to change an Incident to a different Customer, you may do this in the upper right of the Incident where it says Customer in Tile 1:

     

    When you close an Incident, the original reporter will be notified by default.  You may also create Watchlists as needed for Incidents where multiple users are affected.  Then if a customer is granted access to a service, they become available to be added for selection as the customer for all incidents raised on the service.

     

    Reference guide:  https://support.logmeininc.com/gotoassist-service-desk/help/create-incidents-g2asd060002

     

     

    • richie967's avatar
      richie967
      Active Contributor
      6 years ago

      Hi AshC,

       

      Thanks for the information, whilst it's important that a technician can change the customer on on an incident. It is very common that a customer needs to pass the incident to one of their colleagues. How do they do this?

       

      Also, regarding the watchlist, how do we automatically send a notification out to all customers in a company when a technician updates (NOT CLOSES) an incident?

       

      There is often more than one customer at the customers end working on the issue so it is important that all customers can see the update. This is causing issues now.

       

      Cheers, Rich