Finance8 minutes read

    Lending AI Agents That Verify Loan Applications for a Texas Consumer Lender

    Governed lending AI agents on Azure now verify new loan applications by voice at every branch, so specialists only see authentic, qualified applicants.

    Industry
    Consumer lending
    Engagement
    Consulting, design and build
    Platform
    Microsoft Azure, LiveKit
    First agent live
    Loan application verification
    Loan servicing team at work in a consumer lending call center
    The verification agent takes the first call, so the team handles the cases that need a person.

    The short version

    A Texas consumer lender wanted to find out whether agentic AI could take repetitive calls off its call center and lending teams without putting customer data or compliance at risk. Discovery workshops came first, then a test of the market for packaged tools, then custom lending AI agents built on Azure. The first one, a voice agent that verifies new loan applications, is in production across all branches.

    A lender with a strong core system and a new question

    The client is a consumer lending company that has offered personal, credit starter and signature loans since 1968, including to people from underserved communities. Beyond its home state of Texas, it runs service centers in Oklahoma, Virginia and Missouri.

    It already had a robust proprietary loan management system for core processing and servicing. What it lacked was a safe way to use large language models and agentic AI to push efficiency and profitability further. The company had worked with our lending engineering team for over five years, so it asked the people who already knew its systems to validate the idea, plan the agents and deploy them inside live workflows.

    Discovery: picking the use cases worth automating

    Consultants ran focused workshops with the lender's stakeholders to map operational needs, expectations for the agents and the constraints on AI implementation.

    For each high-impact use case, the team delivered an agent concept, a detailed software requirements specification and a tailored set of performance, quality and user acceptance metrics. Those documents gave the lender a clear basis for choosing what to build first, and gave the engineers a fixed yardstick for testing later.

    Three agents the lender chose to launch

    The agents were specified to switch instantly between English and Spanish during calls, so multilingual customers get consistent communication. Verification is live; the other two follow in later projects.

    • 01

      Loan application verification (live)

      Picks up applications that passed initial credit bureau checks and calls the applicant on a consented voice call. It verifies identity with a Social Security number and date of birth and confirms borrowing intent. Only authentic, qualified applications reach human specialists.

    • 02

      Debt collection (in design)

      Planned to call debtors, walk them through repayment options and propose alternative terms on the fly within FDCPA rules. It would collect approvals for saved payment methods, take new card and bank details, and capture promises to pay and renewal confirmations, while the backend triggers real-time gateway payments and ACH direct debits.

    • 03

      Incoming call handling (planned)

      Intended to triage inbound calls, work out the intent of each request and route it to the right loan servicing specialist. Automated call dispositioning would cut wait times and free servicing capacity.

    Buy and customize, or build task-specific agents

    The lender first planned to adapt ready-made agentic AI tools. A shortlist of the most suitable vendor offerings came first, then a feasibility study before anyone wrote code.

    OptionFeasibility findingImpact
    Customize packaged agentic AI toolsMost commercial agentic AI products were not ready for enterprise-grade rollout.Extensive rework needed to handle the lender's real lending processes.
    Build custom agents on cloud AI services and commercial LLMsRecommendedCheaper than customizing packaged tools, with comparable release timelines.More control over agentic workflows and solution scaling.

    The lender chose the custom path. The project manager proposed building the agents one at a time, each as a separate project with its own work breakdown, team plan, estimates and risk steps. That limits scope creep, keeps the same team on the whole initiative and lets later agents reuse tested components with minimal QA overhead.

    How the lending AI agents were designed

    The architects built the verification agent from modular, event-driven components and used managed cloud services wherever possible to keep costly custom code down. LiveKit Cloud configures the calls, the LiveKit Agent SDK holds the agent logic, and Azure Container Apps runs the workflows on Azure, where the lender's systems already lived.

    • 01

      Cost-effective scaling

      Workflows scale horizontally on demand, based on resource use and active sessions. A call dispatch service with queue-based load leveling and configurable session limits prevents overprovisioning. The team compared LLM hosting options such as Azure OpenAI and OpenAI Realtime, then picked configurations that balance tokens, concurrency limits and pricing tiers.

    • 02

      Low latency

      Voice calls need near-real-time responses. Real-time audio streaming through LiveKit was chosen for low-latency concurrent audio between agent and customer, and its streaming APIs for agent and LLM interaction cut integration work and help keep conversations flowing under heavy load.

    • 03

      Interoperability

      The agent talks to the lender's application platform and outside services through standardized APIs. New application sources, customer channels or AI models plug in with minimal changes to the core.

    • 04

      Agent governance

      The agent acts only through structured function calls and predefined business logic, so every action is deterministic, auditable and aligned with business rules. Control modules handle instructions, action tracking and approval, and full interaction tracing lets the team reconstruct any decision.

    Security and compliance controls built in

    In lending, a voice agent handles identity data on every call. These controls were part of the design, not added at the end.

    • Zero-trust principles, with WebRTC, DTLS and SRTP so lending data and audio streams stay encrypted in transit and at rest.
    • Sensitive customer data encrypted again before it enters the communication layer and decrypted only inside isolated agent runtimes, never exposed to external services or LLM vendors.
    • A dedicated Azure Virtual Network with private endpoints to block public exposure and unauthorized access.
    • Region-specific Azure deployments that keep the data residency and processing boundaries GLBA requires.
    • Logging and recording pipelines that check consent, call timing and intent identification against internal policies and TCPA rules.
    • Observability tools that track how the agent handles personal and financial data under GLBA.
    • Secure identity management and encryption aligned with GLBA data protection standards.

    From build to branch rollout

    1. 1

      Build and integrate

      Engineers connected the custom modules and third-party services and integrated the agent with the lender's website, the main source of applications. The admin panel gained agent control dashboards where specialists track verification status and resolve open cases by hand.

    2. 2

      Functional and integration testing

      QA confirmed the agent reads user input correctly, calls back-end services and follows its interaction logic, then validated the links between the agent, telephony services, LLMs and the website.

    3. 3

      End-to-end call simulation

      Full verification calls were simulated to check conversation flow, response accuracy, latency and customer experience.

    4. 4

      Edge and failure scenarios

      Testers fed the agent ambiguous or inconsistent answers, interrupted calls, unexpected inputs, API timeouts and slow model responses. It had to recover without breaking the conversation or exposing sensitive data.

    5. 5

      Load and voice testing

      Load tests on varying data volumes measured scalability, latency and concurrent call capacity. Dedicated voice tests checked speech quality, responsiveness and coherence on live calls.

    6. 6

      Acceptance, pilot and rollout

      In user acceptance testing the agent handled verification accurately and moved data cleanly across systems. A pilot at one branch followed, and as of April 2026 the agent runs in production at all branches.

    Branch lending desk where lending AI agents hand verified applications to loan specialists
    Specialists now start from applications the agent has already verified.

    The numbers behind the project

    Customers served by the lender
    2.5 million+
    Across its history since its founding.
    Offices in Texas
    50+
    The lender's footprint in its home state.
    Audio latency design target
    Sub-250 ms
    What LiveKit real-time streaming was chosen to enable between agent and caller.
    Projected rise in debt recovery
    Up to 20%
    Our estimate for the planned collection agent, alongside lower collection costs.

    Throughout the past five years, the team has always brought structure, technical insight, and a strong understanding of lending operations to our IT initiatives. Seeing that they approached AI engineering the same way gave us confidence from the start. We knew our agents would be secure, well-governed, and aligned with the way we work without overspending. The first live agent fit naturally into our application review process and brought results right away.

    Vice President of Operations, Texas consumer lender

    Results and lessons for your own rollout

    Early feedback from the pilot branch was clear: the agent reduced manual workload and made application verification more consistent. Automated checks at an early stage also tighten risk control, because weak or fake applications stop before a specialist spends time on them. The design work for the debt collection agent is now under way, using the same architecture principles.

    If you are planning lending AI agents of your own, three lessons stand out. Test packaged tools against your real processes before you commit. Ship one narrow agent at a time with the same team. And make every action auditable from day one, with tracing on open standards such as OpenTelemetry.

    LiveKit's agent framework offers SDKs in Python and Node.js, so if you need more capacity for agent logic and integrations, you can hire Python developers or Node.js developers. You can also browse more case studies, or get started with a scoping workshop.

    Questions buyers ask

    Why build custom lending AI agents instead of customizing a packaged tool?

    The feasibility study found most commercial agentic AI products were not ready for enterprise rollout and needed extensive rework for real lending processes. Custom task-specific agents on cloud AI services and commercial LLMs were cheaper, had comparable timelines and gave more control over workflows and scaling.

    How is customer data kept away from LLM vendors?

    Sensitive data is encrypted again before it enters the communication layer and decrypted only inside isolated agent runtimes. The agent runs in a dedicated Azure Virtual Network with private endpoints, so the data stays within controlled components.

    Which regulations did the design account for?

    GLBA for personal and financial data handling and residency, TCPA for customer outreach such as consent and call timing, and FDCPA for the planned debt collection agent.

    How was the verification agent rolled out?

    After functional, integration, end-to-end, edge case, load and voice testing, the lender ran user acceptance testing, then a pilot at one branch. Full production at all branches followed by April 2026.

    Can the agents handle Spanish-speaking customers?

    That is part of the design. The agents were specified to switch instantly between English and Spanish during calls. The verification agent is the first in production; the debt collection and call handling agents are still to be built.

    Technology stack

    Voice and agent framework

    • LiveKit Cloud
    • LiveKit Agent SDK
    • WebRTC

    AI models

    • Azure OpenAI
    • OpenAI Realtime API

    Runtime and scaling

    • Azure Container Apps
    • KEDA
    • Azure Service Bus

    Security and networking

    • Azure Key Vault
    • Azure Virtual Network
    • Azure Private Endpoints

    Data

    • PostgreSQL
    • Redis

    Observability

    • OpenTelemetry
    • Azure Application Insights
    View all
    Enterprise AI Platform with Secure Multi-Model LLM Access
    Artificial Intelligence

    Enterprise AI Platform with Secure Multi-Model LLM Access

    A secure enterprise platform that gives organizations controlled access to GPT-4, GPT-4O, and Perplexity through a single interface. A local screening model checks every prompt before it reaches external LLMs, with role-based access, custom system prompts per department, and a complete audit trail.

    5 minutes readRead more →

    Planning something similar?

    Tell us where the work is stuck today. In one call you get a senior engineer's view of the approach, the risks worth planning for, and a realistic first release.