Pega Customer Service Developer study plan
Pega Customer Service Developer · Give each week a clear focus.
8 weeks · About 6 hours per week
Customer Service Implementation
Map the Customer Service application stack (Customer Service, Customer Service for Financial Services, Healthcare, Insurance editions) and list which rulesets and built-in case types each edition ships with
Create a Pega Platform developer instance and configure the Customer Service application with an operator ID, access group, and default portal so you can log in as an agent
Trace the Service case lifecycle end to end in the Case Designer and annotate every stage, process, and step you find
Write a one-page glossary linking each Customer Service term (Service case, Interaction, Account, Contact, Intent, Task) to the class or rule that implements it
Your checkpoint
A diagram of the Service case lifecycle with all stages, processes, and steps, plus a glossary of at least 15 Customer Service terms mapped to their implementing rules
Customer Service Implementation
Configure an Interaction portal layout by adding and removing widgets in the composite and confirm the change survives a portal reload
Explain the relationship between Interaction, Account, Contact, and Intent data objects and show where each is stored
Build a new Intent category with child intents and verify an agent can select it during an interaction
Identify how the Interaction driver propagates context from the customer composite into the Service case
Your checkpoint
A working Interaction portal with one custom Intent category and a written note explaining how context flows from the composite into a created Service case
Customer Service Implementation
Design a data model for Account and Contact extending the built-in classes without breaking out-of-the-box behavior
Configure a data transform and a validate rule that enforce required fields on Contact creation
Build a data page that loads Account records and reference it from a UI control
Test the model by creating an Account and Contact through the agent portal and confirming validation fires
Your checkpoint
A documented Account/Contact data model with a working data page and a validation rule, demonstrated by a test transcript of create-and-validate steps
Customer Service Implementation
Add a custom stage and step to the Service case and configure a service-level agreement with a goal and deadline
Configure routing so a created Service case lands in the correct work queue and is picked up by an agent
Implement a decision table that drives case priority from customer tier
Explain how case locking and optimistic locking behave when two agents open the same Service case
Your checkpoint
A customized Service case with an added stage, an SLA, queue routing, and a priority decision table, plus a short written explanation of locking behavior
Customer Service Implementation
Configure correspondence fragments and a correspondence rule to produce a customer email from a Service case
Build a flow action that captures agent notes and attaches them to the case history
Add a task to the case and verify it appears in the agent's task list
Review how the out-of-the-box Customer Service rulesets are locked and identify the correct pattern for overriding a rule
Your checkpoint
A Service case that sends a templated customer email and creates an agent task, with screenshots of the generated correspondence and the task in the agent's list
Customer Service Implementation
Explain the difference between the Interaction portal and the back-office case manager portal and when each is used
Configure a knowledge article and link it to an Intent so agents see suggested content during an interaction
Set up a report that lists open Service cases by queue and status
Describe how the Customer Service application handles multi-channel intake (phone, email, chat) at a conceptual level
Your checkpoint
A knowledge-linked Intent plus a working report of open Service cases by queue, with a written comparison of the interaction and back-office portals
Customer Service Implementation
Build an end-to-end scenario from customer identification through case resolution and verify every step works in a fresh session
Debug three common configuration failures (broken data page, missing access role, incorrect routing) and document the fix for each
Review guardrail warnings in the application and resolve at least three of them
Practice explaining your build decisions out loud as you would in a design review
Your checkpoint
A complete end-to-end demo scenario that runs cleanly from a fresh login, plus a troubleshooting log of three failures and their fixes
Customer Service Implementation
Consolidate notes into a one-page reference covering case lifecycle, data model, routing, correspondence, and portals
Re-run the end-to-end scenario without notes and time yourself
Identify weak areas from the timed run and re-read only those topics
Restate each major concept in your own words to confirm understanding rather than memorization
Your checkpoint
A one-page personal reference sheet and a clean timed run of the end-to-end scenario completed without consulting notes
Milestones
Week 2: You can log in as an agent, see the Interaction portal with your custom Intent category, and explain in writing how customer context reaches a newly created Service case
Week 4: A Service case you built routes to the right queue, respects an SLA, and sets priority from a decision table; you can explain case locking to another developer
Week 6: Your case sends a templated email, creates an agent task, surfaces linked knowledge for an Intent, and appears in a working queue report
Week 8: You complete the end-to-end scenario from a fresh login without notes and can explain each configuration decision in your own words