Skip to main content


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

Creating payment reminder actions

Updated on July 1, 2021

Create reminder message treatments across different channels.

Note: Next-Best-Action Designer for Retail Banking is configured to support the Collections issue. It includes various groups to organize Customer- or Account-level actions into categories.
Next-Best-Action Designer taxonomy view of the Retail Banking template
A fragment of Next-Best-Action Designer taxonomy view of the Retail Banking template
          showing various Collections groups.

Start configuring payment reminders by creating a payment reminder action under the Pre collection group by doing the following steps:

  1. In Next-Best-Action Designer, click Engagement policy.

  2. Click the Pre collection group under the Collections issue, and then click Edit.

  3. Click the arrow by Account actions, and then scroll to the Actions section.

  4. In the Create Action window under the Account context, in the action title field, enter Early reminder 10D, and then click Create and open.

  5. Specify the Description, Keycode, and any other relevant fields.

  6. In the Engagement policy tab, specify the conditions under which the action should be available to the customers.

    For example: The action is available to customers whose payment due date is within three days, and the amount due is greater than zero.
    Note: The XCAR data model includes the relevant properties for collections decisioning. If you need any additional properties, edit the customer class in your implementation application.
  7. On the Treatments tab, click Add channel.

  8. Configure an email or SMS treatment for the action.

  9. Configure the action flow as described in Configuring the action flow for payment reminder actions.

    Note: The XCAR data model includes the relevant properties for collections decisioning. If you need any additional properties, edit the customer class in your implementation application.
    Email DB template to store NBA recommendation details in DB table
    A configuration of an email DB template to store Next-Best-Action recommendation
                details in a DB table.
  10. To have more control over treatment eligibilities, configure treatment-level eligibility.

Follow a similar approach to create additional payment reminders under Days Past Due30, Days Past Due60, and so on.

  1. In Next-Best-Action Designer, click Engagement policy.

  2. In the Collections list, select DaysPastDue30, and then click EditCreate Action.

  3. In the Create Action window under the Accounts context, in the action title field, enter Payment reminder 15D, and then click Create and open.

  4. Specify the Description, Keycode, and any other relevant fields.

  5. In the Engagement policy tab, specify the conditions under which the action should be available to the customers.

    For example: You can specify the time period when the payment is due, as in the following figure:
    Specifying the time period for payment due date in an engagement policy.
    Note: The XCAR data model includes the relevant properties for collections decisioning. If you need any additional properties, edit the customer class in your implementation application.
  6. On the Treatments tab, click Add channel.

  7. Configure an email or SMS treatment for the action.

  8. Configure the action flow as described in Configuring the action flow for payment reminder actions.

    Note: The XCAR data model includes the relevant properties for collections decisioning. If you need any additional properties, edit the customer class in your implementation application.
  • Previous topic Configuring payment reminders for collections
  • Next topic Configuring the action flow for payment reminder actions

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.

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

Close Deprecation Notice
Contact us