Pega Customer Service Developer case studies
Pega Customer Service Developer · Put your knowledge to work in context.
The Certified Pega Customer Service Developer credential is Pega's certification for System Architects who want to learn how to implement a Pega Customer Service application. According to Pega Academy's certifications page, the certification is aligned to the Customer Service Implementation '25 mission and is assessed by the Infinity '25 certification exam. Pega positions the credential under its Customer Service Developer certification track, described on that page as helping candidates "Lead the way in customer service innovation." The exam is intended for technical staff - System Architects, as Pega names the role - who build and configure Customer Service applications on Pega Platform rather than for business-only or decisioning roles; Pega's other tracks cover Business Architect, System Architect, Robotics System Architect, Data Scientist, and Decisioning Consultant audiences. Pega's certifications page lists a mission and a certification exam version for this credential but does not publish exam duration, question count, passing score, fee, retake rules, or validity period, so confirm those details on Pega Academy before booking. The Pega Customer Service Developer case studies are 5 cases and about 2,828 words.
1Interaction Portal Composite Latency and Stale Customer Data
A Pega Customer Service 23.1 implementation serves 350 agents in a single interaction portal. The customer composite has six tabs: Summary, Cases, Billing, Orders, Interactions, and Documents.
507 words, about 3 min2VIP Service Cases Breaching SLA in a Shared Work Queue
A financial-services CS application has 140 agents. Cases are created as Service cases with a Customer tier property: Standard, Gold, Platinum.
643 words, about 3 min3Upgrade Risk from Directly Modified PegaCS Rules
A telecom company runs Pega Customer Service 8.8 on Pega Platform 8.8. Over four years, the team customized the interaction portal by saving 380 PegaCS rules into the application ruleset TelcoCS-Work and editing them directly.
577 words, about 3 min4Suggested Responses Ignored in Email Channel
A retailer handles 2,100 customer emails per day in Pega Customer Service 23.1. The email case type uses the standard email composer with a suggested responses panel.
531 words, about 3 min5Screen Pop Identifies the Wrong Customer on Inbound Calls
A health insurer runs Pega Customer Service 23.1 with a CTI integration from a cloud contact center. On an inbound call, the CTI CallOffered event passes the calling number to the interaction portal.
570 words, about 3 min