Appearance
Application detail — use cases
Detailed scenarios for the Docs, Email, Data, Integration, Transactions, Tasks, and Activity tabs. Examples use fictional lender Riverstone Credit and applicant Alex Morgan (application 10844, Personal Loan).
1. Chase missing pay stubs (underwriter)
Persona: Priya, Underwriter
Goal: Applicant submitted the app but pay stubs are missing.
Steps:
- Open application 10844 → Docs tab.
- Read 1 of 4 Documents Received.
- Expand UPLOADED DOCUMENTS — Pay Stub shows Pending.
- Click Request Docs.
- In the composer, select template Document Request – Standard.
- In Request Docs multi-select, choose Pay Stub and Bank Statement.
- Click Send.
- Switch to Email tab — confirm new row Queued then Delivered.
- Click Update Status in the header → Doc Requested (or Processing if your policy uses that while waiting) → confirm in the modal.
Outcome: Applicant receives upload links; Pay Stub moves to Requested then Review when uploaded.
2. Review overnight document queue (reviewer)
Persona: Marcus, Reviewer
Goal: Clear all documents waiting for review before noon.
Steps:
- Docs tab — note Start Review badge shows 3.
- Click Start Review — preview opens on newest Review document.
- For each document: verify image/PDF → Approve with optional note, or Reject with required reason.
- Use Skip to defer a blurry upload and return later.
- When queue empty, modal closes automatically.
- Spot-check Activity tab — document_status_update entries with your user name.
Outcome: All uploads Approved or Rejected; underwriting can proceed.
3. Generate and track loan agreement (closer)
Persona: Elena, Manager
Goal: Generate contract after approval.
Steps:
- Docs → CONTRACTS section → Generate.
- Choose template Personal Loan Agreement v4.
- Complete Generate Document modal (fields pre-filled from application).
- New row appears — status Not Signed until applicant signs.
- After e-sign webhook, refresh tab — status Signed, count in header increases.
- Download signed PDF from row Download action for funding file.
Outcome: Executed contract stored under CONTRACTS.
4. CSR answers “Did you email me?” (support)
Persona: Jordan, CSR
Goal: Confirm whether a request email was sent Tuesday.
Steps:
- Open application → Email tab.
- Search... → type
document. - Locate row Tue 5/20 — Delivered, subject Documents needed for your application.
- Optional: click row action icon to open composer with that message context for a follow-up Send.
- If applicant still confused, check Activity for document_status_update and view events same day.
Outcome: CSR gives accurate callback answer without escalating.
5. Fix wrong employer variable after typo (analyst)
Persona: Sam, Analyst
Goal: Correct User Input employer name before re-decision.
Steps:
- Data tab → Search
employer. - Find variable
employer_name— Source User Input, wrong value. - Click Action pencil → Edit variable modal.
- Enter correct name → Update — toast Variable updated.
- Application tab → re-run underwriting per your policy.
- Integration tab optional — confirm no new errors from providers.
Outcome: Model data matches application form; decision recalculated.
6. Debug failed credit pull (analyst)
Persona: Sam, Analyst
Goal: Understand why bureau score is missing.
Steps:
- Data tab — filter Source → Integration → sub-filter Equifax.
- Note score variable empty or stale.
- Integration tab — sort Timestamp descending.
- Find Equifax row with Status error (red dot) → View.
- Read response body in side panel — note HTTP 503 and error JSON.
- Copy payload for ticket to engineering; retry pull from workflow if available.
Outcome: Root cause documented; applicant status set Pending until retry succeeds.
7. Tag bank deposits for income analysis (underwriter)
Persona: Priya, Underwriter
Goal: Mark payroll deposits as Income 1 for DTI worksheet.
Steps:
- Transactions tab — confirm account Checking ••4521 selected ( Primary badge ).
- Set Date range to last 90 days.
- In To/From search, filter
PAYROLL. - For each credit row → click Add Tag → Income 1 → enter note
Verified employer ACME. - For two similar rows, use row checkboxes → Bulk edit → tag Income 1 once with shared note.
- Click Summary → Income tab to validate totals.
- If wrong account linked, select other account → Mark Primary (analyst/admin).
Outcome: Tagged transactions feed summary; file ready for decision.
8. Coordinate internal follow-ups (manager)
Persona: Elena, Manager
Goal: Assign verifications to two team members with due dates.
Steps:
- Tasks tab → Task.
- Create:
Call employer on listed number— due Tomorrow — assign Priya → Create Task. - Create:
Verify address via utility bill— due end of week — assign Marcus. - Marcus completes his item — checks checkbox → Task marked complete (moves to Completed group).
- Elena monitors open work in Today / This Week sections during standup.
- Activity shows assignments if your tenant logs app_assign events.
Outcome: Work visible on application without external task tool.
9. Auditor sample for compliance (auditor)
Persona: Quinn, Auditor
Goal: Read-only review of consent and communications.
Steps:
- Open funded application → Docs → CONSENT FORMS — download consent PDF (Download only; no Request Docs).
- Email tab — verify decision and adverse action emails Delivered (no Send Email button).
- Activity — expand This month — confirm consent and step_change events.
- Data tab — view income variables; no pencil icons.
- Export screenshots for exam workbook.
Outcome: Evidence chain without modifying records.
10. Bulk download file for investor package (operations)
Persona: Ops specialist (Admin)
Goal: ZIP all approved uploads for external sale.
Steps:
- Docs — expand all three sections.
- Header checkbox select all (only rows with files).
- Download — wait for Preparing... and ZIP download.
- Cross-check count against 3 of 3 Documents Received.
- Upload ZIP to investor portal outside LendAPI.
Outcome: Single archive without clicking each Download icon.
Related topics
- Workflows — quick decision tree
- Documents — button reference
- Transactions and tasks — tagging reference