Skip to main content


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

Schedule Payment Plan case stages and steps

Updated on December 3, 2021

The Schedule Payment Plan case is built using the generic case template. The following figure shows the stages and steps in the case, from eligibility to resolution.

Pega Customer Service Implementation Guide

Schedule Payment Plan case stages and steps
Shows the stages and steps of the Schedule Payment Plan case

Stages and steps

  1. Eligibility stage – Determines whether the case can run or additional verification is required. By default, this stage is disabled. For more information about the case template and how to enable this stage, see Configuring case processing options.
  2. Intake stage – During this stage, the appropriate payment plan and payment method are selected for repayment of the dues.
  3. Process request stage – During this stage, the Make Payment cases are created according to the payment plan and method selected. The case then waits for the payment cases to be resolved successfully.
  4. Resolve – The case is resolved when all child cases (scheduled payment cases) are resolved.

Personas

CSR - Customer Service Representative who uses the assisted channels to schedule payment plans.

Data objects

Account – The customer account that is due for payment.

The project team can modify and extend most areas of this case in App Studio, making it easier to deploy.

Tags

Pega Customer Service 8.7 Pega Customer Service for Communications 8.7 Pega Customer Service for Financial Services 8.7 Pega Customer Service for Healthcare 8.7 Pega Customer Service for Insurance 8.7

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