Loan Officer Follow-Up Scripts That Work at Every Stage

A pre-approved buyer sends documents, says they want a house, then goes quiet. You touch them once, then twice, and now the only line left is "just checking in." So you stop. The file sits.

Quick answer: A loan officer follow-up script that works gives every touch a reason the borrower cares about, keyed to their stage: a pre-approval expiry date, a question they raised, the one document the file is waiting on. It replaces "just checking in" with a specific reason to talk today, so the producer never runs out of things to say and the file never goes silent by default.

Why "just checking in" kills good files

The problem isn't that loan officers are lazy. The problem is that after the second touch, the only message left is a generic check-in, and that message is embarrassing to send and easy to ignore, so producers quietly stop. That's the leak Revenue OS names directly in their stalled-application guide: files pile up in pre-approval for three weeks or more on a single email, and most of them are not dead. They are waiting on a producer who ran out of reasons to call.

Grammarly's writing team makes the same point about "just checking in" in any context: it lacks context, reads as passive-aggressive, and makes the whole message feel optional instead of actionable. For a borrower deciding whether to text you back, "optional" is a decline.

The math is against stopping early. ZoomInfo's pipeline research puts roughly 80% of sales as needing at least five follow-up contacts, while about 44% of reps give up after a single attempt. Vedain's breakdown of touchpoint data lands the average rep at around two attempts, well short of where most deals actually close. Mortgage runs on the same curve. The difference between a producer who closes stalled files and one who writes them off is often just three or four more touches that each had a reason behind them.

What reason-based follow-up actually means

Reason-based follow-up gives each touch a real purpose the borrower cares about, instead of a reminder that you exist. Revenue OS frames it well: a message works only when it carries a reason to talk today, not a reason to buy today. You're not asking for a decision. You're giving them something specific to respond to.

WonderRates, in their guide on building a follow-up system without sounding pushy, describes the shape of a good message: pair context from the last interaction with one relevant piece of information or a clear question, and end with one easy next step. Every cadence date should have a reason behind it before it goes on the calendar. If you can't name why you're reaching out on a given day, that touch isn't ready.

The same conversation, written two ways:

The left column is memory-based nagging. The right column is a system working off three real triggers: a date, a question the borrower raised, and the specific blocker on the file. None of those require you to feel clever. They require you to know where the file is.

Build a reason library keyed to borrower stage

The fix is a short library of reasons organized by where the borrower sits in the process, so whoever picks up the file always has the next real thing to say. You're not writing new copy under pressure. You're pulling the reason that matches the stage.

A pre-approval letter is typically valid for only 60 to 90 days, per Zillow's guide on how long a pre-approval lasts. That expiry is the single most reliable reason in the whole library, and most producers never use it. Carlyle Financial's breakdown of what happens when a pre-approval expires explains why it lands: the borrower has to reapply with fresh documents like recent pay stubs and bank statements, and the rate may have moved. That's a real deadline with a real consequence, not a nudge.

A working library by stage:

The minimum you record per file, drawn from WonderRates' checklist, is not how many times you called. It's the borrower's situation, their open questions, their current stage, the next agreed action, and a follow-up date with a reason attached. Record that and the next touch writes itself.

Who owns the nudge when the producer is slammed

Most follow-up guides skip the real problem: when new leads are flooding in, nobody actually sends the stage-based touch, which is exactly why files die. A loan officer loses pre-approved buyers to silence not because they're lazy, as Revenue OS puts it, but because follow-up runs on mood and nobody is watching which stalled files got a call this week.

A reason library fixes the "what to say" problem. It does nothing for the "who remembers to say it" problem. Lemonhead Design's write-up on loan lead follow-up systems names the real cause: loans leak because follow-up depends on an individual remembering to act amid a heavy workload, instead of being built into a system with triggers and clear ownership. On a busy week, the producer is the single point of failure, and busy weeks are when the most leads arrive.

This is the leak SalesOS is built to close. It carries each file's context forward, so the next touch references the real blocker instead of a generic check-in, and it fires nudges on a schedule nobody has to hold in their head. It works inside the CRM you already run, in your team's own templates and voice, and your compliance team sets the texting rules it follows. You can see how AI Cofounder works if you want the full picture, but the short version is that the reason library runs even on the weeks your team is underwater. If your deeper problem is that automated sequences die the second a lead replies, that's a related leak worth reading about in why lead follow-up automation dies the moment a lead replies.

This is not document-chasing

Reason-based follow-up and document-chasing are two different leaks, and conflating them costs you files. Document-chasing is about getting a borrower who's already engaged to send the pay stub or tax return the file needs. The stalled-conversation leak is about a borrower who has gone quiet and no longer has a reason to respond at all.

Both matter, and the systems overlap, but they fail for different reasons. A file waiting on a document has an owner and a clear ask; it just needs a nudge that escalates. A file stalled in silence has no ask the borrower cares about, which is why "just checking in" shows up and why the producer gives up. If your bottleneck is the paperwork rather than the conversation, the fix is different, and stalled deals: automate borrower document chasing covers that one. This piece is about the files that went quiet because the reason ran out.

Common pitfalls

The most common mistake is treating cadence as a calendar instead of a set of triggers. Sending a touch every 14 days whether or not anything changed trains the borrower to ignore you, because the message is obviously automatic. A touch should fire off the pre-approval expiry date, a stale document, or a date the borrower gave you, not an arbitrary interval.

A few more that sink otherwise-good follow-up:

FAQ

What do I say instead of "just checking in" on a stalled pre-approval?

Lead with the expiry date, because it's a real deadline the borrower cares about. A pre-approval letter is typically good for 60 to 90 days, so a message like "your pre-approval expires in two weeks, want me to refresh it or are you pausing the search?" gives them a specific reason to respond today instead of a vague prompt to think about you.

How many times should a loan officer follow up before giving up on a stalled file?

Most loan officers quit too early, often after two touches, while roughly 80% of sales need at least five contacts per ZoomInfo's research. Plan for five to seven reason-based touches across the file's stage, and make your final touch the honest "should I keep this active or are you pausing?" close rather than another silent drop-off.

How is reason-based follow-up different from chasing borrower documents?

Reason-based follow-up works a borrower who has gone quiet and lost a reason to respond; document-chasing works a borrower who's engaged but hasn't sent a specific file the loan needs. They're separate leaks: one fails because the conversation ran out of reasons, the other because a task to collect paperwork had no owner.

Can a mortgage follow-up system run without sounding pushy or robotic?

A follow-up system sounds natural when every touch carries real context from the file and reads in the producer's own voice, built from the team's best converted deals rather than a generic script. Pushy comes from asking for a decision on every message; natural comes from giving the borrower one specific, easy thing to respond to.

Who should own follow-up on stalled loans when the team is busy?

On a busy week the loan officer is the single point of failure, which is why stalled files get written off exactly when new leads are flooding in. The durable answer is a system with triggers and clear ownership that fires the next reason-based touch on schedule, so follow-up doesn't depend on anyone remembering amid the workload.

If your stalled files are dying because the producer ran out of reasons and the busy weeks win, a short demo will show you how SalesOS carries each file's context forward and keeps the next touch firing. Book a demo and we'll walk your pipeline stage by stage.