Skip to main content


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

Intelligent guidance suggested actions

Updated on February 26, 2021

Pega Customer Service has built-in intelligent guidance to suggest the next best task to a CSR during a customer interaction.

Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide Pega Customer Service Implementation Guide

Intelligent guidance includes the following features:

  • Case match - Before an interaction, suggests an in-progress case as the next best action. A case match suggestion shows an Arrow icon, a light blue background, and the case number. The criteria for case matching are defined in a Case Match rule. A switch in the Suggested actions settings enables case matching.
  • Intent When rules - During an interaction, suggests a case type as the next best action based on another task, event, or user information from the previous or current interaction (for example, always suggest to resend a billing statement when a customer calls to request an address change). The criteria for this feature are defined in an Intent When rule. A suggested action shows a Light bulb icon and a dark blue background.
  • Queued task - During an interaction, strongly suggests a case type as a follow-on task for the current interaction. A queued task shows an Arrow icon and a light blue background.

The following figure shows an example of intelligent guidance suggested actions:

Intelligent guidance suggested actions example
Intelligent guidance suggested actions example

Creating Intent When rules

Intelligent guidance uses an Intent When rule to determine when a task should be suggested, queued, or automatically launched.

  1. In the navigation pane of Dev Studio, click Records, and then expand Decision.
  2. Right-click Intent When and select +Create.
  3. Complete the following information.
    • Label - The name for your Intent When rule.
    • Status - Whether the rule is available for use.
    • Apply To - Interaction class, for example, MyApp-Work-Interaction.
    • Add to ruleset - An open ruleset to save the rule to.
  4. Click Create and open.
  5. Configure the Intent When rule by using one or more conditions.
    • Label - The name of the condition that you will use in the criteria logic
    • Data Source - The data source to use.
    • Field - The property from the data source to use.
    • Operation - The comparison operation.
    • Value - The value to compare the field against.
  6. Use the labels from your conditions to complete the criteria logic, for example, (a and b).

Creating Case Match rules

Intelligent guidance uses a Case Match rule to determine when an in-progress task should be suggested at the start of an interaction, based on the interaction context. Use the pyDefaultCaseMatch rule to reduce duplicate cases. A switch in the Suggested actions settings enables case matching.

Pega Customer Service includes a default Case Match rule, CAReviewServiceItems, that you can copy and modify to meet your business needs.
  1. In the navigation pane of Dev Studio, click Records, and then expand Decision.
  2. Right-click Case Match and select +Create.
  3. Complete the following information.
    • Label - The name of the new Case Match rule, for example, FindRecentMatchingCases.
    • Apply To - Interaction class, for example, MyApp-Work-Interaction.
    • Add to ruleset - An open ruleset to save the rule to.
  4. Click Create and open.
  5. In the Must match conditions section, create one or more conditions that identify a match when the conditions all evaluate to true.
    1. Click Add must match condition.
    2. In the Potential duplicates column, select a property to evaluate.
    3. In the Relationship column, select the relationship to the current case type (for example, is same) that determines a potential match.
  6. In the Weighted match conditions section, create conditions that determine the most likely matches by weight.
    1. In the Find potential duplicate cases where the sum of weighted conditions is at least field, enter a weighted sum value that must be reached in order for a case to be considered a match.
    2. Click Add weighted condition.
    3. In the Weight field, enter the weight to calculate when this condition is reached.
    4. In the Condition fields, select the conditions and operators that will result in the weight specified.
  7. Click Save.

Editing Service request options

Configure the context when a service request type will presented in the Add Task menu and the Suggested tasks area during a customer interaction.

  1. In the navigation pane of App Studio, click Case types.
  2. Click the service request type that you want to open.
  3. In the Settings tab, click Service request options.
  4. On the General tab, to select how to group this task on the Add Task menu, select a value from the Change Add Task menu category to list.
    The Add Task menu category field shows the default or currently selected value. The default value comes from either the Interactions settings or the case type template.
    Note: You cannot change the category if the service request rule is in a framework application ruleset or in a locked ruleset.
  5. To display the current case type in the Add Task menu, select the Display in Add Task menu? check box.
  6. In the Suggestion Criteria section, select the criteria that determine when the intelligent guidance feature suggests this case type.
    1. In the Suggest service request When list, select the case type that triggers the suggested action.
    2. In the Action list, select the action when this case type is triggered:
      • Suggested - Suggest this case type in the Intelligent guidance or Next Best Action section of the Interaction Portal. This case type appears with a Light bulb icon and a dark blue background.
      • Queue - Strongly suggest this case type as a follow-on to the currently open case type. A strong suggestion appears in the Intelligent guidance or Next Best Action section of the Interaction Portal, and it has an Arrow icon and light blue background.
      • Auto-Launch - The Intent Task is launched automatically. For more information, see Configuring the Auto-Launch of Intent Tasks, next.
  7. Optional: Click Add new to create additional suggestion criteria, or click Delete to delete the existing condition.
  8. Click Save.

Making a service case available in more than one Add Task category

Sometimes you might need to have a service case available in more than one Add Task category in the Interaction portal if you are servicing different types of customers in different categories. For example, you might want the Update contact profile service case to appear in both the General and the Account Add Task categories.

When you encounter this scenario, create an intent task in Dev Studio by following the steps in Creating an Intent Task. You cannot configure this scenario in App Studio.

Configuring the Auto-Launch of Intent Tasks

Intent Task rules allow the configuration of an automatic launch of a service process at the start of an interaction, based on a When condition defined in the Criteria tab.

  1. Go to the Records explorer, and then click Process > Intent Task to display the Intent Task instances.
  2. Select an instance that suits your business needs.
  3. Click the Criteria tab and enter value in the following fields:
    • Enter an appropriate Intent Condition.
    • Click the Action drop-down arrow and select Auto-Launch.
  4. Click Save As.

    The Auto-Launch option allows the launch of multiple service processes in the interaction if criteria for the Intent Tasks are set to Auto-Launch when defined in multiple Intent Tasks. The auto-launched service process remains in-focus at the start of an interaction.

    Note: If you define multiple conditions for an Intent Task, it is a good practice to select the Auto-Launch option as the first condition; otherwise it will never be evaluated when any of the conditions defined above it are true.

Tags

Pega Customer Service 8.6

Have a question? Get answers now.

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

Visit the Support Center

Did you find this content helpful?

Yes
No

Want to help us improve this content?
Suggest an edit

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us