What you need
Data sources
- Loan origination system — application records, applicant demographics, requested amounts, and decision history
- Credit bureau API — credit scores, trade lines, delinquency history, and inquiries
- Core banking system — existing account balances, deposit history, and relationship tenure
Knowledge spaces
- Underwriting policy manual — upload your current credit policy, including approval thresholds by product type and risk tier
- Regulatory guidelines — fair lending requirements, disclosure rules, and documentation checklists
| Component | Name | Definition |
|---|---|---|
| Object | Loan Application | Maps to the applications table in the loan origination system. Represents a single borrower request |
| Object | Customer | Maps to customers in the core banking system. Represents an individual or business entity |
| Metric | Approval Rate | Count of approved applications / total applications, segmented by product and branch |
| Metric | Average Processing Time | Mean elapsed days from submission to decision across all applications |
| Dimension | Product Type | Categorizes applications by mortgage, personal, auto, or commercial |
| Dimension | Risk Tier | Groups applications into low, medium, high, and very-high risk based on credit score bands |
Agent setup
Create the agent
Go to Agent Space → New agent.
| Field | Value |
|---|---|
| Name | Loan Intake Analyst |
| Role | Loan Application Reviewer |
| Goal | Review incoming loan applications, verify completeness, assess preliminary risk, and route to the appropriate underwriting queue |
Set the description
You are a detail-oriented loan intake analyst. You evaluate each application against underwriting policies, flag missing documents or data discrepancies, and classify risk tier using credit bureau data and internal account history. You prioritize accuracy and regulatory compliance over speed, and you never approve or deny an application — you prepare it for human decision-making.
Scope data access
Grant access to:
- Loan origination system (applications table, decision history)
- Credit bureau API (scores, trade lines)
- Core banking system (customer accounts, deposit history)
- Underwriting policy manual knowledge space
- Regulatory guidelines knowledge space
- Loan Application and Customer objects, Approval Rate metric
Add skills
Application completeness check
Application completeness check
Trigger: User asks the agent to review a specific application or batch of applications.
- Retrieve the application record from the loan origination system.
- Compare submitted fields against the required-documents checklist from the underwriting policy manual.
- Flag any missing or inconsistent fields (income verification, employment letter, identification).
- Pull the applicant’s credit score and trade line summary from the credit bureau API.
- Look up the applicant’s existing account relationship in the core banking system.
- Generate a completeness summary with a pass/fail status and a list of items needing follow-up.
Risk tier classification
Risk tier classification
Trigger: User asks the agent to classify an application by risk level.
- Retrieve the applicant’s credit score, debt-to-income ratio, and trade line count from bureau data.
- Pull deposit history and average balance from the core banking system.
- Match the product type to the corresponding risk-tier thresholds in the underwriting policy manual.
- Assign a risk tier (low, medium, high, or very-high) based on the combined criteria.
- Return a structured summary with the assigned tier, contributing factors, and the applicable policy section reference.
Routing recommendation
Routing recommendation
Trigger: User asks the agent where to route an application.
- Check the application’s completeness status and risk tier from previous assessments.
- Look up the routing rules in the underwriting policy manual for the given product type and risk tier.
- Identify the correct underwriting queue (auto-approve, standard review, senior review, or decline queue).
- Flag any regulatory holds (e.g., fair lending review triggers).
- Return the recommended queue, expected SLA, and any special handling instructions.
Automation
Playbook: New application intake router
Set the trigger
Set the trigger to Event — New record on the
applications table in the loan origination system. The playbook fires each time a new application is submitted.Build the workflow
The workflow performs a multi-step evaluation of each new application:
- Query the application record and join it with the applicant’s credit bureau data and core banking profile.
- Condition — check whether all required documents are present. If documents are missing, branch to a notification step that emails the applicant with a list of outstanding items.
- Condition — evaluate risk tier. If the risk tier is “low” and all documents are present, route to the auto-approve queue. Otherwise, route to the appropriate review queue.
- Action — update the application status in the loan origination system with the assigned queue and tier.
- Delivery — send a Slack notification to the underwriting channel with the application ID, applicant name, product type, risk tier, and assigned queue.
Configure delivery
- Slack — send to the
#loan-underwritingchannel with application summary - Email — notify the assigned underwriter with a detailed intake report
- Email to applicant — send a confirmation with application ID and expected timeline
What’s next
Customer credit scoring
Build a composite credit scoring model that feeds directly into your loan application workflow.
All Finance & Banking use cases
See the full list.