Siebel Assignment Manager Administration Guide > Assignment Methodology, Strategies, and Scenarios > Examples for Using Delegated Assignment >

Summary for Working with Delegated Administrators

This summary is one of the topics for Examples for Using Delegated Assignment.

Figure 12 shows a high-level process flowchart of the delegated assignment scenario examples described in Examples for Using Delegated Assignment.

Figure 12.  Sample Process Flowchart for Delegated Assignment

Figure 12 shows the following relationships:

• Amy is the EVP of Sales and is the assignment administrator. Amy must first create root-level rule groups, child rule groups, and rules, and add criteria templates (templated criteria) and owners of the child rule groups to the assignment rules before delegated assignment can be implemented.
• Lance and Henry are sales VPs and are delegated administrators (2nd-tier). Lance and Henry must first inherit rules in the rule group Amy created for their respective areas, and can then further refine and delegate those rules further down the hierarchy.
• Sarah and Rick are Sales Managers and are delegated administrators (3rd-tier). Sarah and Rick inherit the rules created by Lance for their respective areas, and then further refine those rules for their sales representatives.
• Robin and Sam are Partners and are delegated administrators (3rd-tier, similar to Sarah and Rick). Robin and Sam inherit the rules created by Henry for their respective areas, and then further refine those rules for their sales representatives.

NOTE:  After a rule is inherited in child rule groups and changes are made to the original rule, such as adding criteria to, expiring, or even deleting the rule, those changes are propagated down the hierarchy to all rules that were inherited from it.

For detailed tasks pertaining to the sample delegated assignment process, see:

• Delegated Assignment Example 1: Assignment Administrator Tasks
• Delegated Assignment Example 2: 2nd-Tier Delegated Administrator Tasks
• Delegated Assignment Example 3: 3rd-Tier Delegated Administrator Tasks
• Delegated Assignment Example 4: 3rd-Tier Delegated Administrator Tasks for Partners

The following points further summarize delegated assignment activities as they pertain to the examples:

• The examples describe a four-level assignment model. However, this is no limit to the number of levels that the delegated assignment manager feature supports, and there is no limit to the number of branches in a level. In these examples, the levels are:

  Level 1 = Amy
  Level 2 = Lance, Henry
  Level 3 = Sarah, Rick, Robin, Sam
  Level 4 = West Sales Reps 1,2,3, and Partner 1 Sales Reps 1,2,3

• Rules group hierarchies are executed from the bottom up. For example, Assignment Manager attempts to use Robin's rules to match a particular lead to a candidate before it tries to use Henry's rules. However, if Robin's rules fail, Assignment Manager then tries Henry's rules, and assigns the lead to Robin, and so on up the hierarchy.

  For more information about rule group hierarchies, see About Hierarchical Rule Groups.

• Each rule group owner can assign a designee.

  Designess have the same responsibilities as an owner. You may want to delegate your ownership to someone else, such as an administrative assistant, to perform the tasks.

  For more information about owners and designees, see Owners and Designees and Adding Owners to the Inheritance Access List.

• Each partner should assign one person as the delegated administrator—in these examples, either Robin or Sam—and that person should manage the partner's rule group. This same person should receive all leads that are not assigned to the partner's sales representatives.
• AAs and DAs can create new criteria (you are not required to use templated criteria). However, it is recommended that the AA create criteria templates (templated criteria) for the most common criteria to ease the learning curve for the DAs.

  For information on how to create new criteria, see Configuring Assignment Criteria.