Skip to main content

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

Using Pega Next-Best-Action Advisor in your desktop application

Updated on August 17, 2021

You can embed Pega Next-Best-Action Advisor into a desktop application by using a mashup script, and customize the script to meet your specific needs. You can then use Pega Next-Best-Action Advisor to either acquire new customers, retain existing customers, or make offers directly from your own application.

Pega Customer Decision Hub Pega Customer Decision Hub Pega Customer Decision Hub Pega Customer Decision Hub Pega Customer Decision Hub Pega Customer Decision Hub

Use case

U+ Comm, a large customer service company, uses Pega Next-Best-Action Advisor without the Pega Customer Service application, but would like a tool for negotiating bundles. U+ Comm can implement the Next-Best-Action Advisor Bundle Negotiator either as a standalone application, or more typically, as integrated into their existing customer service application.

A mashup script allows a business to make the best use of all of the capabilities of Pega Next-Best-Action Advisor with minimal effort by embedding Pega Next-Best-Action Advisor into your own customer service application, for example a call center, and by integrating the two applications seamlessly within a web browser. This type of integrated implementation gives the customer service representative (CSR) a seamless user experience, while using all Pega Platform capabilities and Pega Customer Decision Hub best practices built into Pega Next-Best-Action Advisor.

For more information on Pega Platform capabilities, see Capabilities.

The following figure shows an example of Pega Next-Best-Action Advisor embedded into a customer service application:

Pega Next-Best-Action Advisor embedded into a customer service portal
Pega Next-Best-Action Advisor embedded into a customer service portal
Use this tutorial to learn how to implement the mashup script in your own application, and how to customize the attribute parameters in the dynamically generated code to suit your business requirements. You can, for example, identify a customer by their ID.

Embedding and using the embedded Pega Next-Best-Action Advisor

As a System Architect (SA), use the following process and figure to learn how you can embed Pega Next-Best-Action Advisor into your desktop application. As a CSR, learn how to use Pega Next-Best-Action Advisor that is embedded in another desktop application or a website to fulfill the customer journey.

  1. The CSR takes a call.
  2. The CSR or Pega Next-Best-Action Advisor identifies the customer.
    When Pega Next-Best-Action Advisor is part of Pega Customer Service, customers are identified prior to invoking Pega Next-Best-Action Advisor. As part of a desktop application, customers are identified in one of the following ways:
    • Manually, by the CSR looking at customer name and Customer ID.
    • Automatically, after the the Customer ID invokes the embedded Pega Next-Best-Action Advisor.
  3. The CSR views the detailed customer information (Customer 360).
  4. The SA enables invoking next best action to assess customer needs.
  5. If the next-best-action recommendation is to make the customer an offer, the CSR fulfills the Make Offer journey.
  6. If the next-best-action recommendation is to upgrade or retain the customer, the CSR fulfills the Upgrade/Retain journey.
  7. The CSR configures the offer.
  8. The CSR confirms the offer.
  9. Post Offer processing, for example, pay, schedule, and change order.
    Embedding Pega Next-Best-Action Advisor process flow
    Embedding Pega Next-Best-Action Advisor process flow

Sample code to generate the mashup script

As a System Architect, enable the negotiation capability by launching one of the supported next best actions directly from a desktop application by using the embedded Pega Next-Best-Action Advisor.

  1. Use the following JavaScript function to generate the mashup script that is based on the CustomerID entered by the user: Sample mashup code.
  2. In the sample mashup code, use the following URL for reference:!STANDARD?pyActivity=%40baseclass.doUIAction&action=createNewWork&isWebMashup=true&className=PegaComm-FW-CPMCFW-Work-Negotiation-Retention&flowName=pyStartCase&UserIdentifier=Cscsysadmin&Password=UnVsZXNAMTIzNDU%3D&pzSkinName=CSEndUser&CustomerID=C1000022

  3. For more information on using mashups, see Tutorial: Creating a mashup with Pega Web Mashup.

Next steps

As a System Architect, use the standard Pega Platform capabilities to build a service which takes the results from Pega Next-Best-Action Advisor and makes them available to the host system, for example, a customer service application.

Configure the bundle offers and capture further information such as payments. This integration is beyond the scope of this document. For more information, see Personalizing and purchasing offer bundles in a self-service portal.

Sample code to invoke 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 below.
IntentEvaluate internet equipmentRecents
IntentBuild ValueInteractionGoal
IntentTransfer lineIVR
IntentTransfer lineIVROption
Call typeN/ADNIS
Call typeINBOUNDPurpose
IntentN/ARegistered for eBill

Skipping bundle configuration

When negotiating bundles, as a CSR, you can configure the bundle offer by, for example, choosing the mobile phone color. When the negotiation flow is a part of the embedded Pega Next-Best-Action Advisor implementation, as a SA, you can skip the configuration by deleting the dedicated configuration shape, for example, Equipment Details.

The configuration shape is provided in Pega Next-Best-Action Advisor, but it is more typically used in Pega Customer Service.

You can skip bundle configuration in a bundle negotiation case flow by performing the following actions.
Note: Bundle configuration is only supported by Pega Product Catalog.
  1. In the navigation pane of Dev Studio, click App.
  2. On the Classes tab, search for PegaComm-FW-CPMCFW-Work-Negotiation.
  3. In the list of results, expand ProcessFlow.
  4. Click Negotiation.
  5. In the Negotiate with contact case flow, save the rule to a ruleset in your implementation application, and then click Check out.
  6. Delete the bundle configuration step by right-clicking the Equipment Details shape, and then selecting Delete.
    Deleting the bundle configuration step
    Deleting the bundle configuration step
  7. Click Save, and then click Check in.
    • Previous topic Architecture of the Pega Next-Best-Action Advisor capabilities
    • Next topic Understanding Bundle Negotiator

    Have a question? Get answers now.

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

    Did you find this content helpful?

    Want to help us improve this content?

    We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

    Close Deprecation Notice
    Contact us