Agentic Loan Applications
This solution helps a bank take a personal loan from first conversation to funded account.
Customers apply in Mobile Banking, a conversation agent collects details and documents, Lending Console lets a loan officer review and intervene, and Banking Sync Services bootstraps data, resets demo customers, and creates offers.
Pre-requirements
To install the Agentic Loan Applications solution, you must first create the Trial AI Model TrialClaudeHaiku4_5. The solution’s agents use this model by default, so it must be available before you can install the solution from Forge.
After installation, you can configure the agents to use your preferred AI model. Check the documentation for our recommendations on the most accurate model for each agent role.
Documentation
Full step-by-step documentation is in the documentation site.
Download the zip, extract it, and open index.html in a browser. Start with the Getting Started group.
Getting Started
After you install from Forge, complete these steps so the apps are ready to run. Details are in Getting Started in the documentation site.
Open the three main applications. Replace [your-tenant-host]with your tenant hostname. Each URL should show a login page.
Mobile Banking: [your-tenant-host]/CloneofMobileBanking
Lending Console: [your-tenant-host]/CloneofLendingConsole/
Banking Sync Services: [your-tenant-host]/CloneofBankingSyncServices
Copy the host from any of those URLs (it should end in .app). In ODC Portal, open Solutions Common Services and set DevelopmentDomainto that hostname. Refresh the three apps. Each login page should show a demo-user button:
Mobile Banking — Log in as Matthew Sheldon
Lending Console — Log in as Eddie Riedel (Officer)
Banking Sync Services — Log in as Lydia Miller (Setup Control) If a button is missing, wait a moment and refresh. The setting can take a short time to propagate.
In Portal, open Clone of Banking Sync Services and run the SyncData timer to import bootstrap data. Use SyncDataRecreate to reset and import again. After SyncData runs, Matthew should have 2 accounts, Eddie should have 9 tasks, and Lydia’s dashboard should show Matthew Sheldon.
Optional: change each banking agent from the trial model TrialClaudeHaiku4_5 to the recommended production model. See Banking Agents — Model recommendations in the documentation site.
When those steps are done, you can test the application.
Test Loan Origination Flow
The documentation site includes Test Loan Origination Flow, next to Getting Started. It is a happy-path scenario: a customer accepts a pre-approved offer and continues until they receive the loan. The guide walks through Banking Sync Services (restart the customer with one offer), Mobile Banking (chat, document upload, PIN 1234), Lending Console (application in Referred, approve offer options), and back to Mobile Banking (agree, submit, and see a $60,000.00 loan account). Sample driver’s license, pay stub, and proof-of-address files are linked from that page.
Make it your own
The same Getting Started group has Make it your own. That page lists settings, defaults, and customization points by module so you can adapt the solution to your bank.
Typical customization points include:
Workflow — orchestration, task ownership, timing, and exception paths in Lending Application Workflow
Agents — prompts, guardrails, tools, and models for conversation, policy, document, and fraud agents
Core services — loan, account, KYC, and shared customer behavior behind public service actions
Product and policy — eligibility, pricing, and disclosures (prefer an external rules engine for production)
Integrations — replace mock credit, regulatory, and core-banking Integration Services with your providers
Data sync — wire retrieval actions to real APIs while Banking Sync Services keeps checkpoints and run logs
Apps — Mobile Banking and Lending Console experience, without moving business rules into the UI
Use Make it your own together with the architecture and layer sections in the documentation site when you customize.