Team tab user categories
The Team screens show the policy transaction workload for groups or individual users. The Team screen determines whether a user has work to do on a policy transaction depending upon whether the user is a by-role or by-activity user.
- By-role – These users work on policy transactions when they have a participating role. A customer service representative (CSR) is an example of a by-role user. The CSR is the producer for a policy transaction and makes sure that the policy transaction progresses. The CSR may not have any activities associated with the policy transaction. For this category of user, the Team screen displays policy transactions on which the user has a role.
- By-activity – For certain types of users, having a role on a policy transaction does not represent work. An underwriter may have a role on thousands of policy transactions. For example, one underwriter may have a role on the large number of policies generated by a group CSRs. For a personal lines which renew every six months, a third or more of the policies may have an active renewal in process at any time. One underwriter has a role for each renewal even if the renewal is expected to complete automatically without intervention. Even though the underwriter has a role, these renewal policy transactions do not represent work for the underwriter unless a policy transaction requires some action. An activity makes the underwriter aware that work is required on the policy transaction. For this category of user, the Team screen displays policy transactions on which the user has an activity.
For by-role users, the detail view lists all policy transactions on which the user has a role. For by-activity users, the detail view lists only policy transactions on which the user has an activity. In both cases, the list displays information based on the category of the user being viewed, not the user viewing that information.
Renewal policy transactions are an exception. The Team screen displays renewal policy transactions by-activity for both categories of users.
The Summary screen displays both by-activity and by-role policy transactions and policy transactions. You can select View Policy Transaction to view policy transactions By Role or By Activity. The default view is By Role. The View policy transaction selector does not appear for In Queue or an individual user because the user type determines the Team screen display.
In the base configuration, the Team tab determines the user category
by checking the User.UserType
property. In the base configuration, the UserType typecodes are mapped
to Team tab user types
as follows:
|
Team tab user category |
|---|---|
|
By-activity |
|
By-activity |
|
By-activity |
|
By-role |
|
By-activity |
unknown |
By-activity |