Skip to main content

Adding context to next-best-action decisions

Suggest edit Updated on September 12, 2020

Some of the key aspects of making good next-best-action decisions is understanding why the customer is calling today, knowing the call center's average handle time (AHT), and being aware of any other contextual information from the agent's conversation with the customer. This information is sent to Pega Customer Decision Hub to influence the next-best-action results.

The following table describes the Pega-provided context settings for next-best-action decisions.

Service Intents
The service intent tasks that are currently queued for the customer.
CallVolumeIndicator
The current call volume in the contact center, for example, High, Moderate, or Low.
InteractionGoal
The goal for the interaction as defined in Pega Customer Service for Financial Services.
Intent Channel
The interaction type, for example, Call, Chat, IVR, or Social.
IVR.VRU Functions
The options indicated within the IVR.
CSMapAdditionalContext
Add additional context properties, as needed.

Complete the following steps to add intent-specific context to Pega Retail Advisor decisions.

  1. Open the Int-PegaCDH-Container-Request.MapContext data transform rule in your implementation layer.
    Note: The first item in this data transform is related to questionnaires. If your application uses Pega-provided questionnaires, do not make changes to this item.
  2. Under the primary intent page, use the Primary.Contexts page list property to specify context attributes for the intent task. For each context item, specify values for the following properties.
    • Type
    • Key
    • Value
  3. Click Save as.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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