Siebel Energy Guide > Service Requests and Trouble Tickets in Siebel Energy >

Scenario for Service Requests and Trouble Tickets in Siebel Energy

This scenario shows a sequence of procedures performed by a customer service representative (end user) and a workflow manager (administrator). Your company may follow a different sequence according to its business requirements.

During a typical day in a customer service organization, a group of Customer Service Representatives (CSRs) respond to customer phone calls and assign thirty trouble tickets. Twenty of the trouble tickets are solved using existing solutions, which the CSRs associate with the trouble tickets. Ten of the trouble tickets require new solutions, which the CSRs create after performing the necessary research. Between them, the CSRs make two mistakes when they click the wrong part of the user interface during an operation. They note their mistakes in email messages to the manager and ask the manager to correct them.

At the end of the day, the manager performs routine administrative work on the solutions that were created during the day, starting with correcting the two errors. In one error, a CSR accidently associated a solution with the wrong product defect; the manager corrects this by dissociating them. A different CSR incorrectly associated a solution with a resolution document; the manager resolves the problem by dissociating them.

Next, the manager reviews each of the new solutions in turn. She performs a query for the solutions that were created during the day and examines the first record. She checks that it is associated with a trouble ticket and then reads the solution. Being familiar with this type of problem, the manager recalls a similar solution that may be useful for a CSR to know about. She locates the similar solution and associates the two records.

The manager also recalls a technical document on the company's network that might help to explain the problem. She locates the document, creates a new resolution document record, attaches the document to the record, and associates the record with the solution. She is now satisfied with the solution, so she changes its status to Final and makes sure that it is only visible internally.

The manager reviews the second solution and checks that it is associated with a trouble ticket. This solution is incomplete so the manager leaves the status as Draft. She informs the CSR who created the solution that this problem is related to, and should be associated with, a known product defect, and asks the CSR to research it more thoroughly.

The manager checks that the third solution is associated with a trouble ticket and reads the resolution documents associated with it. One of the resolution documents is an internal technical document that was recently revised and should be replaced. The manager dissociates the solution from the document, locates the revised version on the network, adds it to the database, and associates it with the solution. She then changes the status of the solution to Final.

The manager reviews each of the remaining newly created solutions in a similar manner.

Figure 15 shows the sequence of procedures that end users might follow to manage trouble tickets.

Figure 15.  Example of Sequence for Trouble Tickets