Stalled Deals: Automate Borrower Document Chasing

A file sits at 60% because you're still waiting on a borrower's 2023 tax return, an escrow date nobody confirmed, or one missing pay stub. Nobody on your team decided to let it stall; it stalled because chasing it is somebody's ninth priority on a busy day. Multiply that across a pipeline and you've got real revenue sitting still.

Quick answer: Chasing stalled deals means putting a timer on every open document request so a borrower gets a reminder on a set schedule (say day 2, day 5, day 8), and when the deadline passes the file escalates to the loan officer or processor who owns it. The goal is to remove "someone has to remember" from the process, because that is where files go cold.

Why deals stall waiting on the borrower

Most stalled files aren't stalled on you. They're stalled on a document only the borrower can produce, and the reminder to send it lives in one person's head. A processor asks for last year's W-2, the borrower means to dig it out, life happens, and eight days later nobody has followed up because everyone assumed someone else did. The deal isn't dead. It's just quiet, and quiet files close late or not at all.

The pattern repeats at every stage that depends on the customer: the initial application they half-finished, the pay stub that came in blurry, the tax return, the gift-letter, the settlement statement, the appraisal condition. Each one is a small ask. Each one carries a rate lock and a closing date behind it. And each one gets chased manually, which means it gets chased inconsistently.

There's a second leak here worth naming. When a file moves from loan officer to processor, or the borrower hands off to escrow, the document requests often get re-asked. Redfin's OpenBook reviews are full of borrowers describing exactly this: "So many emails going back and forth asking for things that were already provided." One training outfit, Aceable, calls incomplete handoffs the number one complaint processors have about originators. A borrower asked twice for the same pay stub doesn't just get annoyed. They start to wonder whether your team has it together, right when you need their trust to close.

What automating borrower document reminders actually looks like

Automating borrower document reminders means every open request has a schedule attached to it and sends itself on that schedule, in your team's voice, until the document arrives or a human decides to step in. It is not a blast. It is a per-borrower, per-document sequence with an off switch that trips the second the document lands.

The shape of it, stage by stage:

That last step is the one most tools skip, and it's the one that matters. A reminder that just keeps firing into the void is noise. A reminder that knows when to stop nudging the borrower and start alerting the human turns a stalled file into a decision someone actually makes.

Two things a system like this should never do on its own: give the borrower any rate, loan, or qualification advice, and ignore your texting rules. Whether an automated text can go to a given borrower at a given time is a compliance question your team and your compliance people own. A well-built system follows the rules you set; it doesn't decide them for you.

Manual chasing vs. an automated nudge system

The difference between a person chasing documents and a system doing it isn't effort. It's consistency and memory. A person is great at the judgment call and terrible at remembering to make the sixth follow-up on a Tuesday during a rate-lock scramble. A system is the reverse.

The point isn't to remove people. It's to stop spending your loan officers' judgment on the part a timer does better, and save them for the borrower who calls confused about which tax year you need.

This is the specific leak SalesOS is built to close for a loan team. It tracks what was asked for at each stage, nudges the borrower on the schedule you set in your own templates, stops the second the document arrives, and escalates the file to whoever owns it when a deadline passes, so a stalled deal becomes a flagged decision instead of a forgotten one. You can see how AI Cofounder works if you want the fuller picture of what runs inside the Claude or ChatGPT account you already pay for.

How to set up document chasing on your own team

You can build a version of this manually before you automate anything, and you should, because it forces you to write down the schedule you actually want. Start with your best-closed files and work backward.

1. List every document you chase, by stage

Write down every customer-dependent item, from the half-finished application to the closing documents. Group them by pipeline stage. This is the list your system will put timers on, and if it's not written down, it lives in someone's head, which is the whole problem.

2. Set an interval and a deadline for each

Decide the cadence before you automate it. A common shape is a reminder on day 2, another on day 5, a firmer one on day 8, and a hard escalation at the point where the missing document threatens the rate lock or closing date. The intervals matter less than the fact that they're consistent across every file.

3. Write the reminders in your voice, from files that closed

Don't use generic scripts. Pull the actual messages your team sent on the deals that closed clean and reverse-engineer the cadence from those. Borrowers respond to the tone your team already uses, and a reminder that sounds like a stranger gets ignored. This is exactly how we rebuild sequences when we implement SalesOS: from a client's own best converted examples, not a template pack.

4. Name who each escalation goes to

Every escalation needs an owner. When the day-8 deadline passes on a missing pay stub, someone specific should get the flag, not "the team." Ambiguity about who owns the nudge is why the nudge doesn't happen.

5. Kill the double-ask at handoffs

Before you widen anything, make sure a document sent to the loan officer is visible to the processor so the borrower never gets asked twice. If your CRM and your loan origination system (LOS) don't share that record, that's the first sync gap to close. We wrote about that specific problem in Stop Double-Entering Data Between Your LOS and Your CRM.

Common pitfalls when automating document reminders

The failure modes here are predictable, and every one of them makes the borrower experience worse instead of better. Watch for these.

Get the common case working first, watch it for a few weeks, then layer on the next stage. The same discipline applies to getting borrowers through the earlier steps, which we covered in Get borrowers to finish the application and send documents.

FAQ

How often should you remind a borrower about a missing document?

Reminders on a set cadence such as day 2, day 5, and day 8 work better than daily nudging or waiting until the deadline. Space them so each one is a little more direct, and put a hard escalation at the point where the missing document threatens the rate lock or closing date.

What happens when the borrower still doesn't send the document?

When a deadline passes with no document, the file should escalate to the loan officer or processor who owns it, with a flag that says this one needs a person now. A reminder loop that never hands off to a human just hides the stall instead of resolving it.

Can an automated system text borrowers about documents?

Whether an automated text can go to a given borrower is a compliance question your team and your compliance people decide, not the software. A well-built system follows the texting rules you set; it does not decide them for you, and no vendor should call it "TCPA-safe."

Why do borrowers get asked for the same document twice?

Borrowers get asked twice when a document sent to the loan officer isn't visible to the processor, so the request gets re-made at the handoff. Redfin's OpenBook reviews are full of this complaint, and it's an internal sync leak, not a borrower problem, fixed by keeping the record shared across your CRM and LOS.

If chasing stalled deals is eating your team's week, the fastest way to see whether this fits your process is to walk us through how documents move today. Book a demo and we'll map where your files go quiet and what a timed-nudge-and-escalation system would do about it: https://calendly.com/meet-6omb/ai-cofounder-interview