Understanding multilevel decisioning and the Context Dictionary
Pega Customer Decision Hub enables you to use multilevel decisioning to control how next best actions are presented to various levels of customer contacts, such as a head of household, account owner, or device owner.These levels are referred to as customer contexts and can represent, for example, individual subscribers, as well as households or accounts, all treated as different audiences that must be communicated with in different ways. For example, you can offer the account owner a family data plan that applies to the whole account, and also send out new phone offers to individual household members that qualify for them.
Understanding the relationship between context entities, associated data, and others
Refer to the following section for an explanation of several terms used to describe various aspects of multilevel context creation, and the relationships between them.
- Context entity
- Any entity on which next-best-action decisions can be made. Depending on the industry, this entity can represent, for example, an account, a household, or a policy membership.
- Primary context
- This context represents the individual to whom you communicate next-best-action decisions. For example, the primary context for an account is the account owner, and the primary context for a policy is a policy member. After a decision is made for the context entity, the primary context receives the resulting next-best-action.
- Associated data
- A data entity directly related to either a context entity, or another associated data entity. For example, data about a customer's product holdings can be associated with the Customer context entity, and data about product details can be associated with data about a customer's product holdings. Associated data provides additional information about the context that the Next-Best-Action strategy can then use to make decisions.
- Context Dictionary
- The Context Dictionary enables you to define context entities and primary contexts, as well as the relationship between them. You can also use it to manage the associations between various contexts and associated data. You can access the Context Dictionary through the menu in App Studio.
Supported context definitions
The relationship between context entities and primary contexts must have a parent-child relationship and follow one of the following patterns:
Other configurations, such as having multiple sibling entities under one parent entity, are not supported. If you have multiple brands, organize the customer contexts in such a way as to cover all the brands in one parent-child structure.
Previous topic Understanding Next-Best-Action Designer basics Next topic Configuring the Context Dictionary