Invoking the next best action
In Pega Customer Decision Hub™, you can determine the next best action by invoking the next-best-action strategy framework. As a System Architect, use the following code sample to call the next-best-action real-time container: Sample code to invoke next best action.
In the code sample, replace the following variables, where:
- Retrieve Customer ID code is your company's own code that retrieves the Customer ID.
- Your company's URL is a web address of your company's next best action container.
- Context can be one of the predefined values listed in Context values for determining next best action.
Type | Value | Key |
Intent | Evaluate internet equipment | Recents |
Intent | Moderate | CallVolumeIndicator |
Intent | Build Value | InteractionGoal |
Intent | phone | Channel |
Intent | Passive | NetPromoterCategory |
Channel | N/A | Queuename |
Intent | N/A | CustomerValue |
Intent | N/A | NewCustomer |
Intent | Transfer line | IVR |
Intent | N/A | CreatedFromAnonymous |
Intent | Transfer line | IVROption |
Call type | N/A | DNIS |
Call type | INBOUND | Purpose |
Intent | true | RetailOffersOnly |
CustomerDetails | PEGACRM-ENTITY-CONTACT CON-20513 | ID |
Intent | N/A | Context |
IntentReason | N/A | Intent |
Intent | PegaComm-FW-CPMCFW-Work-Interaction-Call | ObjClass |
Intent | N/A | SuggestedActions |
Intent | N/A | NegotiationCost |
Intent | BillingInquiry | WSSAction |
Intent | N/A | Registered for eBill |
Bundle | Internet | ServicesRequired |
Bundle | Mobile | ServicesRequired |
Bundle | Phone | ServicesRequired |
Bundle | TV | ServicesRequired |
Bundle | Internet | ServicesType |
Bundle | Mobile | ServicesType |
Bundle | Phone | ServicesType |
Bundle | TV | ServicesType |
Bundle | 3 | BundleCount |
Previous topic Tutorial: Using Pega Next-Best-Action Advisor in your desktop application Next topic Skipping bundle configuration