The following procedure walks you through the typical steps to log an Incident. A Request follows a similar workflow.
Good to know:
To log an Incident:
A new Incident Record is created with a unique Incident ID) and a status of New. The Incident automatically enters the Record phase.
If an exact match is found, the Requestor fields are auto-populated with the Customer’s name, avatar, e-mail, and phone. If multiple matches are found (ex: Multiple Customers named Max), the Contact Manager opens so that you can select the appropriate Customer.
Tip: Description is a Rich Text field. To format the text or embed an image, click the Zoom button .
After all required fields are completed, the Incident automatically enters the Classify phase.
Note: When the Incident is saved , an e-mail is automatically created and sent to the Customer to confirm receipt and relay the Incident number (Incident ID). If the Incident is resolved before the first save, the receipt e-mail is not sent because the Resolve e-mail is already being sent. A Journal-History record is created to track the e-mail communication. View e-mails in the Incident Journals tab (Arrangement section).
Note: Category is filtered by Service; subcategory is filtered by category. This three-tiered categorization determines the Incident Type (Incident or Request), which Specifics form to display to capture the appropriate details, and which SLA to invoke.
Tips: If you do not know the three-tiered categorization, provide a word in the Quick Classify field (ex: Printer) , and then press TAB or ENTER to locate a possible match. Wildcards (% or *) can be used when searching. If matches are found, the Category Selector opens to select the appropriate categorization. To browse all categorizations, click the Category Selector button to launch the Category Selector.
After an Incident is identified as an Incident or Request, the relevant Specifics form is displayed.
The priority is displayed in the Priority alert bar of the Quick Info Tile.
After a priority is selected, respond by and resolve by target times are calculated based on the defined priority target times in the invoked SLA, and are then displayed in the SLA section of the Quick Info Tile.
The selected CI record appears on the Configuration Items tab (Arrangement section).
After the Incident is categorized and prioritized, the Incident automatically enters the Investigate/Fulfill phase. (This example follows an Incident, so it enters the Investigate phase. Request Fulfillment follows a similar workflow.)
The Incident status changes to Assigned and the ownership information appears in the Quick Info Tile.
The Incident status changes to In Progress and stamps the Date/Time milestone.
CSM prompts you to log the resolution/fulfillment details and possibly a Cause Code (if it is an Incident).
After the Close Description and Cause Code are logged, a Resolution Details record is created and appears on the Resolution Details tab (Arrangement section) to track the resolution, the Incident status changes to Resolved, and the Incident automatically enters the Resolve phase. An e-mail is created and sent to the Customer to notify him that his Incident was resolved.
After three days, an Automation Process automatically closes the Incident, the Incident status changes to Closed, and the Incident enters the Closed phase. An e-mail survey is automatically created/sent to the Customer to notify him that his Incident was closed and to solicit feedback.
Note: To manually close the record sooner, click the Close Incident link in the I Want To section of the Quick Info Tile.
If, during the three days, you discover that the Incident/Request is not ready to be closed, reopen the Incident/Request by clicking the Reopen Incident link in the Status bar of the Quick Info Tile. If reopened, the Status changes to Reopened and the Incident can be investigated/fulfilled again.