Difference between revisions of "Switch from Incident to Service Request"
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
<div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | <div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | ||
− | __NOTOC__[[Main Page|Home]] > [[How To]] > [[:Category:How_To_-_Service_Manager|Service Manager]] > | + | __NOTOC__[[Main Page|Home]] > [[How To]] > [[:Category:How_To_-_Service_Manager|Service Manager]] > Customer raising either Incident or Service Request |
</div> | </div> | ||
{|style="width: 100%" | {|style="width: 100%" | ||
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 | + | 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. |
Line 17: | Line 17: | ||
:* [[Hiding Unanswered questions|Hiding Unanswered questions]] | :* [[Hiding Unanswered questions|Hiding Unanswered questions]] | ||
:* [[View for future dates|View for future dates]] | :* [[View for future dates|View for future dates]] | ||
− | :* [[ | + | :* [[Customer raising either Incident or Service Request|Customer raising either Incident or Service Request]] |
|} | |} | ||
− | == | + | ==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. | 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. | ||
Line 27: | Line 27: | ||
One service can have a Catalog Item specifically for raising Incidents. | One service can have a Catalog Item specifically for raising Incidents. | ||
− | [[File: | + | [[File:ServiceSR.PNG|700px]] |
The same service can have a Catalog Item that can be used for raising Service Requests. | The same service can have a Catalog Item that can be used for raising Service Requests. | ||
Line 34: | Line 34: | ||
[[File:CustomerServices.PNG|700px]] | [[File:CustomerServices.PNG|700px]] | ||
− | |||
− |
Latest revision as of 09:32, 25 June 2018
Home > How To > Service Manager > Customer raising either Incident or Service Request
IntroductionIn 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.
|
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.
One service can have a Catalog Item specifically for raising Incidents.
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.