Pegasystems has repositioned Customer Service as a governed workflow engine operating beneath the contact center layer rather than replacing it outright. Infinity 26, which reached general availability in July 2026, reflects a deliberate architectural choice: AWS or another CCaaS vendor owns voice, routing, and digital channels, whilst Pega controls the persistent case, business rules, approvals, and back-office work that extends beyond the conversation. This split addresses a real customer problem—46% of respondents in Pega's February 2026 survey rarely or never achieve successful outcomes from AI-powered service—by ensuring that impressive agent performance doesn't mask unfinished work downstream. The shift from metered token pricing to "Predictable AI" tied to completed cases offers procurement teams a more intelligible billing unit, though the contract definition of what constitutes a billable or resolved case remains critically underspecified in public materials. Buyers need explicit language around reopened work, customer abandonment, human completion, and external model failures before forecasting costs, because a closed workflow and a satisfied customer are not automatically synonymous.
The Model Context Protocol (MCP) integration and new agentic capabilities—agentic assignment, document triage, and Infinity Studio—expand Pega's orchestration strategy without fundamentally changing its competitive positioning. MCP allows authorized third-party agents from Anthropic, Google, OpenAI, and AWS to discover and execute Pega processes, giving enterprises model flexibility whilst keeping governance inside Pega's case layer. This two-way pattern is genuinely useful for regulated industries where specialist models might interpret a dispute document whilst Pega applies account rules and manages approvals, but MCP solves connectivity, not accountability—identity, permissions, auditability, and recovery protocols still demand explicit design. The question for teams already running Agentforce or considering ServiceNow is whether Pega's depth in case management and process automation justifies another strategic platform layer in an already crowded stack, particularly when the strongest customer evidence (Primerica, NHS 24, MetLife Mexico) predates the agentic features Infinity 26 introduces.
Pega's deliberate omissions—native voice, workforce forecasting, quality management, recording—reveal where it believes the value lies: controlling what happens after the customer interaction ends. This positioning works well for large enterprises managing complex, long-running service work like claims, disputes, account changes, and regulated decisions, where the service problem doesn't resolve when the chat closes. For teams primarily seeking all-in-one CCaaS consolidation, however, Pega becomes one more governance layer to license and integrate. The real test isn't how impressive the agent looks in isolation; it's whether Pega's workflow engine removes more friction than it adds when a case reopens, an external model fails, or a customer demands human intervention. Buyers should demand demonstrations of these edge cases and measure durable resolution and repeat contact rates alongside workflow completion metrics, not just invoice neatness.
Pega Customer Service is moving toward a governed workflow layer beneath the contact center, with Infinity 26 adding MCP connectivity, agentic service capabilities, and Predictable AI pricing while leaving core CCaaS functions to partners. Pega’s 2026 roadmap is built around something customers have
Pegasystems Has Put a Price on Agentic Customer Service. Buyers Need the Fine Print CX Today