Google Cloud Financial Services Malaysia

Hong Leong Bank

Customer Service Automation · Document Processing · Risk Management

Hong Leong Bank needed to replace slow manual banking operations and limited chatbot performance with a secure AI ecosystem that could support dynamic customer support, document-heavy trade operations, sanction screening, and faster software delivery.

30% efficiency gain
3x increase in digital engagement of monthly chat transactions
Accelerate development time by 25%
Handles 67% of customer support queries

Reported impact

Business outcome

Hong Leong Bank increased chatbot accuracy and engagement, sped up document-heavy operations, reduced development time, and created a secure platform for expanding agentic banking services.

  • Customer Experience
  • Productivity Improvement
  • Risk Reduction

Solution

Hong Leong Bank built its AI ecosystem on Google Cloud with Gemini platform as the secure environment for internal and customer-facing agents. The bank runs Gemini as a private instance to minimize data exposure. For customer service, it replaced a static open-source chatbot with Gemini 2.5 Flash in a Retrieval-Augmented Generation architecture, then used the Agent Development Kit to coordinate specialized agents that call backend APIs and retrieve real-time core-banking data for personalized responses and promotions. Document AI handles trade-finance OCR across invoices and shipping forms and supports sanction screening for credit-underwriting teams. Compute Engine, Cloud SQL, and Google Cloud Search support the wider application environment, while Gemini Code Assist improves developer productivity. This gives HLB one platform for conversational banking, document automation, risk controls, and faster software delivery.

Data flow

Customer or employee requests are interpreted by Gemini 2.5 Flash in Gemini platform, which uses ADK-driven agents to call secure backend banking APIs and return real-time answers. Trade-finance and underwriting documents are processed through Document AI, while the wider application environment relies on Compute Engine, Cloud SQL, and search services.

Solution architecture

8 components · 4 layers
  1. Compute
    • Gemini 2.5 Flash Runs the dynamic RAG chatbot that interprets intent and coordinates personalized banking responses.
    • Document AI Processes trade-finance and underwriting documents for OCR, field extraction, and sanction screening.
    • Compute Engine Supports the broader AI and application runtime around the bank's Google Cloud workloads.
  2. Storage
    • Cloud SQL Stores operational data used by the bank's AI ecosystem and surrounding applications.
  3. Serving
    • Google Cloud Search Supplies enterprise search capabilities inside the wider banking solution landscape.
    • Gemini Code Assist Improves developer productivity and reduces development time for DevOps workflows.
  4. Orchestration
    • Gemini platform Provides the secure private AI environment in which Hong Leong Bank deploys its multi-agent banking workloads.
    • Agent Development Kit (ADK) Lets Gemini command specialized agents that call backend APIs and retrieve core-banking data in real time.

Architecture clues

  • ADK drives specialized agents that call backend APIs
  • Document AI processes invoices and shipping forms across more than 200 languages
  • Gemini Code Assist speeds DevOps workflows
  • Gemini runs as a private instance on Gemini platform

Evidence from the source

Document AI to process high-volume documents, such as invoices and shipping forms.
Gemini 2.5 Flash for its dynamic Retrieval-Augmented Generation (RAG)
Gemini Code Assist that speeds time-to-market.
Using the Agent Development Kit (ADK), Gemini commands specialized agents to execute secure calls to HLB's backend APIs
the bank deploys a diverse suite of AI agents on this platform
Transparency Evidence & methodology 90/100 reference value · 79% 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 value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/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
    6 metrics describe measurable impact.
  • Deployment scale5/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • 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
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • 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. Google Cloud

    Hong Leong Bank customer story

    First-party
    https://cloud.google.com/customers/hongleongbank
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Jan 16, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
  • Sitemap last modified Oct 8, 2026 · Google Cloud · Publisher metadata Publisher-reported modification timestamp; not a publication date.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.