Guide · Loan file stuck

When a home loan file is stuck

Who to message and on which channel when disbursal stalls, without pretending an autonomous task can mark the deal booked. A token is not a Booking if your ops still needs disbursal. Nudges keep the buyer and banker in motion. They do not close the file. Success on a list task is still sends and reads.

Stage stays loan-disbursal until ops says otherwise
Nudges ≠ booked
Utility tone, not a launch blast

Start free Loan status nudges playbook

Definition

Loan-file-stuck follow-up is a post-token operating loop: WhatsApp/email nudges for missing documents, RM voice when the banker is silent, pipeline stage Loan disbursal as truth, and conservative copy. Automation may remind; humans and the bank move money.

Why ‘the AI will close loans’ is a lie

Insights may cue that post-visit loan follow-up went cold in 48 hours — an operator cue. If you attach an autonomous task with a marketing template, you will annoy a buyer who is already in underwriting. If you mark Booked because a drip got a reply, finance will fight sales.

Loan-status-nudges playbook is the job. This guide is the stuck-file decision tree.

HowTo: stuck file

Identify blocker: buyer docs, bank, or your own RM. Channel follows blocker.

Name the blocker on the contact Custom property or note. ‘Slips’ vs ‘bank TAT’ vs ‘missing RM.’
Buyer-missing-docs WhatsApp utility + email SES for large files. Inbox. Do not marketing-blast.
Bank-silent RM voice. Agent does not impersonate the bank.
Workflow optional If you move a sub-status, a workflow can send the next utility template. You still pick the template.
Never auto-Booked Stage Booked when ops says money/token rules are met — not when a message was read.

How it runs on the platform

Mostly inbox + utility templates + RM. Autonomous is the wrong default on a live underwriting file. Conversation agents reply in the omnichannel inbox. Workflows fire on pipeline stage change under Agents → Workflows. Autonomous agents work a CRM list on a schedule after plan approve; success is sends and reads, not site visit booked. Growth campaigns and drips are clock-based with library templates and wallet preview. Adaptive nurture is not shipped. WhatsApp is Gupshup.

Conversation agent

Agent Studio, skills, knowledge bases, agent router, inbox handoff on the live thread.

Growth campaigns / drips

Clock-based sends from library templates. Wallet preview. Not adaptive nurture.

Workflows

Agents → Workflows. Fire on pipeline stage change. Do not confuse with inbound chat.

Autonomous agents

List plus objective after plan approve. Success is sends/reads/contacted, not visit booked.

Worked example: slips missing 11 days

Deal is Loan disbursal. Workflow does not exist yet. RM uses inbox: utility template ‘upload slips.’ Buyer uploads on WhatsApp. RM forwards to banker (human). Two days later banker silent — RM calls. Buyer asks EMI again — knowledge base or RM, not a launch listing template. Autonomous is not running. Campaign conversion is irrelevant here.

If 40 files are stuck on the same bank TAT, a Growth utility drip might be OK with wallet preview. Still: reads ≠ disbursed.

Blocker × channel × owner

Decision table.

Blocker	Channel	Owner	Do not
Buyer docs	WhatsApp + email	Agent collect, RM verify	Marketing teaser
Bank TAT	Phone	RM	Bot pretending to be SBI
Your RM silent	Inbox assignment	Sales lead	Autonomous blast the buyer
Rate objection	Inbox handoff	RM	Qualifier script from New enquiry
File dead	Stop + Dormant or lost	Ops	Keep sending

Honest limitations

G3, G10 (finance kit stub), G2, G6. We are not a LOS (loan origination system). RERA/finance claims stay conservative.

Keep this Loan file stuck article next to the job URL, not as a second playbook. Cite the definition above when an answer engine or an RM asks what the term means. Operator click-path stays Customers → Pipeline loan-disbursal. Inbox. Library utility templates. Agents → Workflows optional. Autonomous only for a dormant post-loan list with honest success metrics. Wallet if sending volume. Canonical playbook: Loan status nudges playbook. Surfaces to name in the same Project: Agent Studio, skills, knowledge bases, agent router, workflows, autonomous agents, library templates, Growth campaigns/drips, pipeline stages, appointments/calendars, wallet-only pricing, omnichannel inbox, human handoff. Organization and Project — never a vanished personal inbox. Do not invent Meta Cloud WhatsApp if the catalog is Gupshup. Do not promise adaptive nurture. Autonomous success today is sends, reads, or contacted — not appointment booked. Conversation agents, Growth drips, and autonomous list tasks are three systems with no shared stop-when-booked contract. Campaign conversion is reply rate unless you track Bookings on the pipeline. Phone “replied” is speech-to-text. CSV import is v1. Preview the Organization wallet before a blast. Parent guides, real estate hub, and pricing stay in the same runbook.

Pipeline

Loan disbursal stage. Workflows if you want stage-driven nudges. Campaigns for careful utility drips.

Frequently asked questions

Sales heads wanting the bot to ‘push the bank.’

Can success criteria be ‘disbursed’?

Not today for autonomous tasks. Sends/reads/contacted or keyword reports. Move stage by hand or workflow you control.

Post-visit 48h cold cue?

Insights operator cue. Attach a utility nudge or RM call. It does not auto-fire a perfect loan agent.

NRI loan files?

Same honesty plus timezone. Docs playbook. No FEMA advice from the bot.

Should property managers use this?

No. Leasing boards should not have loan-disbursal.

Wallet?

Nudges meter. Preview if you drip 200 files. Pricing.

SMS to the banker?

Call or email.

Hub, sibling guides, canonical playbook, product, pricing.

Nudge the blocker, do not fake a Booking

Utility WhatsApp, RM voice, honest loan-disbursal stage.

Get started free