Agentforce in nCino: close the document loop without a borrower portal
Before a commercial loan can advance past underwriting in nCino, the lender needs documents from the borrower or guarantor: two to three years of financial statements, a current certificate of insurance, an environmental questionnaire, and whatever entity documents the credit policy requires. The checklist is in the system. The credit policy is clear.
The problem is the last mile.
The loan officer emails the borrower. The borrower doesn't respond. The officer follows up. The document arrives a week late, or it doesn't arrive at all. The loan stalls in underwriting while the officer manually tracks outstanding items across 30 or 40 active files.
This is not a staffing problem. It's a loop that was never closed.
nCino runs on Salesforce. That means Agentforce can be deployed in the same org — if your institution has the appropriate Salesforce edition, Agentforce licensing, and Einstein trust settings enabled. The document follow-up loop is one of the clearest first use cases once those prerequisites are in place.
Before you build: verify your nCino data model
nCino object API names vary by package version and org configuration. Do not copy object names from a blog post into production Flows without verifying them in your org.
Open Setup → Object Manager and confirm the objects your Document Checklist UI actually writes to. In most nCino deployments you'll find:
Loan record: LLC_BI__Loan__c (legacy package prefix) or nCino__Loan__c (newer naming)
Document / requirement line items: LLC_BI__Requirement__c or nCino__Requirement__c
Borrower / guarantor contact: Contact, often related via nCino__Role__c or loan lookup fields
Covenant / insurance tracking: nCino__Covenant__c (for renewal use cases)
The nCino UI label "Document Checklist" does not always map to an object literally named Document_Checklist__c. Requirement objects are the more common underlying record type for outstanding document items on a loan.
Status picklist values are also org-configurable. Filter your query to whatever values represent open or outstanding in your org — commonly something like Open or Requested — rather than assuming fixed values like Pending or Received.
The standard workflow and where it breaks
When a loan application is created in nCino, the system generates a Loan record and, based on your product configuration and document rules, a set of requirement or checklist items representing everything needed before the loan can advance.
The checklist is machine-generated. The collection is manual.
A loan officer might have a task to gather documents, but the actual outreach — the email, the follow-up, the confirmation that something was received, the update to the requirement record — runs through the officer's inbox. There's no closed loop. There's no reliable record of when the borrower was contacted, what they were asked for, or whether they responded. The nCino record stays stale until someone updates it by hand.
That's the gap Agentforce fills.
The build: one agent, one subagent, three Autolaunched Flows
Open App Launcher → Agentforce Studio → Agents and create a new agent. Add a subagent (Salesforce renamed "topics" to subagents in 2026) scoped in plain language:
"This agent manages outstanding document requests on nCino Loan records. It contacts borrowers and guarantors to request missing items, validates responses, and updates the loan's document requirements in Salesforce."
That definition is not decoration — it's how the reasoning engine routes work to this subagent versus escalating to a human. Keep it narrow.
The subagent needs three actions, each backed by an Autolaunched Flow — not a Screen Flow. Agent actions run in the background without a user interface, and Screen Flows require an interactive session.
Action 1 — Query the loan and outstanding documents
The Flow takes a loan ID or borrower email as input. It queries the Loan object to confirm the file is in the right stage, then queries related open requirement records filtered to your org's outstanding status values. It returns the list of outstanding items and their due dates to the agent.
Register this Flow as an Agentforce Action in Agentforce Studio. Write the action description the way a person would describe the task: "Look up the outstanding document requirements for a given nCino loan."
Best practice: Include a guard condition that exits early if the loan stage is wrong, the borrower contact is missing, or no open requirements exist — rather than letting the agent proceed with incomplete data.
Action 2 — Send the outbound request
The Flow takes the borrower contact and the list of outstanding documents as input. Start with email — it works in every org via standard Flow email actions or Send Email invocable actions.
The email lists the specific documents needed, the due date, and one clear call to action — for example, a secure upload link or instructions to reply with confirmation. No borrower portal login required.
SMS is optional and requires additional setup (Messaging channel, Digital Engagement, compliance review). Do not assume SMS is available out of the box.
The action description: "Contact the borrower or guarantor to request outstanding loan documents."
Best practice: Log an activity on the loan record when outreach is sent. That creates the audit trail loan ops and compliance teams expect — something manual email follow-up often lacks.
Action 3 — Close the requirement on response (with human verification)
When the borrower responds through your configured Agentforce channel, this Flow validates the response, updates the requirement record to your org's received or in-review status, logs an activity on the Loan record, and creates a task for the loan officer to verify the actual document before the item is formally cleared.
The agent marks the item as submitted — not approved. The loan officer still reviews the document against credit policy. That human-in-the-loop step is non-negotiable in regulated lending.
The loan officer's job changes: instead of chasing documents, they review what the agent has already collected. The nCino record stays current. The audit trail is complete.
Best practice: Inbound response handling is custom logic in your Flow or messaging channel — it is not automatic. Design explicitly for how replies arrive in your org (email-to-case, messaging session, secure upload webhook) and test in sandbox before production.
What the loan officer sees
Nothing changes about the loan officer's view of nCino. The Loan record is updated. Requirement items move to received or in-review status. There's a logged activity showing when the agent contacted the borrower and what they were asked for.
If the borrower doesn't respond within a set window — configurable in the Flow — the agent escalates to the loan officer with a task. The human stays in the loop on exceptions. The routine follow-up never reaches their inbox.
A single loan officer managing 30 to 50 active files can lose days per month to document follow-up alone. The agent doesn't replace the relationship — it handles the paperwork friction that gets in the way of it.
Guardrails and best practices before you go live
Subagent scope (what the agent will handle): Keep the subagent definition narrow. If it receives a question about loan terms, interest rates, or anything outside document collection, it should hand off to a human or decline. Configure this in the subagent settings in Agentforce Studio.
Escalation path: Every agent needs a defined fallback. If an action fails — the Flow errors, the contact record is missing, the requirement doesn't exist — it should create a task for the loan officer and stop. Never let the agent retry silently.
Sandbox first: Build and test the full loop in a Salesforce sandbox with realistic nCino test data before promoting to production. Use Agentforce Studio's conversation preview to validate routing and escalation behavior.
Regulated lending constraints: The agent collects and tracks — it does not approve documents, make credit decisions, or bypass your credit policy. Document verification stays with the loan officer. All outreach and status changes should be logged as activities for audit purposes.
Compliance review: Run the design past your compliance, legal, and information security teams before borrower-facing automation goes live — especially if SMS or AI-generated message content is involved.
Where the same pattern extends in nCino
The three-action structure — query the record, send outbound, close on response — applies anywhere nCino has a requirement or checklist object and an external party who needs to respond:
Annual review cycles. Commercial lending relationships typically require annual financial statement updates. The same agent handles outreach to existing borrowers when their review window opens, tracks what's been submitted, and keeps the loan officer's pipeline clean.
Insurance and covenant renewal tracking. Certificate of insurance requirements tied to loan covenants expire. An agent monitoring expiration dates on nCino__Covenant__c records (or your org's equivalent) can contact the borrower before the gap occurs — not after the covenant is already breached.
Pre-close document collection on CRE loans. Title commitments, survey certifications, and closing conditions accumulate on real estate loans in the weeks before closing. The agent tracks what's outstanding, contacts the relevant parties, and updates the loan record without the loan officer managing a spreadsheet in parallel.
The underlying object changes. The architecture doesn't.
A note on what Agentforce is not
Agentforce doesn't replace your loan origination workflow in nCino. It doesn't make credit decisions. It doesn't bypass your credit policy. What it does is remove the manual follow-up loop — the work that happens between the policy and the outcome, in the gaps that don't appear in any nCino dashboard.
If you can build a Flow in Salesforce and your org has Agentforce licensed and enabled, this is a strong first agent to build. Verify your object API names, test in sandbox, and keep the loan officer in the verification step. The document follow-up loop is where most institutions should start.