Salesforce Financial Services United States

Pentagon Federal Credit Union

Customer Service Automation · IT Operations Automation

Manual processes left little time for high-impact relationship building. PenFed knows what it means to serve those who serve.

2 million members migrated off legacy apps
2.8 million members use Agentforce Self-Service as their primary banking interface
55% more efficient collections work
75% of routine IT requests resolved autonomously

Reported impact

Business outcome

PenFed unified more than 600 tools on one Salesforce stack, moved over 2 million members to its self-service banking experience, and uses Agentforce to resolve 75% of routine IT requests while helping collections teams work 55% more efficiently.

  • Customer Experience
  • Productivity Improvement
  • Scalability

Solution

PenFed consolidated more than 600 disconnected tools onto the Agentforce 360 Platform so it could run member service, digital banking, employee support, and collections on one governed stack. Agentforce Financial Services provides the core member-operations layer, while Agentforce Self-Service powers the digital banking experience used by members across web and mobile. The same shared platform also supports internal workflows such as IT service and collections, giving staff consistent data, business rules, and security controls instead of conflicting systems and batch synchronizations. MuleSoft helps connect the surrounding operational landscape, and the unified platform makes it practical to launch targeted AI agents such as Penny for IT support and additional member-facing automations. By using one connected architecture for branches, call centers, mobile, and web experiences, PenFed can move faster, personalize service, and scale agentic workflows without fragmenting its member data again.

Data flow

Shared operational data is managed on the Salesforce Platform, where automation layers use it to run member service, digital banking, collections, and internal IT support on one platform and write the outcome back into the same governed workflow.

Solution architecture

5 components · 3 layers
  1. Ingest
    • MuleSoft Connects external systems and APIs required to run member service, digital banking, collections, and internal IT support on one platform.
  2. Serving
    • Agentforce Self-Service Provides the digital banking and self-service surface that lets users run member service, digital banking, collections, and internal IT support on one platform.
  3. Orchestration
    • Agentforce Financial Services Provides the member-service agent layer and financial-services workflow context that helps teams run member service, digital banking, collections, and internal IT support on one platform.
    • Agentforce Service Automates service-side tasks and responses that help teams run member service, digital banking, collections, and internal IT support on one platform.
    • Salesforce Platform Provides the low-code automation and governance foundation teams use to run member service, digital banking, collections, and internal IT support on one platform.

Architecture clues

  • Agentforce handles internal IT support and collections use cases on top of the same banking data foundation.
  • Member 360 and Employee 360 share the same platform-level business logic and controls.
  • PenFed consolidated more than 600 tools onto a shared Agentforce 360 architecture.

Evidence from the source

2 million members migrated off legacy apps
As they shifted from a military-only focus to an open charter, membership grew quickly — and so did the need for technology that could scale with them.
Founded in 1935 for defense and military communities, they’ve grown into a financial powerhouse with 2.8 million members nationwide.
Manual processes left little time for high-impact relationship building.
More than 600 disconnected tools consolidated
PenFed knows what it means to serve those who serve.
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    6 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Salesforce

    Pentagon Federal Credit Union customer story

    First-party
    https://www.salesforce.com/customer-stories/pentagon-federal-credit-union/
    Source type
    Vendor-published customer story
    Published
    Jan 22, 2026
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

  • Published on source page Jan 22, 2026 · Salesforce · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.