Pega Collections architecture

The following diagram shows high level overview of Pega Collections solution architecture

Unified user experience

Customer Service provides the workflow-based case management capabilities that enable organizations to execute Collections operations consistently across channels. It manages Collections Cases, agent interactions, payment arrangements, exceptions, and recovery processes. Collections supports multiple channels, including agent desktops, web applications, self-service portals, mobile apps, and third-party front ends such as Salesforce. Channel independence is achieved through DX APIs. 

Decisioning

Customer Decision Hub (CDH) is a decisioning tool that sits in the middle of all your channels and helps you optimize your contact strategies and generate personalized offers for your customers. CDH brings cross channel consistency, and effectiveness through targeted messaging. CDH uses business rules to align relevant actions with qualifying customers and then prioritizes those actions based on customer’s likelihood of accepting an offer, the context of the interaction, and financial value the action brings to the business. 

Data

The data layer in Pega Collections provides a unified view of customer, account, payment, and collections information by combining data from Pega and external enterprise systems. Rather than replicating all operational data, Pega uses live data to access information from systems of record such as billing platforms, loan servicing systems, payment systems, CRMs, and data warehouses in real time. This ensures that collectors and decisioning strategies work with current and consistent information. 

The data layer supports both workflow execution and AI-driven decisioning by supplying customer profiles, account balances, delinquency status, payment history, promises-to-pay, and interaction history. This information enables Customer Service to manage collections cases while allowing Customer Decision Hub to determine the most appropriate treatment strategy, channel, and next-best action.

Integration

The Integration layer connects Pega Collections with enterprise systems such as billing platforms, loan servicing systems, payment processors, CRMs, data warehouses, and external communication channels. It enables the seamless exchange of customer, account, payment, and collections data, ensuring that workflows and decisions are based on current information rather than isolated copies of data. 

Through APIs and enterprise integration technologies, Pega Collections can retrieve account details, process payments, update customer records, trigger communications, and synchronize case outcomes across systems. This allows Customer Service workflows and Customer Decision Hub strategies to operate as part of a connected business ecosystem rather than a standalone collections application. 

Workflow 

The workflow in Pega Collections is powered by Pega Customer Service and orchestrates the end-to-end collection process. It manages Collections Cases from initiation through resolution, guiding collectors through activities such as customer outreach, promises-to-pay, payment plans, hardship handling, settlements, and recovery actions. 

Workflows provide structured case management, business rules, task routing, approvals, SLAs, and auditability, ensuring that Collections activities are executed consistently and in compliance with organizational policies.