Difference between revisions of "Customer raising either Incident or Service Request"

From Hornbill
Jump to navigation Jump to search
(Created page with "<div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> __NOTOC__Home > How To > [[:Category:How_To_-_Servic...")
 
 
Line 6: Line 6:
 
|style="width:73%"|
 
|style="width:73%"|
 
==Introduction==
 
==Introduction==
In creating a Progressive capture for an Incident, you might want to branch from one Progressive Capture to another as outlined on https://wiki.hornbill.com/index.php/Switch_Between_Progressive_Captures or you might wish to Switch Call Classes from Incident to Service Request. For example, a customer may be raising an Incident using the portal and if they choose an answer, it continues being an Incident but if they choose another option it becomes a Service Request. A Switch Node in the Progressive Capture would not work because an Incident and Service Request need to have different Business Processes.
+
In creating a Progressive capture for an Incident, you might want to branch from one Progressive Capture to another as outlined on https://wiki.hornbill.com/index.php/Switch_Between_Progressive_Captures or you might wish to give the customer the option of raising either an Incident to Service Request. For example, a customer may access the portal with the desire to log an Incident if they have an issue with an existing service or the option to raise a Service Request regarding a service they wish to request.
  
  

Latest revision as of 15:43, 20 June 2018

Home > How To > Service Manager > Customer raising either Incident or Service Request

Introduction

In creating a Progressive capture for an Incident, you might want to branch from one Progressive Capture to another as outlined on https://wiki.hornbill.com/index.php/Switch_Between_Progressive_Captures or you might wish to give the customer the option of raising either an Incident to Service Request. For example, a customer may access the portal with the desire to log an Incident if they have an issue with an existing service or the option to raise a Service Request regarding a service they wish to request.


Related Articles

Customer raising either Incident or Service Request

In such a scenario, it would be best to use the catalog items against the services. For the Incident, use one Service and catalog Item pertaining to Incidents and for the Service Request, use either the same service and a different catalog item or another service altogether. It all depends on the configuration you choose in the Service.

ServiceIncident.PNG

One service can have a Catalog Item specifically for raising Incidents.

ServiceSR.PNG

The same service can have a Catalog Item that can be used for raising Service Requests.

So depending on the customer's issue they can either use one catalog item or the other to raise either an Incident or Service Request.

CustomerServices.PNG