An operator's access group affects what the operator can do in the application. In addition to the access group, three fields in the operator record influence how the application handles assignment of work to the user.
- Work group
- Chat and messaging settings
- In many implementations, it is more efficient for the application to set values in the operator record during the authentication process than it is to have an administrator manually maintain these records. These rules must be configured as part of the authentication mechanism for your site. For more information, see More about Authentication Services.
- When setting your system-wide security parameters, keep in mind that allowing more than one concurrent login by the same operator might negatively impact some Customer Service application and chat features. In such situations, Pega recommends limiting the number of concurrent sessions to 1. For information, see Specifying the number of concurrent sessions. If you set this value to 1, you can still set the maximum number of concurrent Chat and messaging conversations to a value greater than 1. For information, see Defining chat and messaging settings for an operator and Configuring chat and messaging queues.
Defining the operator work group
The work group setting in the operator record affects how the application delivers work to the operator.
- Review the Operator record.
- Determine the rules for assigning a work group to an operator or the role that multiple operators hold.
- Log in by using an administrator account.
- In the header of Dev Studio, click .
- Select an operator ID.
- On the Work tab, review the work group information for the operator record.
- Determine your policy for assigning a work group to an operator or the role that multiple operators hold.
Defining chat and messaging settings for an operator
The Chat and messaging attributes in the operator record overrides the global settings for chat and messaging, such as the conversation handling capacity of a customer service representative (CSR) and the wait time to allow for the chat window to evaluate the customer queries. For more information about the global chat and messaging settings, see Configuring chat and messaging settings.
- In the navigation pane of App Studio, click and select an operator record.
- To define the number of concurrent conversations a CSR can handle at a same
time, in the Chat and messaging section, enter a value in
the Max concurrent conversations (from this queue)
For example: If the you set the maximum concurrent conversations a CSR can handle to 5, a CSR can work on 5 concurrent conversations only.
- Define the frequency of backlog interactions to a CSR instantly or based on
certain time frame.
- If you set the frequency to Instantly, all the backlog interactions gets assigned to the customer based on the number of concurrent conversations a CSR can handle.
- If you select the For every option, you can set
the frequency delay in getting the backlog interaction assignment to the
CSR based on the time (in Minutes).
For example: If you set the frequency delay time to 5 Minutes, and the maximum concurrent conversations is set to 5, then for every 1 Minute a new interaction assignment gets assigned to the CSR.
- Click Save.
Defining the operator skills
Skill settings in the operator record affect how the application routes work to the operator. Skill settings also affect how the application gets the most appropriate work when using the Get Next Work feature. You must determine the skills that are appropriate for your application and operators.
- Define the skills that are needed for the application.
- Determine which operator records or roles should be associated with those skills.
Defining the operator calendar
The application calendar affects date calculations within the application, such as the date between business days calculation, and the SLA goal and deadline date calculation. The calendar on the operator record is relevant only if you have users who are not working in the same time zone as the rest of the organization. Otherwise, the application uses the calendar on the organization record and you can skip this step.
- Determine the calendar instances that are needed for your application.
- Determine which operator roles need a distinct calendar.
- Determine the operator location.For more information, see More about Calendar data instances.