Siebel Assignment Manager Administration Guide > Assignment Rule Administration > Assignment Methodology and Examples for Creating Assignment Rules >

Example of Creating Assignment Rules for Service Organizations

This topic is part of Assignment Methodology and Examples for Creating Assignment Rules.

This topic gives one example of how to create assignment rules for a service organization. You may use this feature differently, depending on your business model.

Use the following strategy to develop assignment rules for your service organization:

1. Determine the different assignment objects to be assigned.

   Service organizations need to assign ownership of a wide variety of tasks. These tasks may include service requests, activities, and accounts. In addition, a product development organization may need to assign ownership of product defects to engineers. For instance, you may decide to assign only service requests and product defects, because the associated activities are manually assigned by owners of those objects.

2. Determine if multiple assignment objects are assigned using the same assignment rules.

   Multiple assignment objects can be assigned using the same assignment rules. For example, if you are assigning accounts and service requests in the same manner, you can use the same assignment rules by associating those rules with multiple assignment objects.

3. For each assignment object, determine which of the objects is assigned using the same assignment rules.

   The Compare to Object comparison method allows you to assign different groups of objects using different rules. Typically, complex service environments assign different groups of service requests using different rules, such as segmenting the service requests based on service request priority.

4. Determine the strategy for each group of objects to be assigned using the same assignment rules.

   Use the skill criteria to minimize the number of assignment rules. One assignment rule can match different candidates to various objects based on the object characteristics and candidate skills. To determine optimal assignment, determine the criteria that you want to evaluate for each candidate to make sure that the candidate possesses the proper skills to handle the task. These criteria would be the primary type of criteria you would use most frequently for implementing assignments in a customer service environment. These criteria are defined using the Compare Object to Person comparison method in the Assignment Criteria view.

5. Define workload rules.

   Determine the various methods of calculating workloads for employees in your organization. Each workload rule is associated with a specific assignment object. For instance, you can define two workload rules to calculate:

   • Open Service Requests for an employee
   • Critical Service Requests submitted through Siebel eService
6. Define assignment rules, assignment criteria, assignment criteria values, and assignment workloads.

   Using the strategy, rules, and criteria discussed previously, define the assignment rules and the corresponding detail using assignment administration views. In defining rules, criteria, values, and workloads, you can specify scores for each component. These scores are aggregated in determining the total score for each candidate of an assignment rule.

7. Define static and dynamic candidates.

   For static candidates, use the assignment rule Employee, Position, or Organization Candidates view (or use the All People value in the Person Candidates Source field or the All Organizations value in the Organization Candidates Source field) to define eligible employees for assignment. For dynamic candidates, choose the appropriate value from the Person Candidates Source field.

   You may further restrict or weight employees who have different skills using the Compare to Person assignment criteria.

8. Define employee skills.

   After the assignment rules and the corresponding details have been defined, a customer service manager must update the employee skill information (such as product expertise, language skills, and geography). Assignment Manager uses these attributes when evaluating Compare to Person and Compare Object to Person assignment criteria.

9. Release assignment rules.

In the Assignment Rules view, click the Release button. You can then run batch assignment to assign objects affected by the assignment rules. For more information about running Batch Assignment, see Running Batch Assignment.

Figure 7 shows a sample assignment rule for assigning support representatives to a service request.

Figure 7. Assignment Rule for a Service Organization

The assignment rule shown in Figure 7:

• Matches any service request:
  • For Pentium III 600 products
  • With a priority of High
• Uses two criteria with the following values:
  • Product Wildcard. A list of products that include the value CPU Pentium III 600
  • Service Request Priority. A list of service requests whose priority level is High