Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Defining work routing settings for an operator

Updated on June 30, 2021

For continuous and efficient workload management and routing, define skills, work groups, and work queues for operators. As a result, an operator can receive work based on skill set and team membership. For reporting purposes and advanced routing use cases, configure the reporting structure.

For example, when you define the reporting manager of an operator, the manager might receive notifications about the operator's progress on a case.
Before you begin: Create an operator so that a user can access your application. For more information, see Creating an operator ID or Adding an operator by using the organizational chart.
Every operator has a unique worklist that accumulates tasks that the specific operator can retrieve. Additionally, an operator can access a work queue that collects tasks for a team to which the operator belongs. Any team member can pick up tasks from a work queue. Another name for a team is a work group.

For an automated selection of tasks to process, operators can use the Get Next Work logic. Get Next Work automatically prompts users with an assignment that currently has the highest urgency in work queues and work groups that the operator can access.

  1. In the header of Dev Studio, click ConfigureOrg & SecurityOrganizationOperators.
  2. On the Operators tab, select an operator that you want to edit.
    Tip: To find your operator faster, in the Search Text field, enter the operator name, and then click Search.
  3. On the Work tab, in the Organizational unit section, define the affiliation of the operator within the organization by clicking Update, and then provide a relevant organization, division, and unit.
    For example: For an organization, enter the name of your company, for example, UPlusTelco, and then provide a division and unit, such as BankingOperations for a division and Mortgages for a unit.
  4. In the Team field, enter a work group to which the user belongs.
    A work group defines routing of tasks and a reporting manager of the user.
    For example: If you create Team A to review mortgage requests and Team B to investigate issues with mortgage operations, the two teams can use separate areas of your application so that the work is logically separated.
  5. Optional: To assign a user to multiple work groups, click Add a work group, in the text box enter a work group, and then select the radio button next to the work group that you want to set as the default.
  6. Optional: To enhance the reporting options of your application, in the Reports to field, enter the reporting manager for the user.
  7. Optional: To enable routing of tasks based on a skillset, in the Skill field, enter the ability of the user, and then in the Rating field, enter the level of the ability.
    You can apply a rating from 1 to 10, where 10 implies the highest level of the skill.
    For example: To indicate that a user is a fluent speaker of French, in the Skill field, enter French, and then in the Rating field, enter 10.
  8. Optional: To allow the user to process assignments from a work queue that corresponds with the user's work group, in the Work queue section, click Add item, and then provide a work queue and an urgency threshold.
    During Get Next Work processing, your application ignores assignments with urgency lower than the urgency threshold. For more information about Get Next Work, see Customizing the Get Next Work logic.
  9. Optional: To assign the user to multiple work queues, click Add item, and then repeat step 8.
  10. Optional: To trigger the Get Next Work algorithm to retrieve assignments from the work queues of the user first, select the Get from work queues first check box.
    Otherwise, Get Next Work picks up the top assignment on the user worklist, and accesses work queues only if this user's worklist is empty.
    For example: If a user is a member of the Team A to review mortgage requests, the Next Get Work algorithm suggests assignments that the application routes to the Team A work queue first and then moves to the assignments from the user's individual worklist.
  11. Optional: To trigger the Get Next Work algorithm to retrieve assignments from all work queues that correspond with the team that you provided in step 4, select the Use all work queue assignments in user's team check box.
  12. Optional: To trigger the Next Assignment item to consolidate assignments from all of the work queues of the user, sort by assignment urgency, and return the most urgent assignment in any work queue, select the Merge work queues check box.
    If you select the Use all work queue assignments in user's team check box in step 11, the system selects the Merge work queues check box by default and you cannot clear this check box.
  13. Click Save.
  • Previous topic Fields for operator contact information and application access
  • Next topic Fields for operator teams, work queues, and schedules

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us