Difference between revisions of "PEC-IWD/Current/Administrator/IWDPrioritization"

From Genesys Documentation
Jump to: navigation, search
m (Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2")
(Published)
Line 1: Line 1:
 
{{Article
 
{{Article
 
|Standalone=No
 
|Standalone=No
|DisplayName=View, edit and create Prioritization schemas
+
|DisplayName=View, edit, and create Prioritization schemas
|TocName=View, edit and create Prioritization schemas
+
|TocName=View, edit, and create Prioritization schemas
|Context=How to set up and work with the Prioritization schemas that control how workitems' priorities are updated.
+
|Context=Set up and work with the Prioritization schemas that control the initial prioritization and subsequent reprioritization of work items, emails and leads ("work items").
 
|ComingSoon=No
 
|ComingSoon=No
 
|Platform=GenesysEngage-cloud
 
|Platform=GenesysEngage-cloud
|Prereq=
 
 
|Section={{Section
 
|Section={{Section
|sectionHeading=
 
|anchor=
 
 
|alignment=Vertical
 
|alignment=Vertical
|Media=
+
|structuredtext={{NoteFormat|Changes to prioritization schemas can have significant impacts on contact center operation.|}}A Prioritization schema defines an initial priority for new work items in a Category, plus the timestamp (work item age) at which subsequent reprioritizations take place and what the new priority value at each reprioritization will be. It also defines the Service Level Agreement (SLA) for the Category, and how work items are prioritized post-SLA.  A schema can be used by multiple Categories.
|image=
 
|structuredtext=A Prioritization schema defines an initial priority for new workitems in a Category, plus the timestamp (workitem age) at which subsequent reprioritizations take place and what the new priority value at each reprioritization will be. It also defines the Service Level Agreement (SLA) for the Category, and how workitems are prioritized post-SLA.  A schema can be used by multiple Categories.
 
  
{{NoteFormat|Genesys recommends that you start with simple linear prioritization for their environments. As you become more accustomed to how prioritization works in your environment, you can evolve to a more complex prioritization graph. Genesys also recommends that you reduce the interval as the SLA approaches to increase the probability of workitems being assigned to an employee, as the priority is used to reflect the business value of the work.
+
{{NoteFormat|Genesys recommends that you start with simple linear prioritization for their environments. As you become more accustomed to how prioritization works in your environment, you can evolve to a more complex prioritization graph. To increase the probability of work items being assigned to an employee, Genesys also recommends that you reduce the interval as the SLA approaches, because the priority is used to reflect the business value of the work.
  
You can refine the graph by dragging and dropping the curve to represent the business value of the work item over the expected lifecycle. So if there are tiered penalties for work items that breach their due date and time, the graph after SLA can be arranged to reflect these tiers.}}
+
You can refine the graph by dragging and dropping the curve to represent the business value of the work item over the expected lifecycle. So if there are tiered penalties for work items that breach their due date and time, you can arrange the graph after SLA to reflect these tiers. |}}
|structuredtextwide=
 
|FAQHeading=
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 26: Line 19:
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|Media=Image
 
|Media=Image
|image=Prioritization_1.png
+
|image=Prioritization_5.png
|structuredtext=#Select the '''Settings''' tab.
+
|structuredtext=On the '''Configuration''' tab, select the '''Prioritization''' tool from the left toolbar. This displays Prioritization schema details. You can edit them if you have the appropriate privileges.  
#Select the Prioritization tool from the left toolbar.
 
 
 
The Prioritization schema details are displayed and can be changed if you have the appropriate privileges. Remember that such changes can have large impacts on contact center operation.  
 
  
 
You can edit the schema by:
 
You can edit the schema by:
Line 41: Line 31:
  
 
Use the '''Reset''' button to reset changes made in the graph and priority tables.
 
Use the '''Reset''' button to reset changes made in the graph and priority tables.
|structuredtextwide=
 
|FAQHeading=
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 48: Line 36:
 
|anchor=Fieldnames
 
|anchor=Fieldnames
 
|alignment=Vertical
 
|alignment=Vertical
|Media=
+
|structuredtext={{NoteFormat|Changes that you make in the static fields and in the table are reflected dynamically in the '''Priority over time''' graph.|}}
|image=
 
|structuredtext={{NoteFormat|Changes in the static fields and in the table are reflected dynamically in the '''Priority over time''' graph.}}
 
  
 
*'''Name'''—The schema name.
 
*'''Name'''—The schema name.
 
*'''Urgency'''—The units in which the intervals for calculation are denominated:  Days, Hours or Minutes.
 
*'''Urgency'''—The units in which the intervals for calculation are denominated:  Days, Hours or Minutes.
*'''SLA'''—The interval (Days, Hours or Minutes) by the end of which workitems must be completed.
+
*'''SLA'''—The interval (Days, Hours or Minutes) by the end of which work items must be completed.
*'''With priority management over'''—The post-SLA interval (Days, Hours or Minutes) during which the workitems are to be monitored and managed.
+
*'''With priority management over'''—The post-SLA interval (Days, Hours or Minutes) during which the work items are to be monitored and managed.
*'''Priority'''—Minimum, SLA and Maximum priorities for the workitems.
+
*'''Priority'''—Minimum, SLA and Maximum priorities for the work items.
*'''Speed of increase as SLA approaches'''—Use the slider bar to accelerate or decelerate the change in priority when workitems under this schema are reprioritized before their SLA. As you move the slider bar, the curvature of the '''Priority over time''' graph changes dynamically to reflect the changes. A straighter line indicates a more single-speed regime. A more curved line indicates acceleration as the SLA approaches.
+
*'''Speed of increase as SLA approaches'''—Use the slider bar to accelerate or decelerate the change in priority when work items under this schema are reprioritized before their SLA. As you move the slider bar, the curvature of the '''Priority over time''' graph changes dynamically to reflect the changes. A straighter line indicates a more single-speed regime. A more curved line indicates acceleration as the SLA approaches.
*'''Steps'''—The number of times the workitems under this schema are reprioritized, both before and after their SLA.
+
*'''Steps'''—The number of times the work items under this schema are reprioritized, both before and after their SLA.
 
*'''Reduce interval as SLA approaches'''—Use the slider bar to alter the interval between reprioritization steps as the SLA approaches.
 
*'''Reduce interval as SLA approaches'''—Use the slider bar to alter the interval between reprioritization steps as the SLA approaches.
|structuredtextwide=
 
|FAQHeading=
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
Line 68: Line 52:
 
|alignment=Horizontal
 
|alignment=Horizontal
 
|Media=Image
 
|Media=Image
|image=Prioritization_2.png
+
|image=Prioritization_6.png
|structuredtext=#Select the '''Settings''' tab.
+
|structuredtext=To create a new Prioritization schema, on the '''Configuration''' tab, select the '''Prioritization''' tool from the left toolbar and click '''Add prioritization...'''  
#Select the Prioritization tool from the left toolbar.
 
#Click '''Add prioritization...''' to create a new Prioritization schema.
 
  
 
Use the field definitions above to set up your new schema. Some fields have default values, listed here:
 
Use the field definitions above to set up your new schema. Some fields have default values, listed here:
Line 85: Line 67:
 
**'''Before SLA'''&mdash;<tt>10</tt>
 
**'''Before SLA'''&mdash;<tt>10</tt>
 
**'''After SLA'''&mdash;<tt>5</tt>
 
**'''After SLA'''&mdash;<tt>5</tt>
|structuredtextwide=
 
|FAQHeading=
 
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Revision as of 16:47, March 31, 2021

Set up and work with the Prioritization schemas that control the initial prioritization and subsequent reprioritization of work items, emails and leads ("work items").

Important
Changes to prioritization schemas can have significant impacts on contact center operation.
A Prioritization schema defines an initial priority for new work items in a Category, plus the timestamp (work item age) at which subsequent reprioritizations take place and what the new priority value at each reprioritization will be. It also defines the Service Level Agreement (SLA) for the Category, and how work items are prioritized post-SLA. A schema can be used by multiple Categories.
Important
Genesys recommends that you start with simple linear prioritization for their environments. As you become more accustomed to how prioritization works in your environment, you can evolve to a more complex prioritization graph. To increase the probability of work items being assigned to an employee, Genesys also recommends that you reduce the interval as the SLA approaches, because the priority is used to reflect the business value of the work. You can refine the graph by dragging and dropping the curve to represent the business value of the work item over the expected lifecycle. So if there are tiered penalties for work items that breach their due date and time, you can arrange the graph after SLA to reflect these tiers.

View and edit Prioritization schema

On the Configuration tab, select the Prioritization tool from the left toolbar. This displays Prioritization schema details. You can edit them if you have the appropriate privileges.

You can edit the schema by:

  • Changing the values in any of the fields in the top part of the panel.
  • Changing the priority values directly in the hideable table on the right of the panel.
  • Dragging the individual data points up or down on the Priority over time graph.

Use the Cancel button to abandon all changes entered on the page.

Use the Reset button to reset changes made in the graph and priority tables.

Field names

Important
Changes that you make in the static fields and in the table are reflected dynamically in the Priority over time graph.
  • Name—The schema name.
  • Urgency—The units in which the intervals for calculation are denominated: Days, Hours or Minutes.
  • SLA—The interval (Days, Hours or Minutes) by the end of which work items must be completed.
  • With priority management over—The post-SLA interval (Days, Hours or Minutes) during which the work items are to be monitored and managed.
  • Priority—Minimum, SLA and Maximum priorities for the work items.
  • Speed of increase as SLA approaches—Use the slider bar to accelerate or decelerate the change in priority when work items under this schema are reprioritized before their SLA. As you move the slider bar, the curvature of the Priority over time graph changes dynamically to reflect the changes. A straighter line indicates a more single-speed regime. A more curved line indicates acceleration as the SLA approaches.
  • Steps—The number of times the work items under this schema are reprioritized, both before and after their SLA.
  • Reduce interval as SLA approaches—Use the slider bar to alter the interval between reprioritization steps as the SLA approaches.

Add a new Prioritization schema

To create a new Prioritization schema, on the Configuration tab, select the Prioritization tool from the left toolbar and click Add prioritization...

Use the field definitions above to set up your new schema. Some fields have default values, listed here:

  • UrgencyDays
  • SLA50
  • With priority management over80
  • Priority
    • Minimum0
    • At SLA500
    • Maximum600
  • Steps
    • Before SLA10
    • After SLA5
Comments or questions about this documentation? Contact us for support!