Safely manage your Zendesk from the AI assistant you already use, via the Deltastring MCP. Beacon configuration platform
← Back to news

Yorkshire Building Society touts customer service gains with AI agents

Yorkshire Building Society's deployment of three AI agents—Penelope, Sam, and Alf—demonstrates a pragmatic approach to agent augmentation within a heavily regulated sector. Rather than replacing human agents, YBS positioned these tools as administrative accelerators: Sam summarizes complaints (saving seven minutes per use), Alf retrieves policies and case history, and Penelope drafts responses (saving up to 26 minutes on complex cases). The foundation for this rollout was deliberate infrastructure work—Microsoft Fabric for data architecture, Purview for governance, and Dynamics 365 Contact Centre-as-a-Service to consolidate fragmented systems. YBS also piloted internal AI agents for risk and control testing, reporting 40% efficiency gains. The narrative here is straightforward: financial services organisations face acute friction from regulatory compliance requirements, and AI agents that reduce context-switching and administrative overhead create measurable time savings that redirect agent capacity toward actual customer interaction.

The implications for CX teams are twofold. First, this validates a specific use case: AI agents excel at pre-work and post-work tasks—summarization, retrieval, drafting—rather than direct customer interaction. For teams already running Dynamics 365 or similar unified platforms, the question becomes whether your current stack can surface the contextual intelligence these agents require, or whether you're still forcing agents to navigate multiple systems. Second, YBS's emphasis on human oversight and the explicit commitment to keeping humans available signals that the competitive advantage lies not in automation depth but in automation *placement*—knowing where to insert AI to eliminate friction without removing the human element that financial services customers expect. The 26-minute savings on complex complaints is meaningful, but only if those minutes translate into better member outcomes rather than simply higher throughput. For support leaders evaluating similar deployments, the critical metric isn't time saved per interaction; it's whether your team's capacity reallocation actually improves resolution quality or member satisfaction, or whether you're simply compressing the same work into shorter cycles.